Cross-Border Payments
Providers using this tag (77)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 18 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 17 Early or largely undocumented
Minimal 21 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 6 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 1 Early or largely undocumented
Minimal 2 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.4 | +11.7 | 75 |
| Contract Quality | 26.6 | 20.1 | +6.5 | 75 |
| Discoverability | 65.7 | 61 | +4.7 | 75 |
| Operational Transparency | 16.8 | 14 | +2.8 | 75 |
| Contract Governance | 8.4 | 6.5 | +1.9 | 75 |
| Access Clarity | 27 | 26.5 | +0.5 | 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) | 16% | 10% | +6 |
| MCP server (first-party) | 20% | 13% | +7 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 11% | +5 |
| Security | 100% | 96% | +4 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 5% | 13% | -8 |
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 91.4
- 2 Lightspark 70.3
- 3 Airtm 60.3
- 4 Flywire 60.1
- 5 iBanFirst 59.5
- 6 Currencycloud 59.4
- 7 BVNK 58.1
- 8 Ripple Labs 57.7
- 9 Klasha 54.8
- 10 Duplo 53.4
- 1 Airwallex 61.6
- 2 Tesser 56.1
- 3 iBanFirst 55.1
- 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
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.