Defaults

Chains and currencies

Wallet creation and the CLI default to Tempo Testnet. Payment requests use the selected wallet’s network and have no testnet default of their own. Mainnet setup is an explicit choice in the CLI.

Setting	Default	Notes
Default chain ID (wallet creation)	`42431` (Tempo Testnet)	Applied when `chainId` is omitted from `POST /api/wallets`. For payments, select the intended wallet with `walletId`.
Default chain ID (CLI)	`42431` (Tempo Testnet)	Used by `create-conto-agent`. Override with `--chain`. Mainnet also requires confirmation.
Default chain type	`EVM`	Applied to new wallets when omitted.
Default Tempo Mainnet currency	`USDC.e`	Returned in payment responses for chain `4217`.
Default Tempo Testnet currency	`pathUSD` (TIP-20)	Returned in payment responses for chain `42431`.
Default Base/Ethereum/Arbitrum/Polygon currency	`USDC`	The chain’s primary stablecoin.
Default Solana currency	`USDC` (SPL)	Resolved by chain ID `solana-mainnet`.

For a headless mainnet setup, specify both the chain and acknowledgement, for example --chain 4217 --confirm-mainnet. Interactive mainnet setup displays a real-funds confirmation before creating any resources.

Explorer URLs

Each Tempo network has its own canonical explorer.

Chain ID	Name	Explorer
`4217`	Tempo Mainnet	`https://explore.tempo.xyz`
`42431`	Tempo Testnet	`https://explore.testnet.tempo.xyz`

EVM chains use the standard block explorers (basescan.org, etherscan.io, etc.) and Solana uses solscan.io / explorer.solana.com.

Wallets

POST /api/wallets uses these defaults when a field is omitted:

Field	Default
`walletType`	`EOA`
`chainType`	`EVM`
`chainId`	`42431` (Tempo Testnet)
`custodyMode`	`MANAGED`
`controlModel`	Organization default. `CONTO_MANAGED` until an owner public key is configured

Custody priority

The payment evaluator selects wallets in this order when an agent has multiple linked wallets: MANAGED > SMART_CONTRACT > EXTERNAL

Agent-wallet links

POST /api/agents/{id}/wallets applies these defaults. Linking a mainnet wallet to a DEV or STAGING agent succeeds but returns a warnings entry, because only PROD agents can pay from mainnet wallets.

Field	Default	Notes
`delegationType`	`LIMITED`	Other values: `FULL`, `VIEW_ONLY`, `PREAPPROVED`, `ALLOWLIST`.
`spendLimitPerTx`	`100`	USD. `null` means unlimited.
`spendLimitDaily`	`1000`	`null` means unlimited.
`spendLimitWeekly`	`null`	Unlimited unless set.
`spendLimitMonthly`	`null`	Unlimited unless set.
`allowedHoursStart`	`0`	Hour of day, 0-23.
`allowedHoursEnd`	`24`	Hour of day, 1-24.
`allowedDays`	All 7 days	Pass a shorter list, e.g. `['Mon','Tue','Wed','Thu','Fri']`.
`timezone`	`UTC`	IANA names accepted (`America/New_York`, etc.).

For wallet-level spend limits, null means no cap and 0 blocks all payments through the link. To remove a cap, set the field to null with PATCH /api/agents/{agentId}/wallets/{walletId}.

External-wallet auto-create

When POST /api/sdk/payments/approve is called with a senderAddress that does not exist in the organization, Conto creates an EXTERNAL wallet automatically with:

Field	Default
`spendLimitPerTx`	`100` USD
`spendLimitDaily`	`1000` USD
`spendLimitWeekly`	`5000` USD
`spendLimitMonthly`	`20000` USD
`delegationType`	`FULL`
`custodyType`	`EXTERNAL`
`enforcementMode`	`MONITORING_ONLY`

delegationType is a label on the agent-wallet link. It does not loosen the spend limits or policies. enforcementMode: MONITORING_ONLY means Conto does not hold this wallet’s keys. It checks payments sent through approve and cannot block a transfer the wallet signs outside Conto. See wallet custody. Tighten these via PATCH /api/agents/{agentId}/wallets/{walletId} before relying on them in production.

Approval tokens

Endpoint	Token TTL
`POST /api/sdk/payments/request`	5 minutes
`POST /api/sdk/payments/approve` (external wallets)	10 minutes

Tokens are single-use. After expiry, request approval again.

SDK keys

