# For AI agents

Discover the routed API, verify exact scopes and keep participant authority separate.

Cleard provider API · 1.4.0 · Base Sepolia test USDC.

Start with capabilities.json and routing-openapi.json. Use /v1/routing and fetch current metadata before sending requests.

[Routing OpenAPI](https://cleard.ai/docs/routing-openapi.json): Exact requests, responses, scopes and wallet-link operations.

[Quickstart](https://cleard.ai/docs/quickstart.md): Fresh access through payment, claim, refund and recovery.

- [Sandbox limits](https://cleard.ai/docs/routed-checkout.md#sandbox-limits): 20 lifetime purchases shared across account programs per deployment; 32 open purchases per merchant wallet per reserve. Unpaid checkouts count too.
- Obtain seven-day scoped service access through a verified account and the designated reviewer public key. Never invent program credentials.
- Ed25519 reviewer keys and EVM wallet keys have different roles. A service credential cannot sign for a merchant, buyer or reviewer.
- Preserve the creation-based claim deadline and separate decision/collection deadlines from the accepted purchase.
- POST may persist an obligation or execute testnet transactions. Bind the exact purchase, beneficiary, asset, chain, terms and evidence; preserve idempotency keys.
- Read receipts and fresh snapshots. Approved does not mean paid. Stop on changed pins, signatures or canonical blocks.
- Notifications use the fixed same-sandbox signed receiver and caller-driven retries. No external provider webhook or scheduler is active.

Reserve mode collects from explicit deposits and eligible routed payments. Direct mode requires a bounded signed mandate and separate allowance over the enrolled merchant wallet. Neither accesses provider-managed balances or intercepts arbitrary external inflows.

[Capabilities JSON](https://cleard.ai/docs/capabilities.json): Current machine-readable integration support.