Skip to main content

​
Developer Tooling

Use this page when you want a working integration, not just conceptual docs. Start with the CLI, verify the runtime with setup probes, then add API docs, MCP tools, webhooks, and audit trails as you move toward production.

​
Fastest First Run

npx @conto_finance/create-conto-agent
The CLI provisions an agent, wallet, policy, SDK key, and local config. Choose Tempo Testnet for the first run so you can fund with free pathUSD and exercise the real request and execute flow without real funds. After the wizard completes, run the generated example: 
npx tsx example.ts

​
Toolbelt

ToolUse it forLink
CLI quickstartOne-command agent, wallet, policy, and key setupCLI quickstart
SDK setup probeVerify agent status, wallets, scopes, and limitsGET /api/sdk/setup
OpenAPIGenerate clients and inspect request schemasAPI reference
MCP serverGive Claude/Codex/Cursor agent tools accessInstall MCP server
WebhooksReceive signed payment and agent lifecycle eventsWebhooks
Audit logsReview policy decisions and sensitive actionsAudit logs
Policy testingDry-run and validate policy behaviorPolicy testing

​
Setup Probe

Before making a payment, call the setup endpoint with the same SDK key your agent will use: 
curl https://conto.finance/api/sdk/setup \
  -H "Authorization: Bearer $CONTO_API_KEY"
Check these fields in the response:
  • agent.status is ACTIVE
  • at least one wallet is linked and funded
  • scopes includes payments:request
  • execute-capable flows include payments:execute
  • limits and policies match the agent’s expected spending envelope

​
Generated Clients

The OpenAPI document is the contract for generated clients: 
curl https://conto.finance/api/openapi > conto-openapi.json
Use it with your preferred generator or import it into tools like Postman, Bruno, or an internal API portal. The interactive reference is available at conto.finance/api-docs.

​
Production Readiness

Before giving an autonomous agent production funds, confirm:
  • SDK keys are named by environment and agent, for example prod-research-agent
  • each runtime uses the narrowest key type and scopes it needs
  • webhook signature verification uses the raw request body
  • testnet policy results match the production policy envelope
  • organization API keys are stored only in backend or CI systems
  • agent SDK keys are rotated after demos, contractor access, or leaked logs
  • audit logs are reviewed after the first live payment

​
Useful Next Reads

Choose Your Integration

Decide between SDK, REST, MCP, OpenClaw, Hermes, x402, and MPP.

Recipes

Copy-paste API, SDK, skill, and payment examples.

Authentication

Understand SDK keys, org API keys, key types, and scopes.

Testing Payments

Safely test with Tempo Testnet before moving money in production.