Skip to main content
Conto SDK requests authenticate with agent-specific SDK keys:
Every SDK key belongs to exactly one agent and always expires: the default lifetime is 365 days and the maximum is 730 days.

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

The full key is shown only once. Store it in your secrets manager before closing the dialog.

Via API

Response
To create an admin key with "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 require payments: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, and merchant: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 with POST /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

  1. Go to Agents
  2. Open the agent
  3. Open the SDK Integration tab
  4. Click Revoke

Via API

Revocation is immediate.

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.