Make your first policy-checked test payment
Connect your buyer agent and set its spending rules. Start with a simulated sandbox: no account, signer, or funds needed.
Node.js 20.19+ · Temporary credentials expire after 7 days
mkdir conto-first-paymentcd conto-first-paymentnpx -y @conto_finance/ create-conto-agent --sandbox --jsonnode example.mjs --executeWhat success looks like
{
"status": "completed",
"receipt": { "settlementMode": "test" }
}Your example also prints a request ID.
Choose what you want to test
Simulated settlement and an onchain testnet transfer are separate paths.
Simulated sandbox
Test API calls, spending controls, and receipts. A completed response has settlement mode test.
Open sandbox guide
Tempo Testnet transfer
Sign in and create a managed wallet funded with free pathUSD. Settlement mode live means onchain, including testnet. Check chain 42431 and wait for completion.
Open testnet guide
Test all three payment decisions
A successful integration handles all three decisions.
Approved
Execute the approved request, then inspect its receipt and completion state. Approval alone is not settlement.
Blocked
The API returns DENIED. Stop and read the reason. In a new anonymous sandbox, a request above the default $5 per-payment limit is blocked.
Needs approval
The API returns REQUIRES_APPROVAL. Keep the request ID while an authorized reviewer decides. Check its state before taking the next action.
Connect your runtime
Use an agent SDK key for payments. Use an organization key to provision resources.
TypeScript
Typed payment requests, receipts, and organization management in your backend.
npm install @conto_finance/sdkHTTP and Python
Use the REST API from any language. Start with a runnable Python example.
GET /api/sdk/setupMCP assistants
Connect Claude Code, Claude Desktop, or another MCP client with an agent SDK key.
npx @conto_finance/mcp-serverCheck your integration before using real funds
Keep the request ID so an uncertain response never becomes an accidental second payment.
Inspect a payment
Follow the original request ID through approval, execution, and settlement.
Connect webhooks
Verify signatures, handle repeated events, and reconcile missing deliveries.
Prepare for production
Check network support, signing, credentials, and recovery before moving funds.
Need help with an integration? Contact developer support with your request ID and package version.
Common questions
What does Conto do?
Conto is a buyer-side control layer. The agent owner or budget holder sets policy. Conto checks it before the agent pays, routes approvals, and records outcomes.
What can an agent try without a person?
An anonymous sandbox needs no account, signer, or funds. It creates temporary credentials that expire after seven days, and a preset test card with fixed limits for simulated purchases at Conto test merchants. A completed test receipt means the simulated workflow finished. No onchain transfer occurred.
Which runtimes can connect?
Call Conto from the agent's code using REST, the TypeScript SDK, the Node.js CLI, or a local STDIO MCP client such as Claude, Codex, Cursor, or VS Code. OpenClaw and Hermes can use the published skill. The CLI and SDK require Node.js 20.19+. For MCP, Node.js 22 requires 22.12+ and Node.js 23 requires 23.2+. Payment tools run in the local STDIO server, `npx @conto_finance/mcp-server`, with an agent SDK key. The hosted server at https://conto.finance/api/mcp signs a person in with OAuth to view their workspace and propose changes. It never creates SDK keys or makes payments. https://conto.finance/docs/mcp is a documentation search server.
What requires a person?
A verified, signed-in owner claims the sandbox using a single-use browser handoff. Remote agents can poll for completion without a localhost callback. An onchain testnet payment needs an account and a funded wallet. Production requires the appropriate access, wallet and signing setup, funds, and approved policies. Claiming a sandbox does not enable production payments. A connected card needs a Builder or Enterprise plan, and the cardholder adds and verifies it in the dashboard. Any plan can try connected cards and Conto in test mode. Upgrade to Builder or Enterprise for production card access.
Can a wallet bypass Conto?
An external signer must call Conto before sending. A wallet owner or exported key may spend outside that integration. Enforcement depends on the wallet control model. Review the custody guide before selecting it.
Which payment rails are available?
Use stablecoins or connected cards. Check the payment support reference for network and signing prerequisites, and the pricing page for current plans.
Building with a coding agent? Machine-readable resources
The agent manifest indexes installation, authentication, sandbox signup, skills, and documentation.