Skip to main content
code<spar>
DocsCookbooksServersSandbox
Documentation@codespar/sdk v0.16.11

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 14 meta-tools, governed by signed mandates.

Sell side
Quickstart: get paid
Put an x402 paywall in front of your API and take the first paid call in five minutes.
Buy side
Quickstart: buyer agent
Give your coding agent a governed wallet and let it shop and pay under a signed mandate.
Concepts
How CodeSpar Works
Architecture, request lifecycle, and the Complete Loop explained.

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 340 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, 14 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

340 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 14 meta-tools, for Claude Code, Cursor, Windsurf or any client that speaks the protocol. No HTTP client to write.

The CLI

134 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

The same infrastructure with the money going the other way, side by side: the sell loop, the buy loop, and the one artifact both produce.

TOUR
See both sides run
Two agent loops end to end, and the receipt that closes each one.
Edit on GitHub

See both sides run

The same infrastructure with the money going the other way. Watch the mandate gate, the router and the receipt stay identical while the direction flips.

On this page

Start hereFour ways in, one runtimeSee both sides run
Introduction | CodeSpar