Mercado Pago
Mercado Pago is the payments and financial-services arm of Mercado Libre, Latin America's largest e-commerce and fintech platform. Founded in 2003, it processes a substantial share of LatAm digital payments across Brazil (PIX, Boleto, cards), Argentina, Mexico (SPEI, OXXO), Chile, Colombia, Peru, and Uruguay, with consumer wallet, merchant acquiring, card issuing, lending, and crypto products layered on top. The developer portal at developers.mercadopago.com exposes a deep payments stack — Checkout Pro (hosted), Checkout Bricks (composable web components), Checkout API (full server-side control), Orders API (next-gen checkout), Subscriptions, Payment Links, Point (in-person card readers), and QR payments — backed by REST APIs and official SDKs in Node.js / TypeScript, Python, PHP, Ruby, Java, .NET, Go, iOS, and Android, plus a CLI, an MCP server for AI agents, e-commerce plugins (WooCommerce, VTEX, Tiendanube, Shopify), and an n8n integration. Regional developer portals (.com.ar, .com.br, .com.mx, .com.cl, .com.co, .com.pe, .com.uy) localise docs and pricing per LATAM market.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Mercado Pago the way a machine reads it — 68 machine-readable artifacts across 44 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mercado Pago scores 54.0/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Mercado Pago
Each block below is one kind of artifact we hold for Mercado Pago. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 44
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mercado Pago Checkout Pro
Hosted, pre-configured checkout experience. Merchants create a preference via API, then redirect the buyer to a Mercado Pago hosted page that handles UI, payment-method selectio...
Mercado Pago Checkout Bricks
Composable web components ("bricks") merchants embed in their own UI — card form, wallet, payment-method picker, status screen, security code. Lets merchants assemble a branded ...
Mercado Pago Checkout API
Full server-side checkout control. Tokenise cards client-side, create a payment server-side, manage 3DS challenges, handle capture, refund, and installments — all without redire...
Mercado Pago Orders API
Next-generation unified Orders API consolidating payments, captures, refunds, and transactions under a single resource. Supports multi-method orders, partial captures, partial r...
Mercado Pago Subscriptions API
Recurring payment subscriptions (preapproval) with scheduling, shared plans, free trial, proration, and pause / resume / cancel. Supports both subscription plans (preapproval_pl...
Mercado Pago Payment Links API
No-code / low-code link generation for collecting a one-off or recurring payment via shareable URL or button — SMS, WhatsApp, email, social.
Mercado Pago Customers & Cards API
Manage stored customers and tokenised cards for one-click and recurring payments. CRUD for customers, addresses, and card tokens.
Mercado Pago Merchant Orders API
Aggregate a preference + its payments into a single merchant_order resource for reconciliation, multi-payment handling, and order lifecycle.
Mercado Pago Point API (POS)
Integrates merchant systems with Mercado Pago Point card readers for in-person payments. Push an amount to a paired terminal, manage stores, points-of-sale, and terminals, and r...
Mercado Pago QR API
Static and dynamic QR code APIs for in-person collection, with order-linked status retrieval and webhook callbacks. Underpins the Mercado Pago wallet QR pay flow.
Mercado Pago Chargebacks API
Retrieve and respond to chargebacks, including dispute reason codes and lifecycle states.
Mercado Pago Claims & Disputes API
Post-sale claims, mediations, evidence upload, messages, and notification retrieval for resolving buyer disputes.
Mercado Pago Reports API
Generate, configure, and download release / settlement / account-money reports for reconciliation and accounting.
Mercado Pago OAuth 2.0 API
OAuth 2.0 authorisation-code flow for platform integrations: marketplaces and partners obtain delegated access tokens on behalf of merchants.
Mercado Pago Webhooks / Notifications
Event-driven notifications for payments, refunds, chargebacks, subscriptions, merchant orders, and account changes. Webhooks are signed with an x-signature header so receivers c...
Mercado Pago Node.js SDK
Official Node.js / TypeScript SDK wrapping the Mercado Pago REST APIs for payments, preferences, subscriptions, customers, cards, and merchant orders.
Mercado Pago Python SDK
Official Python SDK wrapping the Mercado Pago REST APIs.
Mercado Pago PHP SDK
Official PHP SDK wrapping the Mercado Pago REST APIs. Used by the WooCommerce plugin and most LATAM PHP merchant stacks.
Mercado Pago Ruby SDK
Official Ruby SDK wrapping the Mercado Pago REST APIs.
Mercado Pago Java SDK
Official Java SDK wrapping the Mercado Pago REST APIs.
Mercado Pago .NET SDK
Official .NET / C# SDK wrapping the Mercado Pago REST APIs.
Mercado Pago Go SDK
Official Go SDK for the Mercado Pago REST APIs.
Mercado Pago iOS SDK
Official iOS / Swift mobile SDK providing card tokenisation, hosted payment screens, and Checkout integration for native iOS apps.
Mercado Pago Android SDK
Official Android / Kotlin mobile SDK for tokenisation, payment screens, and Checkout integration in native Android apps.
Mercado Pago CLI
Command-line interface for managing Mercado Pago integrations: trigger test events, inspect webhook deliveries, scaffold sample apps, and run local listeners. Distributed via a ...
Mercado Pago MCP Server
Model Context Protocol server exposing Mercado Pago APIs as tools for AI agents and IDE assistants. Enables agent-driven payment, preference, and checkout workflows from Anthrop...
Mercado Pago WooCommerce Plugin
Official WooCommerce gateway plugin enabling Mercado Pago Checkout Pro, Bricks, and Checkout API payment methods in WordPress stores.
Mercado Pago n8n Node
Official n8n workflow automation node for orchestrating Mercado Pago operations alongside other SaaS apps.
Mercado Pago Authentication API
OAuth 2.0 authorisation flows
Mercado Pago Cards API
Tokenised customer cards
Mercado Pago Chargebacks API
Read chargebacks and disputes
Mercado Pago Claims API
Buyer claims, mediations, and evidence
Mercado Pago Customers API
Stored customers and addresses
Mercado Pago Merchant Orders API
Aggregated preference + payments order resource
Mercado Pago Orders API
Unified Orders API (next-generation checkout)
Mercado Pago Payment Methods API
Discover available payment methods
Mercado Pago Payments API
Create, capture, refund, and search payments
Mercado Pago Plans API
Subscription plans
Mercado Pago Point API
In-person POS (stores, terminals)
Mercado Pago Preferences API
Checkout Pro preferences
Mercado Pago QR API
QR-code in-person collection
Mercado Pago Refunds API
Refund payments
Mercado Pago Reports API
Settlement and release reports
Mercado Pago Subscriptions API
Recurring preapproval subscriptions
Scroll within the panel for all 44 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Mercado Pago REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mercado Pago Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Mercado Pago Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Mercado Pago Webhooks (IPN / Webhooks v2)
Mercado Pago webhook notifications for payments, refunds, chargebacks, merchant orders, subscriptions, and POS events. Webhook payloads include `x-signature` and `x-request-id` ...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Mercado Pago Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Mercado Pago Payment
JSON SCHEMAMercado Pago Checkout Preference
JSON SCHEMAMercado Pago Refund
JSON SCHEMAMercado Pago Subscription (Preapproval)
JSON SCHEMAJSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Mercado Pago Payment Structure
JSON STRUCTUREMercado Pago Preference Structure
JSON STRUCTUREExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Mercado Pago — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mercado-pago · machine-readable index on apis.io