Machine View
Developer Tooling
Source: https://conto.finance/docs/guides/developer-tooling
# Developer Tooling
> A practical toolbelt for building, testing, and operating Conto agent payment integrations
- Human URL: https://conto.finance/docs/guides/developer-tooling
- Raw Markdown: https://conto.finance/docs/guides/developer-tooling.md
- Terminal view: https://conto.finance/ai/docs/guides/developer-tooling
Documentation group: Guides
# Developer Tooling
Use this page when you want a working integration, not just conceptual docs. Start with the CLI,
verify the runtime with setup checks, then add API docs, MCP tools, webhooks, and audit trails as
you move toward production.
## Fastest First Run
```bash
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:
```bash
node example.mjs
```
## Toolbelt
| Tool | Use it for | Link |
| --------------- | --------------------------------------------------- | ----------------------------------------------- |
| CLI quickstart | One-command agent, wallet, policy, and key setup | [CLI quickstart](https://conto.finance/cli/quickstart) |
| SDK setup check | Verify agent readiness, wallets, scopes, and limits | [`GET /api/sdk/setup`](https://conto.finance/sdk/installation) |
| OpenAPI | Generate clients and inspect request schemas | [API reference](https://conto.finance/api-docs) |
| MCP server | Give Claude/Codex/Cursor agent tools access | [Install MCP server](https://conto.finance/mcp/install) |
| Webhooks | Receive signed payment and agent lifecycle events | [Webhooks](https://conto.finance/guides/webhooks) |
| Audit logs | Review policy decisions and sensitive actions | [Audit logs](https://conto.finance/guides/audit-logs) |
| Policy testing | Dry-run and validate policy behavior | [Policy testing](https://conto.finance/guides/policy-testing) |
## Setup Check
Before making a payment, call the setup endpoint with the same SDK key your agent will use:
```bash
curl https://conto.finance/api/sdk/setup \
-H "Authorization: Bearer $CONTO_API_KEY"
```
The CLI wraps the same endpoint with pass/fail checks:
```bash
npx conto doctor
```
Check the customer-facing summary:
- the agent is available for payment calls
- at least one wallet is available and funded
- `scopes` includes `payments:request`
- execute-capable flows include `payments:execute`
- spending controls match the agent's expected envelope
## Generated Clients
The OpenAPI document is the contract for generated clients:
```bash
curl https://conto.finance/api/openapi > conto-openapi.json
```
Use it with your preferred generator or import it into tools like Postman, Bruno, or your API
portal. The interactive reference is available at [conto.finance/api-docs](https://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
Link: https://conto.finance/guides/choose-your-integration
Decide between SDK, REST, MCP, OpenClaw, Hermes, x402, and MPP.
### Recipes
Link: https://conto.finance/guides/recipes
Copy-paste API, SDK, skill, and payment examples.
### Authentication
Link: https://conto.finance/sdk/authentication
Understand SDK keys, org API keys, key types, and scopes.
### Testing Payments
Link: https://conto.finance/guides/testing-payments
Safely test with Tempo Testnet before moving money in production.