Upgrading from Agent API v2
Every RPC URL and key secret issued under Agent API v2 keeps serving. The v2 management API is retired: its routes answer410 gone with a next_action
naming the account API operation to use, and the same management secret works
there. Use this page to move an integration from /api/v1/management to the
account API.
What keeps working
What’s retired
Where each v2 operation moved
What changed in meaning
- Balances belong to accounts, not keys. Every key of an account draws on one USD balance. Payments addressed to a v2 key ID credit that key’s account.
- Keys reach every profile of their account. A v2 key pinned to one Custom profile keeps that profile as its default and is scoped to it.
- Running out of money doesn’t stop a paying app. Accounts that have paid fall back to public providers for 30 days instead of failing.
- Usage is counted per method. Requests are sized in per-method CU and priced in USD; free allowances and Pro included usage are restated in per-method CU.
- Agent-created keys share one rate limit per account instead of 50 RPS each.
- A claim link comes from the agent, not the RPC key, so an exposed key can’t hand over a funded account. Keys from before agents existed still claim with their RPC key.
Older keys without an agent
A key created before agents existed has its own provisional account with no agent. Its RPC key can request that account’s claim link, since it’s the account’s only credential:Older URL forms
These forms serve until 30 days pass with no traffic on them:Next
- Keys, URLs and profiles: the URL grammar.
- Accounts, people and agents: what an account owns.
- Response signals and errors: the new headers and codes.