Mercado Pago
Mercado Pago is the payments and financial-services arm of Mercado Libre, Latin America's largest e-commerce and fintech platform. Its developer portal at developers.mercadopago.com exposes a rich payments stack - Checkout Pro (hosted), Checkout Bricks (composable web components), Checkout API (full server-side control), Subscriptions, Payment Links, Point (in-person card reader), and QR payments - backed by REST APIs and official SDKs in Node.js, Python, PHP, Ruby, Java, .NET, plus a CLI and an MCP server for AI agents. Regional portals (.com.ar, .com.br, .com.mx, etc.) localise the docs and pricing per LATAM market.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Mercado Pago the way a machine reads it — 27 machine-readable artifacts across 20 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 34.6/100 (thin), with a separate agent-readiness read of 48/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.
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 20
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 Payments API
Core REST API for creating and managing payments across cards, account-money, bank transfer (Pix in Brazil), boleto, and other LATAM methods. Supports capture, refund, partial r...
Mercado Pago Checkout Pro
Hosted, pre-configured checkout experience. Merchants create a preference via API, then redirect the buyer to the Mercado Pago hosted page that handles UI, payment-method select...
Mercado Pago Checkout Bricks
Composable web components ("bricks") that merchants embed in their own checkout UI - card form, wallet, payment-method picker, status screen. Lets merchants assemble a branded c...
Mercado Pago Checkout API
Full server-side checkout control: tokenise cards client-side, create a payment server-side, manage 3DS challenges, and handle capture and refund - all without redirecting the b...
Mercado Pago Subscriptions API
Recurring-payment subscriptions with scheduling, plans, free trial, proration, and pause / resume / cancel. Supports both subscription plans (shared) and per-customer pre-approv...
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, or social channels.
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, receive the authorization result, and reconcile via...
Mercado Pago QR API
Static and dynamic QR code APIs for in-person collection, with order-linked status retrieval and webhook callbacks.
Mercado Pago Webhooks / Notifications
Event-driven notifications for payments, refunds, chargebacks, subscriptions, and merchant-account changes. Webhooks are signed so receivers can verify authenticity.
Mercado Pago Node.js SDK
Official Node.js / TypeScript SDK wrapping the Mercado Pago REST APIs for payments, preferences, subscriptions, 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.
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 CLI
Command-line interface for managing Mercado Pago integrations, triggering test events, inspecting webhook deliveries, and scaffolding sample apps.
Mercado Pago MCP Server
Model Context Protocol server that exposes Mercado Pago APIs as tools for AI agents and IDE assistants, enabling agent-driven payment and checkout workflows.
Mercado Pago Payments API
The Payments API from Mercado Pago — 4 operation(s) for payments.
Mercado Pago Preferences API
The Preferences API from Mercado Pago — 3 operation(s) for preferences.
Mercado Pago Subscriptions API
The Subscriptions API from Mercado Pago — 3 operation(s) for subscriptions.
Scroll within the panel for all 20 ·
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.
Mercadopago 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.
Mercadopago Finops
FINOPSSecurity 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.
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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mercadopago · machine-readable index on apis.io