Cross-Border Payments
Providers using this tag (77)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 18 Early or largely undocumented
Minimal 20 Almost no public developer surface
APIs with this tag (16)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (3)
These companies publish an API, specification or operation carrying “Cross-Border Payments” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Where this tag sits
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 75 providers in the APIs.io catalog tagged Cross-Border Payments, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 35.1 | 23.2 | +11.9 | 75 |
| Contract Quality | 24.1 | 17.6 | +6.5 | 75 |
| Discoverability | 64 | 58.1 | +5.9 | 75 |
| Operational Transparency | 17 | 13.7 | +3.3 | 75 |
| Contract Governance | 8.3 | 6.3 | +2 | 75 |
| Access Clarity | 27.6 | 26.5 | +1.1 | 75 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 20% | 14% | +6 |
| MCP server (first-party) | 20% | 12% | +8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 11% | +5 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 5% | 14% | -9 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Airwallex 85.3
- 2 Lightspark 66.4
- 3 Airtm 57.8
- 4 Currencycloud 57.2
- 5 iBanFirst 57.1
- 6 Ripple Labs 55.6
- 7 Flywire 55
- 8 BVNK 54.3
- 9 Klasha 51.3
- 10 Duplo 50.6
- 1 Airwallex 61.6
- 2 Tesser 56.1
- 3 iBanFirst 53
- 4 Ripple Labs 51.8
- 5 BVNK 50
- 6 Airtm 49.4
- 7 LianLian Global 46.7
- 8 Afriex 46.6
- 9 Lightspark 46.2
- 10 Rain 39.4
Coverage caveat. 73 of 75 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 5 October 2026, across 29093 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.