SDK Authentication
Conto SDK requests authenticate with agent-specific SDK keys:Choose the Right Credential
Use the credential type that matches the job you need to do:| Credential | Format | Best for | Notes |
|---|---|---|---|
| Standard SDK key | conto_agent_... | Agent payment requests and agent-scoped read access | Works with the Conto client |
| Admin SDK key | conto_agent_... | Delegated agent workflows that need elevated access to agents, wallets, or policies | Agent-scoped identity with an expanded scope preset |
| Organization API key | conto_... | Backend/admin automation across the whole organization | Use with ContoAdmin |
ContoAdmin requires an organization API key. Admin SDK keys can call elevated HTTP API
endpoints, but they are not a drop-in replacement for the ContoAdmin constructor.Generate SDK Keys
Via Dashboard
Choose a preset
Select Standard for least-privilege access or Admin if the agent needs elevated
management access.
Via API
Use SDK Keys
Initialize the agent SDK
Use environment variables
.env
Use org keys with ContoAdmin
Admin SDK Reference
Use organization API keys with
ContoAdmin for organization-wide provisioning and management.Standard SDK Scopes
If you omitscopes, standard SDK keys get the default least-privilege preset:
| Scope | Included by default | Description |
|---|---|---|
payments:request | Yes | Request policy evaluation for a payment |
wallets:read | Yes | View wallet balances and limits |
policies:read | Yes | View policies assigned to the agent |
transactions:read | Yes | View transaction history |
counterparties:read | Yes | View counterparties and trust data |
alerts:read | Yes | View alerts related to the agent |
agents:read | Yes | View agent profile and setup summary |
analytics:read | Yes | View spend analytics |
network:read | Yes | Query network trust data |
payments:execute | No | Execute approved payments or use autoExecute |
payments:approve | No | Approve external-wallet payments |
payments:confirm | No | Confirm external-wallet payments |
transactions:write | No | Retry failed transactions or record x402/MPP transactions |
policies:exceptions | No | Request and view policy exceptions |
counterparties:write | No | Create and update counterparties |
alerts:write | No | Acknowledge and resolve alerts |
audit:read | No | View audit logs |
Use the
scopes array when creating a standard SDK key via API if the agent needs more than
the default preset.Admin SDK Keys
Admin SDK keys use an elevated preset intended for delegated agent management workflows. They include:- All standard SDK scopes
agents:writewallets:writepolicies:write
admin super-scope.
They also cannot create other admin SDK keys. That escalation path is blocked intentionally.
Key Expiration
All SDK keys have a mandatory expiration.| Value | Behavior |
|---|---|
| Omitted | Defaults to 365 days |
30 | Short-lived testing key |
90 | Recommended production rotation window |
365 | Long-lived standard key |
730 | Maximum allowed lifetime |
Revoke Keys
Via Dashboard
- Go to Agents
- Open the agent
- Open SDK Keys
- 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 truly needs elevated management access.
- Grant
payments:executeonly to agents that should actually move funds. - Rotate keys on a schedule instead of waiting for emergency revocations.