Circle

RESTful API at api.circle.com. Clean resource hierarchy: wallets → transfers → transactions. Idempotency keys on all POST operations for safe retries. Pagination via pageAfter cursor. Webhook events cover wallet balance changes, transfer completions, and payout status. Blockchain addresses generated deterministically per wallet for external funding. Consistent response envelope: {data: {...}} across all endpoints. API versioning via URL prefix.

Circle's APIs cover programmable USDC wallets, fiat on/off-ramps, and cross-border payouts. For agents, the most relevant surfaces are: Wallets API (create and fund programmable wallets per user or agent), Transfers API (move USDC between wallets), and Payouts API (ACH, wire, crypto payouts to external accounts). The Programmable Wallets (Web3 Services) enable agents to hold and spend USDC without needing private key management — Circle handles custody. Clean REST API, excellent docs, and sandbox environment make integration fast. One of the best agent-native payment APIs available. Confidence is docs-derived.

API key auth via Authorization: Bearer header. Entity secret for server-side signing of sensitive operations (wallet creation, high-value transfers). Separate sandbox vs. production API keys. Webhook signature verification via HMAC-SHA256. IP allowlisting available on enterprise plans. Entity secret pattern adds a second factor for high-value operations without requiring full key rotation. Permission scopes available on API keys.

developers.circle.com has some of the best API documentation in the fintech space: conceptual guides, workflow tutorials, full API reference with request/response examples, and a Postman collection. Sandbox environment mirrors production with test USDC. SDKs for Node.js and Python. Getting started is fast — first wallet and transfer achievable within minutes of obtaining a sandbox key.

Structured error responses: HTTP status code + JSON body with code (machine-readable), message (human-readable), and errors array for validation failures. Documented error codes for common cases (insufficient funds, invalid address, etc.). Rate limits documented per endpoint category. Blockchain settlement adds latency variance; Circle surfaces this via transfer status lifecycle (pending → confirmed → complete). Retry-After headers on 429 responses.