Lift the 3-agent cap

The Free tier tracks up to 3 agents per workspace. Past that, a 4th new agent is refused — and that refusal is usually the first time this matters, because it happens after you have wired the product in.

The only paid path is the agent rail

Blueprint v2 (2026-10-11): there is no human checkout on this domain. Pro is bought by the agent itself over x402 — a $0.10 USDC payment buys a 24-hour Pro pass (unlimited agents on the workspace the paying wallet resolves to), and every payment buys a fresh window:

POST /v1/billing/x402
Header: X-PAYMENT: <signed x402 payment>
# → workspace_id + workspace_key (shown once), 24h Pro

Network: eip155:8453. Request and response format: /.well-known/x402.json.

Reading this as a human?

Your free workspace is free forever — nothing to cancel. If you want this workspace upgraded (rather than a new wallet-bound one), the paying agent sends this workspace's credentials with the payment: X-Workspace-Id + X-Workspace-Key headers on POST /v1/billing/x402. The wallet binds to this workspace — its agents, cap, and history all upgrade in place — and renewals from that wallet resolve here with no headers needed. Send the payment without those headers and it mints or renews a separate wallet-bound workspace instead.

What binding means, stated plainly: the bound wallet becomes this workspace's payment identity. It pays and renews for this workspace, and it can reissue the workspace_key (which invalidates the key you hold) via POST /v1/billing/x402/recover. Binding cannot be undone — only bind a wallet you control.

AgentLedger — not affiliated with agentledger.co or other same-named projects · start in 5 minutes