MCP Server
Connect RobotMoney to your agent stack.
Use MCP to give Claude, ChatGPT, custom agents, or other MCP-compatible systems access to accounts, payment actions, transaction context, and policy-controlled tools.
FOR BUILDERS
One API between your agent and money.
Provision agent accounts, apply programmable rules, authorize payments, and move money across multiple rails with one API.
INTEGRATE
Choose how your agents connect.
REST API
Build RobotMoney directly into your product.
Create agent accounts, request payment authorization, manage policies, initiate transactions, and retrieve structured receipts programmatically.
SDKs
Ship faster with typed integrations.
Use native SDKs to manage agents, policies, payments, and events without wiring every endpoint yourself.
QUICKSTART
From zero to your first agent payment in minutes.
01 — GET A SANDBOX KEY
Start without moving real money.
Create a sandbox project and test with synthetic accounts, transactions, and policies.
02 — CREATE AN AGENT ACCOUNT
Give the agent its own financial identity.
Provision an account with limits, allowed actions, payment methods, and approval rules.
03 — AUTHORIZE A PAYMENT
Ask RobotMoney before money moves.
Send the transaction context. RobotMoney returns an allow, hold, or reject decision with the reason and applicable policy.
JAVASCRIPT
const payment = await robotmoney.payments.create({
agent_id: "agent_procurement_01",
amount: 18700,
currency: "USD",
recipient: "northwind_co",
reason: "Invoice #1042"
});JSON
Response:
{
"decision": "hold",
"reason": "vendor_bank_details_changed",
"policy": "approval_required_for_changed_bank_details",
"requires_approval": true
}Every request returns a decision, reason, applicable policy, and transaction record.
04 — EXECUTE + RECORD
Move the money and keep the proof.
Approved transactions execute through the selected rail and return a structured transaction receipt.
DEVELOPER PRICING
Build free. Pay as your agents transact.
Start in sandbox at no cost. Move to production when you’re ready, with usage-based pricing for APIs, accounts, and payments.
Start In Sandbox
Build free. Go live when you're ready.
Test every payment with synthetic data. Production stays propose-only until your policy and approval rules are in place.
SANDBOX
Free to build
Test agents, policies, and payment flows without moving real money.
API + MCP
Usage-based
Pay for the infrastructure your agents actually use.
PAYMENTS
Transaction-based
Fees scale with the money your agents move.
ENTERPRISE
Custom
Volume pricing, additional rails, compliance requirements, and dedicated support.
THE RESOURCES
Everything you need to ship.
The reference material, guides, and tooling developers need to build on RobotMoney.
API.ROBOTMONEY.COM
API Reference
Every tool, every field, every error. The typed contract for the whole catalog.
DOCS.ROBOTMONEY.COM
Guides And Tutorials
From first call to production, including the propose-sign-settle lifecycle.
STATUS.ROBOTMONEY.COM
Status And Changelog
Live uptime, versioning policy, and what shipped. Breaking changes never ship unversioned.
FAQ
Developer questions.
Everything you need to know before your first call, and a few things after.
How do I connect an agent to RobotMoney?
Developers can integrate RobotMoney through its API, MCP interface, and supported SDKs, depending on the application and agent architecture.
Can I create a separate account for every agent?
Yes. Agent accounts can provide separate identities, permissions, limits, payment methods, and transaction histories so agents do not need to share broad financial credentials.
How does payment authorization work?
When an agent requests a transaction, RobotMoney can evaluate the payment against its account permissions, business context, configured policies, and approval requirements before execution.
Can I define payment policies programmatically?
Yes. Policies can define things such as transaction limits, approved counterparties, payment types, approval thresholds, and conditions that cause a payment to be held or rejected.
What payment rails can I access through the API?
RobotMoney is designed as a rail-agnostic layer spanning payment methods such as cards, ACH or bank transfers, wires, stablecoins, x402, and partner payment APIs.
Does RobotMoney return the reason behind a payment decision?
The goal is for payment decisions to be explainable. Applications can receive the transaction outcome together with the policy or condition responsible for allowing, holding, or rejecting it.
How are transactions and agent activity recorded?
RobotMoney maintains transaction and decision records so developers can trace the agent, payment, applicable rules, authorization, and execution. Where supported, evidence can also be anchored on-chain.
Build agents that can move money safely.
Accounts, controls, payment rails, and proof, all behind one integration.