Skip to main content
The ZeroClick agentic API is a conventional HTTP REST API under /api/v1/*, fronted by the ZeroClick storefront. Agents pay at ZeroClick’s pay URL; ZeroClick verifies payment, HMAC-signs the request, and forwards it to the Momentra upstream. The backend verifies the signature, checks the allowance, serves, and settles usage.

​
How a call flows

1

Agent pays at ZeroClick

The agent is issued a challenge and pays at the ZeroClick pay URL (paid routes only).
2

ZeroClick signs and forwards

ZeroClick HMAC-signs the request (zc-signature) and forwards it to the Momentra backend, preserving the path verbatim.
3

Momentra verifies and serves

The backend verifies the signature, checks the allowance for paid routes, serves, and settles usage via a zc-usage header on the 2xx.
Every REST request must include the full /api/v1 prefix exactly as shown. Dropping it returns 403 Missing Authentication Token. The /api/v1 prefix is owned by the paths, not the base URL — the storefront base owns the host, the paths own the prefix.

​
Connection

Endpoints

The six /api/v1/* routes and their bodies.

The ZeroClick contract

Verify → check allowance → serve → settle.

Free and paid

The two kinds of free work and the credit parity.

Configuration

Dashboard setup, SSM secrets, go-live checklist.