Skip to main content
The /sandbox/* routes let an autonomous agent onboard itself: mint a zn_test_ key with no account, place sandbox orders, and later have a human fold the sandbox into a real Zinc account without invalidating the agent’s key.
This group is the route-by-route reference. For the narrative version — why it works this way, the walkthrough, and what changes when you go live — start with the Agent Sandbox guide.

​
Endpoints

​
Behavior worth knowing before you call them

  • Provisional accounts are sandbox-only. A minted account can never act on live mode, claimed or not, and has no wallet — sandbox orders don’t need one.
  • Keys expire after 7 days without use, and everything they created is deleted with them. Any use resets the clock.
  • Minting is rate-limited per IP per day plus a global ceiling. 429 means reuse the key you already have; 503 means the mint path is temporarily unavailable and failing closed rather than running uncapped. Both carry Retry-After.
  • Claim tokens are single-use and returned exactly once, in the mint response’s claim_url. Only the hash is stored, so the URL cannot be regenerated.
  • Claiming reassigns the key rather than revoking it, which is the point — the agent keeps working afterward.

Agent Sandbox guide

The flow end to end, with a quickstart and a going-live checklist.

Sandbox & Testing

Test mode itself — the magic product URLs and the scenarios they simulate.