emerging · 1.2 capabilitymarket actiondomain

E-Invoicing

Score 21.3 / 100 27 providers +2 via APIs 10 APIs Search apis.io →
Business capabilities this tag reaches
Subscription Billing & Revenue Management 1
Variants seen in the corpus: Electronic InvoicingE-Invoicing

Providers using this tag (27)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Strong 2 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 3 Early or largely undocumented
Minimal 1 Almost no public developer surface
Unrated 1 Not yet scored

APIs with this tag (10)

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 →

Strong 1 Solid coverage with minor gaps
Developing 4 Usable, with meaningful gaps to close
Thin 5 Limited public surface area

Companies reaching this through an API (2)

These companies publish an API, specification or operation carrying “E-Invoicing” 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.

Pennylane Zuora

Score breakdown

Frequency
43.0
log-scaled weighted occurrences
Breadth
0.7
spread across providers
Quality lift
46.4
mean composite of providers using it
Cohesion
7.5
strength of nearest seed neighbor

Where this tag sits

Invoicing broader

Related tags

Tax Compliance 5 co-occurrences Invoicing 14 co-occurrences Tax 7 co-occurrences Accounting 10 co-occurrences Procurement 5 co-occurrences Product 6 co-occurrences Transaction 5 co-occurrences Fintech 16 co-occurrences

Where this tag comes from

Provider tag27
Api tag10
Openapi tag1
Openapi op tag1

Cohort brief

Auto-generated

The 25 providers in the APIs.io catalog tagged E-Invoicing, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
25
of 27 in the catalog
Mean Kin Score
37.7
+14.8 vs catalog 22.9
Mean Agent Readiness
22.5
+10.6 vs catalog 11.9
Spread
10.5–64.7
median 41.4 · σ 13.7
How the 25 split by band
Exemplar 0Strong 2Developing 11Thin 8Emerging 3Minimal 1
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 45.1 23.2 +21.9 25
Contract Quality 31.8 17.6 +14.2 25
Discoverability 70.8 58.1 +12.7 25
Access Clarity 38.1 26.5 +11.6 25
Operational Transparency 23.4 13.7 +9.7 25
Contract Governance 9.9 6.3 +3.6 25

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 15% 14% +1
MCP server (first-party) 15% 12% +3
Agent Skills 0% 0% 0
OAuth scopes 23% 11% +12
Security 96% 98% -2
Arazzo workflows 4% 2% +2
Governance rules 8% 14% -6

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.

Top by Kin Score
  1. 1 Tradeshift 64.7
  2. 2 Sirenic 56
  3. 3 Proactis 54
  4. 4 Duplo 50.6
  5. 5 Agicap 50.2
  6. 6 inFakt 48.1
  7. 7 Anrok 47.8
  8. 8 Sibill 46.8
  9. 9 Fonoa 43.3
  10. 10 Paraşüt 42
Top by Agent Readiness
  1. 1 Sirenic 70.9
  2. 2 Anrok 56.5
  3. 3 Tradeshift 50.9
  4. 4 Causa Prima 46.8
  5. 5 Agicap 43.3
  6. 6 Sibill 33.3
  7. 7 Vayana Network 31.4
  8. 8 Basware 30.9
  9. 9 Fonoa 29.8
  10. 10 Procuros 29
All 27 members of this roster resolve to a provider in the catalog; 25 carry a score (93%). The figures above describe the scored members only.
Coverage caveat. 22 of 25 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.

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.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/e-invoicing"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/e-invoicing"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/e-invoicing/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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