ContoAdmin for organization-level automation: provisioning agents, attaching wallets, assigning
policies, and creating agent SDK keys. Use the Conto client for agent runtime payment calls.
ContoAdmin takes an organization API key (conto_...), never an agent SDK key. See
authentication for the key types.
Initialize
Provision an agent
CONTO_API_KEY.
The example uses CONTO_MANAGED. ORGANIZATION_CONTROLLED wallets are EVM only and need the
owner’s public authorization key registered in Settings > Security > Wallet ownership first. Use
CONTO_MANAGED when the owner does not need to export the key. If keyAccess is
EXPORT_RECONCILIATION_REQUIRED, wait before attempting another export.
agents.list({ search }) also matches externalId. Callback query and fragment values are
redacted in responses, so send callbackUrl again when rotating a callback token. Each agent’s
setup field reports READY or ACTION_REQUIRED and names the field to update.
Method map
See shared budgets for inputs, permissions, and examples.
Teams
Teams need SDK0.10.0 or later. A team’s policies apply to every agent in it, alongside company
policies, and its slug is recorded as the department on its agents’ payments. Reads need
agents:read and changes need policies:write.
team.listMembers() and need the Manager role or higher.
Moving an agent into a team takes it out of its old one. If your organization requires approval for
budget changes and a move or removeAgent() takes the agent off a budget, it waits for governance
approval. A team can be deleted once it has no agents, policies or budgets.
With SDK 0.10.1 or later, agents.listPolicies(agentId) is typed with the agent’s team and the
company and team policies it inherits.
Policy version history
Every change to a policy is versioned. Review the history, diff two versions, and roll back.Scopes
Read methods need the matching*:read scope. Create, update, delete, link, assign, provision,
freeze, and revoke methods need the matching *:write or admin scope.
Security notes
- Organization keys can manage all agents and wallets in the organization.
- Prefer scoped keys for CI and provisioning jobs.
- Rotate keys regularly and revoke unused keys.
- Only owners change billing plans, in the dashboard. Organization API keys cannot change them.