# Zappier by Verae

> Zappier (zap.verae.ai) is the Zapier-oriented customer surface for Verae timestamping. Hash files locally, stamp digests only (no file upload), wait for receipt by default, optionally attach a registration PDF.

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

## Offerings and usage

- Zapier Platform app creates: timestamp and timestamps_batch (API Base URL https://zap.verae.ai, x-api-key or xVerae- Bearer, x-billing-channel: zapier).
- Browser hasher at /client/hasher/ then POST /v1/timestamp or /v1/timestamps with digests only.
- Customer account portal at /portal/ for billing, invoices, statement, and minting long-lived xVerae- tokens.
- OpenAPI explorer at /docs. Prefer /v1/*; legacy key-… keys still work.

## Preferred links

- [Customer account portal (Zapier-focused)](https://zap.verae.ai/portal/)
- [OpenAPI / Swagger UI](https://zap.verae.ai/docs)
- [Client-side SHA-256 hasher](https://zap.verae.ai/client/hasher/)
- [Zapier Platform app assets](https://zap.verae.ai/client/zapier-app/)
- [This file](https://zap.verae.ai/llms.txt)
- [MCP / API / PDF / DataCube customer portal](https://customer.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)