Receipts
Receiptsreceipts
Providers using this tag (49)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 20 Usable, with meaningful gaps to close
Thin 11 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (45)
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 2 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 22 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 7 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 49 providers in the APIs.io catalog tagged Receipts, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 47 | 17.5 | +29.5 | 49 |
| Access Clarity | 42.7 | 22.3 | +20.4 | 49 |
| Operational Transparency | 30.3 | 11.3 | +19 | 49 |
| Developer Ergonomics | 36.7 | 17.9 | +18.8 | 49 |
| Discoverability | 69.4 | 60.4 | +9 | 49 |
| Contract Governance | 14.5 | 6.4 | +8.1 | 49 |
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) | 27% | 16% | +11 |
| MCP server (first-party) | 4% | 7% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 31% | 9% | +22 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 10% | 2% | +8 |
| Governance rules | 35% | 13% | +22 |
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 Efí Pay (Gerencianet) 70.6
- 2 iOS 67.9
- 3 Argyle 62.8
- 4 FaturaPDF — Brazilian Invoice & Receipt PDF API 60.5
- 5 PlateIQ 59.6
- 6 Mindee 57.6
- 7 Mamo 57.1
- 8 Dext 56
- 9 Authenticx 54
- 10 Flipdish 54
- 1 OpenGov 63.1
- 2 Authenticx 44.1
- 3 American Express Global Business Travel 42.6
- 4 LianLian Global 41.7
- 5 SumUp 38.8
- 6 FaturaPDF — Brazilian Invoice & Receipt PDF API 36.9
- 7 Qubiqle 36.4
- 8 Flipdish 35.2
- 9 Veryfi 35.1
- 10 PlateIQ 34.6
Work with this as data
Every tag 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 tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/receipts"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/receipts"
curl "https://apis.io/api/v1/cohorts/tag/receipts/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.