Loopay
Loopay is a Latin American B2B fintech infrastructure company headquartered in Bogotá, Colombia and backed by 500 Global. It provides cross-border and local business payments, international collections, mass payouts, multi-currency Banking-as-a-Service accounts, automated bank reconciliation, and treasury management for companies operating across Colombia, Peru, Mexico, and Ecuador. Loopay exposes a token-authenticated REST API (OpenAPI 3.0, 31 operations) that lets platforms create and track payouts, manage sources of payment and pay-ins, group affiliates, and read balances and ledger movements — settling supplier and beneficiary payments in under 24 hours.
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 Loopay the way a machine reads it — 19 machine-readable artifacts across 15 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 — Loopay scores 41.1/100 (thin), with a separate agent-readiness read of 62/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 Loopay
Each block below is one kind of artifact we hold for Loopay. 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 15
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.
Loopay Affiliate API
The Affiliate API from Loopay — 4 operation(s) for affiliate.
Loopay Bank API
The Bank API from Loopay — 1 operation(s) for bank.
Loopay Company API
The Company API from Loopay — 1 operation(s) for company.
Loopay CompanyProduct API
The CompanyProduct API from Loopay — 1 operation(s) for companyproduct.
Loopay Country API
The Country API from Loopay — 1 operation(s) for country.
Loopay Currency API
The Currency API from Loopay — 1 operation(s) for currency.
Loopay DocumentType API
The DocumentType API from Loopay — 1 operation(s) for documenttype.
Loopay Movements API
The Movements API from Loopay — 1 operation(s) for movements.
Loopay PaidMethods API
The PaidMethods API from Loopay — 1 operation(s) for paidmethods.
Loopay PayIn API
The PayIn API from Loopay — 2 operation(s) for payin.
Loopay Payout API
The Payout API from Loopay — 6 operation(s) for payout.
Loopay PhysicalPoint API
The PhysicalPoint API from Loopay — 1 operation(s) for physicalpoint.
Loopay SourcesOfPayment API
The SourcesOfPayment API from Loopay — 5 operation(s) for sourcesofpayment.
Loopay SourcesOfPaymentAdmin API
The SourcesOfPaymentAdmin API from Loopay — 3 operation(s) for sourcesofpaymentadmin.
Loopay User API
The User API from Loopay — 2 operation(s) for user.
Scroll within the panel for all 15 ·
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.
loopay-mcp.yml
MCP SERVERSecurity 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 Loopay — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
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/loopay · machine-readable index on apis.io