What is CodeSpar?

CodeSpar is commerce infrastructure for AI agents in Latin America. We provide a single SDK and a unified session model that lets your AI agents process payments, issue invoices, ship packages, send notifications, and interact with ERPs -- without integrating dozens of regional APIs yourself.

Think of CodeSpar as the Stripe for AI agent commerce. Where Stripe unified web payments behind one API, CodeSpar unifies the entire Latin American commerce stack -- Pix, boleto, Nota Fiscal, Correios, Mercado Envios, WhatsApp Business, and more -- behind one SDK call that any AI agent can invoke.

import { CodeSpar } from "@codespar/sdk";

const codespar = new CodeSpar({ apiKey: process.env.CODESPAR_API_KEY });
const session = await codespar.sessions.create({
  servers: ["stripe", "mercadopago", "correios"],
});

const tools = await session.tools();
// 24 tools ready for your agent to call

Who is CodeSpar for?

What can you build?

Architecture

CodeSpar sits between your AI agent and 57 regional commerce APIs. The architecture has four layers:

Your Agent (Claude, GPT, Gemini, LangChain, CrewAI, or any MCP client)
    |
    v
@codespar/sdk  <-- 12 Adapters: claude, openai, vercel, langchain, google-genai, mastra, crewai, autogen, llama-index, letta, camel, mcp
    |
    v
CodeSpar API (api.codespar.dev)
    |                                  Routing, auth, usage tracking, billing
    v
57 MCP Servers
    |
    +-- Payments:    Zoop, Asaas, Pagar.me, PagSeguro, Cielo, Stone, EFI, iugu, Vindi, Celcoin, EBANX, Mercado Pago, Conekta, Wompi
    +-- Fiscal:      Nuvem Fiscal, Focus NF-e, Facturapi, AFIP, Siigo
    +-- Logistics:   Melhor Envio, Correios, Skydropx, Andreani, Coordinadora
    +-- Messaging:   Z-API, Evolution API, Zenvia, Take Blip, RD Station
    +-- Banking:     Stark Bank, Inter, Nubank, Nequi, BCRA, Pix BCB, Open Finance, STP/SPEI
    +-- ERP:         Omie, Bling, Tiny, Conta Azul, Colppy, Alegra, Bind ERP, Belvo
    +-- E-Commerce:  VTEX, Mercado Libre, Tienda Nube
    +-- Crypto:      Mercado Bitcoin, Bitso, Circle, UnblockPay
    +-- Protocols:   Stripe ACP, Google UCP, x402, AP2
    +-- Data:        BrasilAPI

How it flows:

1. Your agent receives a user request (e.g., "Create a R$49.90 checkout link for the Pro Plan").
2. The adapter converts the agent's tool call into a CodeSpar SDK call.
3. The SDK sends the request to api.codespar.dev, which authenticates, routes, and tracks usage.
4. The API forwards the call to the appropriate MCP server (e.g., the Stripe MCP server).
5. The MCP server executes the operation against the regional API and returns structured results.
6. Results flow back through the stack to your agent, which presents them to the user.

The Complete Loop

Every agent interaction follows a consistent three-phase pattern we call the Complete Loop:

const result = await session.execute({
  name: "codespar_discover",
  arguments: { domain: "payments" },
});

{
  "domain": "payments",
  "servers": ["stripe", "mercadopago", "asaas", "pagarme"],
  "tools": [
    { "name": "codespar_checkout", "description": "Create a checkout session for a product or service" },
    { "name": "codespar_pay", "description": "Process a payment via Pix, boleto, or card" }
  ],
  "capabilities": ["pix", "boleto", "credit_card", "checkout_link"]
}

const result = await session.execute({
  name: "codespar_checkout",
  arguments: {
    provider: "stripe",
    amount: 4990,
    currency: "BRL",
    description: "Pro Plan",
    payment_methods: ["pix", "card"],
  },
});

{
  "checkout_id": "chk_abc123",
  "url": "https://checkout.stripe.com/c/pay/cs_live_...",
  "amount": 4990,
  "currency": "BRL",
  "status": "open",
  "expires_at": "2026-04-15T23:59:59Z"
}

// Chain: send the checkout link via WhatsApp
const notification = await session.execute({
  name: "codespar_notify",
  arguments: {
    channel: "whatsapp",
    to: "+5511999887766",
    template: "checkout_link",
    variables: {
      customer_name: "Maria",
      checkout_url: result.url,
      amount: "R$49.90",
    },
  },
});

The 6 Meta-Tools

Meta-tools are high-level operations that abstract the underlying MCP servers. Instead of calling provider-specific endpoints, your agent calls a meta-tool and CodeSpar handles the routing.

Key Numbers

• 57 MCP servers across 10 domains: payments, fiscal, logistics, messaging, banking, ERP, e-commerce, crypto, public data, and agentic commerce protocols
• 6 meta-tools that abstract all server routing and provide a consistent interface
• 12 framework adapters -- Claude, OpenAI, Vercel AI SDK, LangChain, Google Gemini, Mastra, CrewAI, AutoGen, LlamaIndex, Letta, CAMEL-AI, and MCP
• 1 SDK -- @codespar/sdk@0.2.0 on npm, with a single session model for all operations
• 71 packages on npm under the @codespar scope
• 2 environments -- csk_test_ keys for sandbox with mock data, csk_live_ for production

Getting Started