Skip to main content
Platform overview

The platform, end-to-end.On one page.

Three layers — SDK, orchestration, ledger. Six meta-tools. Every LatAm commerce API. All the safety rails between your agent and a settled transaction. Below is the whole map.

Live architecturePlatform
agent → ledger · five gates
Agent
Claude · OpenAI · Vercel AI · any MCP client
Intent· natural language
SDK · Session
6 meta-tools, framework-agnostic
discover
checkout
pay
invoice
ship
notify
Orchestration
Five gates before any rail is touched
policy
mandate
route
execute
audit
MCP servers
Every commerce API, MIT · on npm
payments
fiscal
logistics
messaging
erp
Rails
Real providers, real money
Pix
Stripe
Circle
WhatsApp
Omie
Ledger
Hash chain · replayable · auditor-ready
sealed receipt
Three layers

SDK, orchestration, ledger.Each one is substitutable.

The whole point of the split is that nothing is monolithic. Self-host the SDK and wire your own orchestration. Use the orchestration without the ledger. Bring our ledger to your own stack. Pick any shape.

01
Layer

SDK

How agents reach CodeSpar

Session-first developer experience. One object holds auth, tools, and ledger hooks for a single agent interaction. Six meta-tools instead of 99 raw ones. Adapters for Claude, OpenAI, Vercel AI, and any MCP client.

  • Sessions · isolated contexts with scoped credentials
  • 6 meta-tools · discover, checkout, pay, invoice, ship, notify
  • Framework adapters · Claude, OpenAI, Vercel, MCP
  • Managed auth · OAuth, API keys, token refresh, lifecycle
See the SDK
02
Layer

Orchestration

What keeps money moving safely

Five guardrails between the agent's intent and any rail call: policy check, mandate verification, route selection, execute with retries, seal to the ledger. Everything here is managed, versioned, and revocable.

  • Policy engine · budgets, deny-lists, time windows
  • HMAC mandates · signed, scoped, revocable
  • Payment router · cheapest-route optimization
  • Escrow · milestone-based release
See the guardrails
03
Layer

Ledger

Why every decision is replayable

Every check, route, execution, rollback, and revoke is hashed into an append-only chain. Tamper-evident by construction. Exportable to SIEM or an auditor as signed JSON in one command. Your receipts cannot lie.

  • SHA-256 hash chain · chained per-org
  • Immutable · tamper-evident · replayable
  • Exports · Datadog, Splunk, S3, JSON, CSV
  • Auditor-ready receipts per transaction
Read the security model
The stack

What sits underneath.Rails, primitives, protocols.

Three groups. Every integration is opt-in and swappable — same meta-tool, different provider underneath.

Rails
Money movement primitives
  • Instant payments
    Pix BCB · SPEI · Transferencias 3.0
  • Cards
    Stripe · Zoop · PagSeguro · Cielo · Asaas
  • Stablecoins
    Circle USDC · Mercado Bitcoin · Bitso
  • Bank transfers
    Stark Bank · Open Finance · BCB
Commerce primitives
Invoice, ship, notify, sync
  • Fiscal docs
    Nuvem Fiscal · Focus NFe · Conta Azul
  • Logistics
    Melhor Envio · Correios · VTEX
  • Messaging
    Evolution · Z-API · Twilio · Zenvia
  • ERP
    Omie · Bling · Tiny
Agent protocols
Agent-native payment standards
  • Stripe ACP
    Agent checkout inline in chat
  • Google UCP
    Unified commerce protocol
  • x402
    HTTP 402 · machine-to-machine
  • AP2
    Agent-to-agent scoped spend
How you pay

Open source is free.You pay when transactions settle.

MCP servers and the SDK are MIT-licensed and published on npm. Orchestration is usage-based — $0.10 per settled transaction, plus 0.5% on cross-border FX. No minimums. No setup fee.

See the whole thing running.

Open the Sandbox and run a real transaction in under a minute. Or book a demo and we walk you through it end-to-end.