Setting	Default	Notes
`expiresInDays`	`365`	Optional. Defaults to 365 when omitted.
Max `expiresInDays`	`730`	2-year hard cap.
Key format (standard)	`conto_agent_...`	Per-agent. Used for payment operations.
Key format (admin)	`conto_agent_...`	Per-agent. Adds write scopes. See Credential scopes.
Org API key format	`conto_...`	Org-level. Used with `ContoAdmin`.

Full keys are returned only once at creation. Store them immediately.

Payment requests

Setting	Default
`currency` (on `POST /api/transactions`)	`USDC`
`urgency`	`NORMAL`
`autoExecute`	`false`
Idempotency window	Indefinite. Same `idempotencyKey` + same payload returns the cached result. Different payload returns `409 IDEMPOTENCY_CONFLICT`.

Policy evaluation

Setting	Default	Notes
Policy priority direction	Higher first	Policies are evaluated in descending priority.
Default policy priority	`50`	Use `0-100`. Reserve 90+ for security/compliance rules you want evaluated first.
API scope when omitted	Inferred	`assigned` with `agentIds`, otherwise `organization`.
Rule combination	`AND`	All rules in a policy must pass.
Policy combination	`AND`	Organization baselines and all effective assignments must pass. First `DENY` stops evaluation.
Trust score scale	Decimal `0.0-1.0`	`TRUST_SCORE` compares this against the network score. An address with no network history scores `0.5`.

Counterparties

Field	Default
`trustScore`	`0.5`
`trustLevel`	`UNKNOWN`
`riskLevel`	`MEDIUM`
`verified`	`false`
`type`	`VENDOR`

A new counterparty record starts at 0.5 with level UNKNOWN. Conto sets the level from the ranges below each time it rescores the counterparty, for example after a confirmed payment. TRUSTED also requires a verified counterparty, otherwise the level stays VERIFIED. Below 0.2 the level is BLOCKED only when there are adverse signals such as failed or flagged transactions, otherwise UNKNOWN.

Range	Level
`0.75 - 1.0`	`TRUSTED`
`0.5 - 0.75`	`VERIFIED`
`0.2 - 0.5`	`UNKNOWN`
`0.0 - 0.2`	`BLOCKED`

Rate limits

See Rate limits.

Pagination

Field	Default
`limit`	`50`
Max `limit`	`100`
`offset`	`0`

Response envelopes vary by endpoint. See API conventions.

Webhook delivery

Setting	Default
Max attempts	`3` (network errors, `408`, `429`, and `5xx` only)
Backoff	Immediate first attempt, retries after 1s, then 2s
Timeout	10 seconds
Signature header	`X-Conto-Signature` (HMAC-SHA256)
Required scheme	HTTPS (HTTP and private IPs blocked)

Auto-freeze thresholds

Automatic protection is off for new agents (enabled: false). These are the default thresholds:

Setting	Default
`maxConsecutivePolicyViolations`	`5`
`maxConsecutivePaymentFailures`	`5`
`spendVelocityMultiplier`	`3` (3x the agent’s normal rate)
`largePaymentMultiplier`	`10` (10x the agent’s normal size)
`minimumTrustScore`	`0.2`
`trustScoreDropThreshold`	`0.3` (a 30% drop)
`maxNewCounterpartiesPerHour`	`10`

Tunable via PATCH /api/agents/{id}/freeze-config. See Automatic agent protection.

Org roles

OrgRole enum: OWNER, ADMIN, MANAGER, MEMBER, VIEWER. New members default to MEMBER. See Roles and permissions for the permission matrix.

API

SDK and tools

Policy rules

Chains and currencies

Explorer URLs

Wallets

Custody priority

Agent-wallet links

External-wallet auto-create

Approval tokens

SDK keys

Payment requests

Policy evaluation

Counterparties

Rate limits

Webhook delivery

Auto-freeze thresholds

Org roles

​Chains and currencies

​Explorer URLs

​Wallets

​Custody priority

​Agent-wallet links

​External-wallet auto-create

​Approval tokens

​SDK keys

​Payment requests

​Policy evaluation

​Counterparties

​Rate limits

​Pagination

​Webhook delivery

​Auto-freeze thresholds

​Org roles

Chains and currencies

Explorer URLs

Wallets

Custody priority

Agent-wallet links

External-wallet auto-create

Approval tokens

SDK keys

Payment requests

Policy evaluation

Counterparties

Rate limits

Pagination

Webhook delivery

Auto-freeze thresholds

Org roles