Skip to main content
code<spar>
DocsGuidesServersSandbox
Documentation@codespar/sdk v0.16.0

The agentic OS for money movement in Latin America.

Commerce checkout, procurement, payroll, treasury and cross-border, over the rails the region actually uses (Pix, boleto, NF-e, WhatsApp, SPEI), behind one SDK and fifteen meta-tools, governed by signed mandates.

Start here

Pick the thing you came to do. Each of these ends with a real response, not a diagram.

Browse the HTTP API

All 227 operations, generated from the OpenAPI document the API serves. Everything works over plain REST — no SDK required.

Make your first call

From a key to a response in three curls, with nothing installed.

Get paid for an API call

Put a paywall in front of an endpoint and take the first paid call.

Let an agent spend

Give an agent an allowance instead of a key. It pays inside the cap you signed.

Charge over Pix

Issue a Pix charge, receive it, and see the credit land in the ledger.

Connect an agent over MCP

One hosted URL, 15 meta-tools, no HTTP client to write. Claude Code, Cursor, Windsurf or any client that speaks it.

Set up your environment

SDK, CLI, adapters, test mode, and the machine-readable contracts.

You get paid.
The sell side: price what your endpoints and agents do, and settle to a wallet you control. Gate is live on Base mainnet with real USDC. Meter is in beta during final mainnet validation. Collect links are in early access.
You send agents out to spend.
The buy side: give an agent an allowance instead of an API key. It pays inside the cap you signed, and off-mission spend is refused before money moves.
The trust layer
Both sides run on the same six primitives. They are not add-ons: every product above is a different door into the same governed runtime.

Four ways in, one runtime

The same governed runtime answers all four. Pick by what you are building with, not by what you are building.

Plain REST

227 operations, generated from the OpenAPI document the API serves at /openapi.json. No SDK, no client library, any language — Go, Java, .NET, PHP. Start at `codespar whoami`'s route and follow the resource you need.

TypeScript or Python SDK

A typed client over the same operations, plus the session and meta-tool ergonomics. `npm i @codespar/sdk` or `pip install codespar`.

MCP

One hosted URL and 15 meta-tools, for Claude Code, Cursor, Windsurf or any client that speaks the protocol. No HTTP client to write.

The CLI

103 commands over the same surface, for exploring the catalog, minting a mandate, or debugging a session from a terminal.

Integrating without our SDK?

Everything the SDK does is an HTTP call you can make yourself, and mandate signing is server-side — you never hold a signing key. The HTTP reference and the served OpenAPI document are the complete contract; point your own generator at it.

See both sides run

Same infrastructure, same governance. Watch the direction of money flip while the mandate gate, the router, and the receipt stay identical.

↘ You get paid

agent · seller agent
sb_sell_idx
Charge R$249 for the Pro Plan and send the Pix code to +55 11 99988-7766 on WhatsApp.
Cobrança criada. Enviando o copia-e-cola no WhatsApp do cliente...
Enviado. Quando o Pix liquidar, emito a NFS-e e te aviso.
codespar_charge → pix✓ done620ms
codespar_notify → whatsapp✓ done340ms
codespar_invoice → nfse● runningon settle
inbound charge · fiscal document on settlement · same audit chainRun this cookbook in Sandbox →

↗ You send agents out to spend

agent · buyer agent
sb_buy_idx
Buy the cheapest ração golden 15kg at Cobasi and pay with my wallet.
Encontrei por R$ 179,90. Checkout da loja pronto, Pix gerado. Pagando com a carteira, dentro do mandato (cap R$ 500/mês)...
Pago. Recibo assinado rcp_8f2a gravado no ledger. Restante do mandato: R$ 320,10.
codespar_shop → checkout✓ done84s
codespar_wallet → balance✓ done180ms
codespar_pay → pix✓ done1.4s
mandate-gated spend · signed receipt · audit chainRun this cookbook in Sandbox →

✦ Either way, the same artifact

Every settled move on either side seals a signed receipt binding permission, settlement, and proof:

Agentic receipt
rcp_8f2a41c9
signed · Ed25519
Mandate — the permission
mandatecm_gWEZO68q
capBRL 500.00 / month
spent after thisBRL 179.90
Payment — the settlement
railpix
amountBRL 179.90
end-to-end refE18236120…7401
Delivery — the proof
evidencestore order #1049-B confirmed
chain a91c…04be 7d2f…c918verifiable offline via did:web
A signed agentic receipt binding the mandate, the settled payment, and the delivery proof, chained into the audit ledger and verifiable offline.
Browse by commerce domain
A second lens on the same rails: the domains below serve both sides. A charge and a payment ride the same Pix providers. Pick a domain to jump to the catalog, the meta-tool, and the cookbook.
Edit on GitHub

Your first call

From an API key to a successful authenticated request in three curls, before you install anything.

On this page

Start hereFour ways in, one runtimeSee both sides run↘ You get paid↗ You send agents out to spend✦ Either way, the same artifact
Introduction | CodeSpar