Transaction rails for AI agents.
Start with sandbox cash, then add wallets, checkout credentials, transfers, webhooks, and Solana USDC payout intents. Guardrails are built in, but the product center is the money API your agents can build on.
Features
Agent wallets
Give each agent or workflow a funded wallet object with balance, keys, transaction history, and optional guardrails.
Checkout credentials
Create a checkout intent, authorize it, and mint a scoped payment credential for the exact purchase path.
USDC payouts
Use payout intents for Solana USDC sends. Spending keys create and read; your app decides when to require review.
Sandbox money
Use din_test_ keys and the USD faucet to validate wallets, checkout, cards, and webhooks without real money.
Transfers
Move value between Dino workspaces and agent wallets with idempotent APIs, payment codes, and lifecycle events.
Spending keys
Agents get a din_ key, not your card number, wallet seed, bank login, or team admin credential. Rotate or revoke any time.
Append-only ledger
Every request, check, approval, and payment is written to a ledger you can query later. Nothing is deleted.
Webhooks
Subscribe to spend_request, purchase_intent, transfer, and crypto_payout lifecycle events from one console.
Guardrails
Budgets, limits, merchant rules, approval thresholds, and audit controls are built in but do not have to be your app's center.
Revoke keys instantly
One command to revoke a key. The agent can no longer make purchases. Past entries stay in the ledger.
Check rails from the terminal
Query balances, transactions, payout status, pending reviews, and webhook delivery without opening a dashboard.
Export the ledger
Export spend records by agent, time range, or merchant. CSV or structured JSON for your own tools.
Cash and crypto webhooks
Reconcile spend_request, purchase_intent, and crypto_payout events from the same developer console.
Works with MCP clients
Cursor, Claude, Windsurf, Raycast, or your own agent can sit behind the same trusted tool boundary.
Possibilities
Ask about agent transactions
Ask Claude what your agents moved this week, which payouts are pending, or how much balance is left per wallet. Get structured answers back.
Pay while you code
Your Cursor agent needs an API key or tool subscription. It creates a transaction through Dino, and your app's guardrails decide the path.
Approve overnight purchases
OpenClaw runs overnight tasks that need to spend. Approvals under your threshold go through automatically. Anything over lands in your queue at morning.
Daily budget report
Every morning, Zapier pulls the ledger for all agent accounts and posts a spend summary to Slack. No one has to ask.
Build a custom money workflow
Use the public REST API to build exactly the agent you need. Hold balance, create payment credentials, send USDC, transfer funds, and reconcile webhooks.
One protocol, every rail
MCP is the long-term natural-language surface. Start with the REST contract today, then layer wallet, card, transfer, and payout tools onto the same ledger.
Approve in a keystroke
Hit a shortcut, see pending approvals, approve or deny with one key. Faster than opening a dashboard.
Hands-free purchasing
Manus runs long tasks that need to buy tools or compute. Dino handles the money movement and guardrails so you do not wire raw credentials into the agent.
Automate with a cron job
A 10-line script that runs nightly: fetch pending approvals, approve anything under $50, push the rest to Slack. No UI needed.
CLI
- ◇ Public transaction API today
- ◇ Sandbox faucet for USD test cash
- ◇ Check balances and status
- ◇ Idempotency for safe retries
- ◇ Approval URLs for human review
- ◇ Ledger-backed transaction history
- ◇ Interactive demo (
dinobankwalkthrough)
Crypto
- ◇ Solana USDC payout intents over REST
- ◇ Devnet testing uses external chain faucets
- ◇ Spending keys create and read payout intents
- ◇ Dashboard or team API key handles operator review
- ◇ Webhooks report lifecycle status
Developer experience
- ◇ One canonical REST contract
- ◇ din_ spending keys, dba_ team keys, or OAuth / MCP
- ◇ Wallets, cards, payouts, and ledger in one flow
- ◇ OpenAPI-backed reference docs
- ◇ Additional surfaces roll out from the same contract
Infrastructure
Every spend request flows through Dino's rules before it is approved. The public REST contract is the source of truth for the other developer surfaces.
┌──────────────────┐
│ Agents │
└────────┬─────────┘
│
MCP / CLI / API
│
┌─────────────────────────────────────────────────────────┴─────────────────────────────────────────────────────────┐
│░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
│░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Dino ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
│░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
│░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Transaction rails for AI agents ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
│░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
└────────────┬────────────────┬──────────────┬──────────────┬──────────────┬──────────────┬─────────────────────────┘
│ │ │ │ │ │
▼ ▼ ▼ ▼ ▼ ▼
┌─────────────┐ ┌──────────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────────┐
│ Wallets │ │ Cards │ │ USDC │ │Transfers │ │Webhooks │ │ Guardrails │
└─────────────┘ └──────────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────────┘Get started
Start with a sandbox key and test cash, then choose the cash or crypto path your agent actually needs.