# Verae Customer Portal

> customer.verae.ai is the Verae customer account portal for MCP agents, direct API integrators, PDF registration, and DataCube / Peergos apps. Same billing backend as zap.verae.ai; different offerings and usage instructions.

Host: customer.verae.ai
Canonical portal: https://customer.verae.ai/portal/
Sibling surface: https://zap.verae.ai/portal/

## Offerings and usage

- MCP timestamping via mcp.verae.ai — digests-only; hash locally before stamp.
- Edge REST: POST https://zap.verae.ai/v1/timestamp and /v1/timestamps with wait-by-default; attachPdf:true for registration PDF.
- Mint long-lived xVerae- tokens under Security; use as x-api-key or Authorization: Bearer on the edge.
- DataCube / Peergos outbox stamps use the same digests-only contract.
- Upstream api.veraetime.net still uses MCP JWT until it accepts xVerae- natively.

## Preferred links

- [Customer account portal (MCP/API/PDF/DataCube)](https://customer.verae.ai/portal/)
- [OpenAPI explorer on the API host](https://zap.verae.ai/docs)
- [MCP timestamping app](https://mcp.verae.ai/)
- [Application client OpenAPI](https://mcp.verae.ai/openapi/application-client.yaml)
- [This file](https://customer.verae.ai/llms.txt)
- [Zapier-oriented portal](https://zap.verae.ai/portal/)

## Auth for apps

- Prefer long-lived `xVerae-` tokens from the portal Security tab (shown once; store as `x-api-key` or `Authorization: Bearer`).
- Legacy `key-` API keys still work.
- Digests-only: send SHA-256 hex digests; do not upload file bytes.
- Stamp wait is on by default; set `attachPdf: true` only when a registration PDF is needed.

## Optional

- [Full OpenAPI](https://zap.verae.ai/docs)