Embed payments for your users' agents with the Partner API
The AgentBank Partner API lets your backend offer payments to verified end users: fiat to crypto, crypto to fiat, or fiat to fiat through an intermediate crypto asset. You provide the final recipient; AgentBank handles routing and returns the funding instruction and payment state.
Last reviewed 2026-10-03
Who this is for
- Agent platforms whose users' agents need to pay suppliers, contractors or bills in local currency.
- Payroll, procurement and marketplace products adding bank payouts to markets their current provider does not reach.
- Fintech apps that want on-ramp and off-ramp routes behind their own interface.
If you are connecting a single assistant rather than building for your own end users, use MCP instead. See For developers.
The integration in six steps
- 01
Provision
Receive merchant credentials and an Ed25519 signing key for your backend. Onboarding
- 02
Create the end user
Submit a complete KYC record and artifacts; apply versioned partial updates later. End-user KYC
- 03
Confirm rail readiness
Wait for provider KYC forwarding and read which fiat rails the user is eligible for before creating a payment. Rail readiness
- 04
Verify the recipient
Parse a QR or validate a direct bank-transfer recipient without storing it. Verify bank recipient
- 05
Estimate and create
Get a non-binding, readiness-filtered quote, then create one on-ramp, off-ramp or fiat-to-fiat payment with an idempotency key. Payments
- 06
Fund, track, reconcile
Present the exact funding instruction, follow the payment to a terminal state, and receive HMAC-signed webhooks. Funding and tracking
What you get
| Capability | Detail |
|---|---|
| Payment shapes | On-ramp (fiat to crypto), off-ramp (crypto to fiat), fiat to fiat through an explicit settlement asset such as USDC. |
| Recipient instruments | Direct bank transfer, QR, mobile money, with a uniform recipient schema per rail. Schemas |
| Discovery | Live currency catalog, fiat payment capabilities per direction, and a curated bank-name directory per rail. List fiat payment capabilities |
| Compliance | Core-issued end users with full KYC; AgentBank is operated by Thinking Horizon, Inc., a FinCEN-registered Money Services Business. |
| Reliability | Idempotent creation, safe retries, conflict resolution, durable webhook delivery with one-time HMAC secrets. Errors and idempotency |
| Environments | Isolated sandbox and production hosts with promotion guidance. Environments |
Coverage
Local banking rails in 50+ countries. Exact routes, directions and recipient instruments are read live from the discovery endpoints rather than from a static list, so your product only offers what is available to that end user at that moment.
Commercials and next step
Pricing is quoted per integration. Start with the Partner API quickstart, then contact [email protected] with your use case, markets and expected payment shapes.
Frequently asked questions
- Who holds funds during a payment?
- AgentBank returns an exact funding instruction for each payment. Payment and banking partners may receive or process funds while completing a supported payment. AgentBank does not take custody of your end users' wallet funds.
- Do I need to run KYC myself?
- You collect the KYC record and artifacts in your product and submit them to create a Core-issued end user. AgentBank forwards to providers and reports rail readiness back to you.
- Can I test before going live?
- Yes. The sandbox host is isolated from production and supports the full provisioning-to-payment path.