/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.Why a cold probe sees 401 before any 402
This surface is broker-mediated by design. Only ZeroClick holds the signing
key (kid → secret); it signs each request after collecting payment, then
forwards it. The backend verifies that signature first, so a cold, unsigned (or
wrongly-signed) probe is rejected with 401 invalid_zeroclick_signature before
the allowance check that would issue a 402. That is correct behavior, not a
broken payment path: the 402 payment challenge is issued by ZeroClick at the
pay URL, not by a raw probe against /api/v1/*.
If you want a payment challenge an agent can hit directly with no broker
pre-registration, use the MCP server instead — a paid tool with an empty
balance returns a Stripe Checkout link inline (see
MCP billing). The two surfaces bill the same
momentra-events
service on one shared unit: 1 event = 1 credit = 1 ZeroClick unit = $0.01.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.
