Authentication
Send the key in the Authorization header, or in X-Ceta-Key:
Authorization: Bearer ck_live_Xr3…:<secret>\nX-Ceta-Key: ck_live_Xr3…:<secret>
A key is <key id>:<secret>. The id (ck_live_…, ck_test_…; older keys ck_…)
is shown in the console; the secret is shown once when the key is created or rotated, and only its SHA-256 hash is stored.
Scopes
read— everyGET /api/v1/…endpoint.mcp— the MCP server (POST /mcp) for AI agents.write— reserved for write endpoints.-
api:<slug>— one marketplace API through the gateway (issued when you subscribe).
Rotation and revocation
Rotate issues a new key with the same label and scopes; the old one keeps working for 24 hours so you can deploy the new one. Revoke stops a key at once.
Transacting
A key acts for the person who created it. Anything that moves money needs that person verified by Authpermit (GET /api/v1/verification). Test keys never transact.