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.

Loopay publishes 15 API contracts indexed on the APIs.io network, including Affiliate API, Bank API, Company API, and 12 more. Tagged areas include Company, Payments, Fintech, Banking as a Service, and Cross-Border Payments.

The Loopay catalog on APIs.io includes 1 Spectral governance ruleset.

Loopay’s developer surface includes documentation, API reference, authentication, sandbox, engineering blog, support, signup flow, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.6/100 thin ▬ flat Agent 24/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Payments Fintech Banking as a Service Cross-Border Payments Payouts Treasury Latin America

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Payments & Card Management

BC-1340

Payout

POST /payout/create POST /payouts/sign

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 35.6/100 · thin

Contract Quality 9.5 / 19

Developer Ergonomics 8.1 / 15

Access Clarity 1.6 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/loopay/"><img src="https://apis.io/badge/loopay/card.svg" alt="Loopay on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 10.5 — up to +17.9 composite points
Contract Quality scores 50.6 — up to +12.4 composite points
Operational Transparency scores 10.5 — up to +11.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/loopay/apis.yml: open an issue on github.com/api-evangelist/loopay to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 15

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 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.

Loopay Document type API

The Document type API from Loopay — 1 operation(s) for document type.

Scroll for all 15

Open Collections 15

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

loopay-api Affiliate API

OPEN COLLECTION

loopay-api Affiliate Bank API

OPEN COLLECTION

loopay-api Affiliate Company API

OPEN COLLECTION

loopay-api Affiliate CompanyProduct API

OPEN COLLECTION

loopay-api Affiliate Country API

OPEN COLLECTION

loopay-api Affiliate Currency API

OPEN COLLECTION

loopay-api Affiliate DocumentType API

OPEN COLLECTION

loopay-api Affiliate Movements API

OPEN COLLECTION

loopay-api Affiliate PaidMethods API

OPEN COLLECTION

loopay-api Affiliate PayIn API

OPEN COLLECTION

loopay-api Affiliate Payout API

OPEN COLLECTION

loopay-api Affiliate PhysicalPoint API

OPEN COLLECTION

loopay-api Affiliate SourcesOfPayment API

OPEN COLLECTION

loopay-api Affiliate SourcesOfPaymentAdmin API

OPEN COLLECTION

loopay-api Affiliate User API

OPEN COLLECTION

Scroll for all 15

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create and track a Loopay payout

AGENT SKILL

Reconcile Loopay payouts and movements

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Loopay API Rules

55 rules · 45 errors 7 warnings 3 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Loopay Openapi Overlay

2 actions · security · loopay-openapi-original.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Loopay Authentication

token · 1 scheme

SECURITY

Loopay Domain Security

TLSv1.3

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Loopay Agentic Access

31 operations · 9 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Sandbox

Sandbox

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

WellKnown

AgentSkill

AgenticAccess

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

DataModel

Conformance

Lifecycle

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

SecurityPolicy

SecurityPolicy

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Company 3

The organization behind the API

Blog

Blog

LinkedIn

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: loopay
name: Loopay
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/loopay/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://loopay.com/wp-content/uploads/2023/09/Loopay-web-imgs-24-150x139.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Payments
- Fintech
- Banking as a Service
- Cross-Border Payments
- Payouts
- Treasury
- Latin America
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: loopay:loopay-affiliate-api
  name: Loopay Affiliate API
  description: The Affiliate API from Loopay — 4 operation(s) for affiliate.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Affiliates
  tags_raw:
  - Affiliate
  properties:
  - type: OpenAPI
    url: openapi/loopay-affiliate-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-bank-api
  name: Loopay Bank API
  description: The Bank API from Loopay — 1 operation(s) for bank.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Bank
  properties:
  - type: OpenAPI
    url: openapi/loopay-bank-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-company-api
  name: Loopay Company API
  description: The Company API from Loopay — 1 operation(s) for company.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Company
  properties:
  - type: OpenAPI
    url: openapi/loopay-company-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-companyproduct-api
  name: Loopay CompanyProduct API
  description: The CompanyProduct API from Loopay — 1 operation(s) for companyproduct.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - CompanyProduct
  properties:
  - type: OpenAPI
    url: openapi/loopay-companyproduct-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-country-api
  name: Loopay Country API
  description: The Country API from Loopay — 1 operation(s) for country.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Country
  properties:
  - type: OpenAPI
    url: openapi/loopay-country-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-currency-api
  name: Loopay Currency API
  description: The Currency API from Loopay — 1 operation(s) for currency.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Currency
  properties:
  - type: OpenAPI
    url: openapi/loopay-currency-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-movements-api
  name: Loopay Movements API
  description: The Movements API from Loopay — 1 operation(s) for movements.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Movements
  properties:
  - type: OpenAPI
    url: openapi/loopay-movements-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-paidmethods-api
  name: Loopay PaidMethods API
  description: The PaidMethods API from Loopay — 1 operation(s) for paidmethods.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - PaidMethods
  properties:
  - type: OpenAPI
    url: openapi/loopay-paidmethods-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-payin-api
  name: Loopay PayIn API
  description: The PayIn API from Loopay — 2 operation(s) for payin.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Pay-In
  tags_raw:
  - PayIn
  properties:
  - type: OpenAPI
    url: openapi/loopay-payin-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-payout-api
  name: Loopay Payout API
  description: The Payout API from Loopay — 6 operation(s) for payout.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Payout
  properties:
  - type: OpenAPI
    url: openapi/loopay-payout-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-physicalpoint-api
  name: Loopay PhysicalPoint API
  description: The PhysicalPoint API from Loopay — 1 operation(s) for physicalpoint.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - PhysicalPoint
  properties:
  - type: OpenAPI
    url: openapi/loopay-physicalpoint-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-sourcesofpayment-api
  name: Loopay SourcesOfPayment API
  description: The SourcesOfPayment API from Loopay — 5 operation(s) for sourcesofpayment.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - SourcesOfPayment
  properties:
  - type: OpenAPI
    url: openapi/loopay-sourcesofpayment-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-sourcesofpaymentadmin-api
  name: Loopay SourcesOfPaymentAdmin API
  description: The SourcesOfPaymentAdmin API from Loopay — 3 operation(s) for sourcesofpaymentadmin.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - SourcesOfPaymentAdmin
  properties:
  - type: OpenAPI
    url: openapi/loopay-sourcesofpaymentadmin-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-user-api
  name: Loopay User API
  description: The User API from Loopay — 2 operation(s) for user.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - User
  properties:
  - type: OpenAPI
    url: openapi/loopay-user-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
