Ripio
Ripio is a Latin American cryptocurrency exchange founded in 2013, offering crypto trading, stablecoins, DeFi products, a Visa crypto card, and B2B infrastructure and liquidity across Brazil, Argentina, Chile, Uruguay, Colombia, Mexico, Peru and Spain. Its developer-facing product is the Ripio Trade API (v4) — a REST and WebSocket trading API covering market data, order management, balances, statements, cryptocurrency deposits and withdrawals, and real-time streaming. Authentication uses an API Token plus HMAC-SHA256 request signing. The platform is SOC 2 Type II certified with a HackerOne bug bounty. Backed by Pantera Capital.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Ripio the way a machine reads it — 19 machine-readable artifacts across 11 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 — Ripio scores 60.6/100 (strong), with a separate agent-readiness read of 87/100 (agent native). 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 Ripio
Each block below is one kind of artifact we hold for Ripio. 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 11
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.
Ripio Book API
The Book API from Ripio — 2 operation(s) for book.
Ripio Cryptocurrency Deposits API
The Cryptocurrency Deposits API from Ripio — 2 operation(s) for cryptocurrency deposits.
Ripio Cryptocurrency Withdrawals API
The Cryptocurrency Withdrawals API from Ripio — 3 operation(s) for cryptocurrency withdrawals.
Ripio General endpoints API
The General endpoints API from Ripio — 3 operation(s) for general endpoints.
Ripio Orders API
The Orders API from Ripio — 11 operation(s) for orders.
Ripio Public API
The public endpoints have a reduced requests limit and a 30 seconds cache. For increased limits, use the private endpoints.
Ripio Ticker API
The Ticker API from Ripio — 2 operation(s) for ticker.
Ripio Ticket API
The Ticket API from Ripio — 1 operation(s) for ticket.
Ripio Transactions API
The Transactions API from Ripio — 1 operation(s) for transactions.
Ripio User API
The User API from Ripio — 6 operation(s) for user.
Ripio Wallets API
API to check addresses of wallets.
Scroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
ripio-mcp.yml
MCP SERVERRate 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.
Ripio Rate Limits
RATE LIMITSEvent 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.
Ripio Trade Webhooks
ASYNCAPISecurity Posture 4
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 Ripio — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
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/ripio · machine-readable index on apis.io