Remittances
RemittanceRemittances
Providers using this tag (47)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 20 Almost no public developer surface
APIs with this tag (12)
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 4 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (8)
These companies publish an API, specification or operation carrying “Remittances” 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
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 46 providers in the APIs.io catalog tagged Remittances, 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 | 27.6 | 23.4 | +4.2 | 46 |
| Access Clarity | 27.3 | 26.5 | +0.8 | 46 |
| Discoverability | 61.3 | 61 | +0.3 | 46 |
| Contract Governance | 6.6 | 6.5 | +0.1 | 46 |
| Operational Transparency | 13.5 | 14 | -0.5 | 46 |
| Contract Quality | 19.1 | 20.1 | -1 | 46 |
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) | 7% | 10% | -3 |
| MCP server (first-party) | 7% | 13% | -6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 11% | +6 |
| Security | 100% | 96% | +4 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 4% | 13% | -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 Candid Health 68.8
- 2 Flutterwave 62.6
- 3 Optum 61.7
- 4 Airtm 60.3
- 5 Zero Hash 58.2
- 6 Capitalist 50.7
- 7 Afriex 50.6
- 8 Uzum 50.4
- 9 NALA 47.7
- 10 Caliza 46.3
- 1 Airtm 49.4
- 2 LianLian Global 46.7
- 3 Afriex 46.6
- 4 Optum 40.8
- 5 Uzum 38.7
- 6 Candid Health 38.3
- 7 NALA 38.2
- 8 Zero Hash 37.2
- 9 Caliza 36.2
- 10 Capitalist 35.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.