Guides9 min read
Updated 2026.10.06 · Fabiano Cruz
MCP vs. API: what changes when the caller is an agent
An API is written for the developer who wires two programs. MCP is read by the model at runtime. The differences follow from that.
Read articleBlog
Ideas and guides for agents that do business.
Featured
More to explore
Browse all articlesIdeas5 min read
Agents Can Build Anything. Then They Hit the Paywall.
Every service an agent uses in production asks for an account, auth and a payment. What sits underneath: a wallet, a mandate and more than one rail.
All articles
19 articles
Ideas5 min read
The Rails Will Stay Plural. The Authorization Doesn't Have To.
Pix, SPEI and UPI have their own infrastructure and rules, so no private ledger will absorb them. What can hold on every rail is the authorization.
Ideas7 min read
One Authorization, Any Rail
Machine payments grew up in crypto and in English. The post's thesis: a signed Pix mandate can play the role the x402 handshake plays in crypto.
Ideas5 min read
Agents Can Build Anything. Then They Hit the Paywall.
Every service an agent uses in production asks for an account, auth and a payment. What sits underneath: a wallet, a mandate and more than one rail.
Guides9 min read
MCP vs. API: what changes when the caller is an agent
An API is written for the developer who wires two programs. MCP is read by the model at runtime. The differences follow from that.
Ideas21 min read
MCP Is a Commodity. Here's What Isn't.
Seven layers between an agent and a completed transaction, and why the moat is what gets built on top of MCP.
Guides9 min read
How to Build a Payment Agent with CodeSpar
A walkthrough of a session, a Pix charge, an NF-e and a WhatsApp notice from one agent, with examples for @codespar/sdk 0.16.11.
Latin America13 min read
The Complete Loop: How AI Agents Run a Business in Latin America
The flow the article describes, from a Pix charge to bank reconciliation, and why the region is different. Not every step in it is implemented and verified in the product.
Engineering9 min read
Session-first: How We Designed the CodeSpar SDK
Sessions as context containers, a small set of meta tools, and managed auth.
Guides10 min read
The Complete Loop in 5 Lines of Code
A step-by-step run with the SDK, from payment to reconciliation.
Ideas10 min read
The commerce layer for AI agents doesn't exist yet. We're building it.
Agents break when asked to charge via Pix or issue an invoice. The founding essay on why CodeSpar starts with commerce in Latin America.
Ideas24 min read
207 companies. $2.4B deployed. Zero in Latin America.
A map of agentic commerce: value-chain layers, competing protocols, funding, and Latin America's position in the survey it presents.
Ideas20 min read
Six protocols. The wrong question is which one wins.
The tool layer matters regardless of which payment protocol wins.
Latin America18 min read
Why instant payment rails are better for AI agents than cards
Instant rails fit agent payments better than card-on-file.
Latin America16 min read
How we taught an AI agent to issue electronic invoices in LatAm
Each country's invoice format, wrapped as a tool an agent can call.
Engineering12 min read
Building the Largest MCP Catalog for Latin America
Why Latin American commerce APIs had no MCP servers, how the catalog was built, and what we learned along the way.
- Illustrative
Latin America23 min read
WhatsApp is the operating system for commerce in Brazil. Not a channel. The platform.
Where businesses already talk to customers, agents can close the order.
Guides15 min read
10 things you can build with CodeSpar today
Ten use-case designs for agents using the CodeSpar MCP catalog and SDK, with business context and conceptual code sketches.
Engineering25 min read
We open sourced our entire MCP catalog. Here's why MIT — not AGPL, not SSPL, not BSL.
Why the MCP servers are MIT licensed, and what stays proprietary.