Global Options
All commands support these flags:Agent & Status
conto doctor calls GET /api/sdk/setup with your SDK key and reports each check, including
whether the key has payments:request and payments:execute and whether the wallet can execute
real transfers. It exits non-zero when a hard check fails, so you can use it in scripts.For anonymous sandbox setups created with create-conto-agent --sandbox, conto doctor treats
simulated execution as healthy and reports the sandbox expiry instead of warning that the wallet
is manual-only.Payments
--dry-run runs the full policy evaluation (all rules, all policies) and returns APPROVED,
DENIED, or REQUIRES_APPROVAL without sending any transaction.Transactions
Wallets
Spending Limits
Alerts
Policies
See Policy Management for full CRUD documentation.Authentication
MCP Server
Documentation
Init Wizard
--chain expects the chain ID returned by GET /api/chains, for example 42431, 4217, 8453,
or solana-mainnet. If it is omitted, setup uses Tempo Testnet (42431). --api-key is also
accepted, but CONTO_ORG_API_KEY avoids placing the key in process arguments.JSON Mode
Every command supports--json for machine-readable output:
Configuration Files
Configuration precedence is process environment, project
.env.local, project
conto.config.json, then global ~/.conto/config.json. Generated credential files use owner-only
permissions, and init adds .env.local to the project .gitignore.