Choose the right credential
ContoAdmin requires an organization API key from Settings > API Keys.
Admin SDK keys can call elevated HTTP API endpoints, but ContoAdmin rejects them.Generate SDK keys
Via dashboard
1
Open the agent
Go to Agents and select the agent that will use the key.
2
Create a key
Open the SDK Integration tab and click Generate SDK Key.
3
Choose a preset
Select Standard for the payment lifecycle plus read access, or Admin if the agent also
manages agents, wallets, or policies. Only organization owners and admins can create admin keys.
4
Set expiration
Choose 30, 90, or 180 days, 1 year (the default), or 2 years (the maximum).
5
Copy the secret
Via API
"keyType": "admin", the organization API key needs the admin or
team:write scope.
Scopes
A scope authorizes an operation. Wallet links, policies, spend limits, approvals, and resource ownership still decide what a key can pay.Agent key presets
Standard is the default. x402 and MPP recording requirepayments:execute, not
transactions:write, so they work with a standard key.
Admin SDK keys
Admin keys add the scopes that Standard lacks: audit reads, write access to agents, wallets, policies, counterparties, and alerts, retries of failed transfers, policy change requests, andmerchant:purchase (off unless Conto enables it for your organization). On organization endpoints
an admin key acts with Manager permissions for the whole organization. Admin keys do not include
team management, organization settings, or the organization admin super-scope, and an admin key
cannot create another admin SDK key.
Organization API key scopes
Only Owners create organization API keys, in Settings > API Keys or withPOST /api/api-keys.
Organization keys always expire: expiresInDays defaults to 365, which is also the maximum. The
dashboard offers three presets, and the API also accepts individual scopes.
Available scopes:
agents, wallets, transactions, policies, counterparties, and alerts
(each :read and :write), plus analytics:read, audit:read, team:read, team:write,
org:read, org:write, and admin.
Revoke keys
Via dashboard
- Go to Agents
- Open the agent
- Open the SDK Integration tab
- Click Revoke
Via API
Best practices
- Store SDK keys in a secrets manager, not in source control.
- Use separate keys for development, staging, and production.
- Prefer standard keys unless the agent needs elevated management access.
- Standard keys can move funds. Limit what they can spend with policies, spend limits, and approvals.
- Rotate keys on a schedule instead of waiting for emergency revocations.