- aid: loopay:loopay-document-type-api
  name: Loopay Document type API
  description: The Document type API from Loopay — 1 operation(s) for document type.
  humanURL: https://api.loopay.com/explorer
  baseURL: https://api.loopay.com
  tags:
  - Document type
  properties:
  - type: OpenAPI
    url: openapi/loopay-document-type-api-openapi.yml
  - type: APIReference
    url: https://api.loopay.com/explorer
  - type: Authentication
    url: authentication/loopay-authentication.yml
  - type: Conventions
    url: conventions/loopay-conventions.yml
  - type: DataModel
    url: data-model/loopay-data-model.yml
common:
- type: CapabilityMap
  url: capabilities/loopay-capability-edges.yml
  name: Loopay Business Capability Map
- type: DeveloperPortal
  url: https://api.loopay.com/explorer
- type: Documentation
  url: https://api.loopay.com/explorer
- type: APIReference
  url: https://api.loopay.com/explorer
- type: Authentication
  url: authentication/loopay-authentication.yml
- type: Conventions
  url: conventions/loopay-conventions.yml
- type: DataModel
  url: data-model/loopay-data-model.yml
- type: Conformance
  url: conformance/loopay-conformance.yml
- type: Lifecycle
  url: lifecycle/loopay-lifecycle.yml
- type: Sandbox
  url: sandbox/loopay-sandbox.yml
- type: X-MCPServerCandidate
  url: mcp/loopay-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/loopay-llms.txt
- type: Overlay
  url: overlays/loopay-openapi-overlay.yaml
- type: WellKnown
  url: well-known/loopay-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/loopay-agentic-access.yml
- type: DomainSecurity
  url: security/loopay-domain-security.yml
- type: Blog
  url: https://loopay.com/blog-fintech-pagos-latinoamerica/
- type: Support
  url: https://loopay.com/contacto/
- type: SignUp
  url: https://app.loopay.com/
- type: Login
  url: https://app.loopay.com/
- type: TermsOfService
  url: https://loopay.com/terminos-y-condiciones/
- type: SecurityPolicy
  url: https://loopay.com/politica-de-seguridad/
- type: LinkedIn
  url: https://www.linkedin.com/company/somosloopay/
- type: Website
  url: https://loopay.com
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 14
  pass: local-v1

Loopay API — frequently asked questions

Does Loopay have an API?

Yes. APIs.io lists 15 APIs from Loopay, including Loopay Affiliate API, Loopay Bank API and Loopay Company API, and 12 more.

Is there an OpenAPI specification for the Loopay API?

Yes. APIs.io indexes 15 OpenAPI specifications for Loopay, each linked for download from this page.

How do I authenticate with the Loopay API?

Loopay uses bearer-token authentication (token · 1 scheme). The details are profiled on APIs.io as Loopay Authentication.

Is the Loopay API ready for AI agents?

Loopay has a Kin Score of 35.6 out of 100 (thin) and an Agent Readiness score of 24.0 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/loopay"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/loopay/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/loopay/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.