Your agent is ready to do business. Your money isn't.
One account where agents pay and get paid. Mandates you set. Payments that settle. An audit trail for every payment.
Test keys are free.
Sandbox run · demo data
Day one
Three things it does on day one.
Sell on WhatsApp, pay a supplier, receive a Pix. Nobody types a card number.
WhatsApp assistant
A customer asks on WhatsApp. The agent closes the sale in the chat, with a Pix.
The Pix code arrives in the thread and is paid before the conversation ends.
Supplier payments
The agent pays a supplier's boleto inside the mandate.
Payments run within your mandate. Requests matching your approval rules wait for review; requests outside hard limits are blocked.
Collections
The Pix lands on the same account as the spend.
Money in and money out share one payment history.
Sandbox run · demo data
How it works
How a payment moves.
CodeSpar is not the model. The model prepares the intent; mandates, limits, review and records live in CodeSpar.
01
Connect
Hosted MCP or SDK. Works with Claude Code, Cursor, Codex CLI and any client that speaks MCP.
02
Mandate
A signed spend authority: cap, scope, expiry. The model can't rewrite it.
03
Payment method
One call. CodeSpar picks the payment method that fits: Pix, boleto, card or USDC.
04
Record
Every governed action is recorded in a hash-chained audit trail. Every settled spend gets a signed receipt.
The problem
Money is the last thing agents can't move.
Money out, stuck
The agent compares four offers, picks the best one, and stops. Someone copies a boleto line into a bank app and loses the afternoon. The supplier waits. The deal waits.
Money in, lost
A customer's agent is ready to buy and your checkout asks for a human. A calling agent would pay for your API and you give it away or turn it down.
Govern and prove
Budgets, rate limits and approvals, checked before the call runs.
Sandbox run · demo data
01
Spending rules
Payments run within your mandate. Requests matching your approval rules wait for review; requests outside hard limits are blocked.
mnd_22sh_v2 · you set the values demo
limit per transaction R$ 3,000
hard budget R$ 20,000 per month
outside hard limits blocked
- Payment cap
- Period budget
- Allowed recipients
- Rate limit
02
Approvals
Requests matching your approval rules wait for review. A person decides before money moves.
- Approval rules
- Expiry
- Status and history
- Verified approverrolling out
03
Payment records
Every settled spend gets a signed receipt anyone can verify. The audit trail records every governed action.
ed25519:9f2c…7ab1 · verified
- Signed receipt
- Audit trail export
- CSV exportrolling out
- Reconciliationrolling out
One flow, end to end
The agent finds the invoice, checks your rules, pays, returns the receipt.
Sandbox run · demo data
Machine to machine
Agents pay per call and get paid per tool.
The same wallet buys compute for your agent and charges other agents for yours. Every line carries the mandate that allowed it.
Money out
The agent buys September compute from Nimbus Cloud, under its mandate.
Money in
Another agent calls get_quote. 402, it pays, your tool answers.
Sandbox run · demo data
What you start selling
Agents are ready to buy from you. Your checkout isn't ready for them.
Let them pay for the order or the API call, then reconcile it in one payment history.
Checkout for agents
Shop · Collect
A customer asks on WhatsApp, your agent assembles the cart, and a Pix closes the sale without leaving the thread, paid by the customer or by their agent, same payment history.
Charge per API call
Gate · Bill
Put a price on the endpoint. The calling agent pays per request under its mandate, x402 or the payment method you validate, and every call is recorded.
Links and payouts
Collect · Pay
Send a link any buyer can pay. Pay suppliers, sellers or other agents on Pix, boleto, card or USDC, with your rules and a receipt each time.
Sandbox run · demo data
Works where your agent works
Same account, same policy, in your coder or in your runtime.
- 01Sign up and create a project with a csk_test_ key.
- 02Point the hosted MCP endpoint at Claude Code, Cursor or any MCP client, or use the SDK and CLI.
- 03Give the agent a test mandate and ask for a test purchase.
- 04Watch the proposal, the state and the receipt in the dashboard.
- 01Open the business account, sandbox first. No regulated account is needed to start.
- 02Connect through the API, the SDK or the hosted MCP.
- 03Set a mandate per agent: limits, review rules, revocation.
- 04Reconcile proposals, receipts and the payment history. KYC/KYB before production.
The platform
Four layers between intent and money.
Identity and governance
Agents · Mandates · Guardrails · Audit trail
Mandates and consent, guardrails, approvals and revocation. Sessions stay scoped; every action carries its proposal ID and lands in the audit trail.
Money and banking
Collect · Pay · Wallet · Cards
Charges and checkout, payouts, Pix, boleto, card and USDC. Wallet, transfers and one payment history across all of it.
Monetization and commerce
Gate · Bill · Shop · Spaces
Access gates and per-call charging, an API paywall for machine spend, and a full seller checkout with invoices and fulfillment.
Developer surface
Hosted MCP · SDK · CLI
Hosted MCP, SDK for Node and Python, REST and OpenAPI, CLI, server catalog, webhooks and test keys.
One book
From a two-cent call to a month of GPU hours.
Same mandate, same payment methods, same receipt. The amount changes; the rules don't.
The mandate is the limit
Limits per purchase, per day and per counterparty, checked on our servers, outside the model.
The receipt is the proof
Every settlement is signed and tied to the proposal and approval that caused it.
Review is where you come in
A boleto above the per-transaction limit waits for one tap in the Dashboard. Within it, nothing asks.
Sandbox run · demo data