niche · -1.3 capability resource

Intelligent Document Processing

Score 18.1 / 100 28 providers +11 via APIs 16 APIs Search apis.io →
Variants seen in the corpus: IDPIntelligent Document Processing

Providers using this tag (28)

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

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

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 4 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Emerging 1 Early or largely undocumented
Minimal 1 Almost no public developer surface

Companies reaching this through an API (11)

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

Acronis Axway Codefresh Events.com Harness Lancaster University Mia-Platform Palo Alto Networks Qlik Sense Stytch Wazo

Score breakdown

Frequency
43.3
log-scaled weighted occurrences
Breadth
0.4
spread across providers
Quality lift
36.0
mean composite of providers using it
Cohesion
0.0
strength of nearest seed neighbor

Related tags

Document AI 14 co-occurrences OCR 15 co-occurrences Document Processing 10 co-occurrences Data Extraction 12 co-occurrences Extraction 5 co-occurrences Classification 6 co-occurrences Audit 6 co-occurrences

Where this tag comes from

Provider tag28
Api tag16
Openapi tag4
Openapi op tag20

Cohort brief

Auto-generated

The 26 providers in the APIs.io catalog tagged Intelligent Document Processing, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
26
of 28 in the catalog
Mean Kin Score
36.7
+12.6 vs catalog 24.1
Mean Agent Readiness
23.7
+9.6 vs catalog 14.1
Spread
3–61.3
median 35.7 · σ 16.8
How the 26 split by band
Exemplar 0Strong 5Developing 6Thin 8Emerging 4Minimal 3
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Contract Quality 38.5 18.6 +19.9 26
Developer Ergonomics 40.4 24.5 +15.9 26
Operational Transparency 21.9 13.2 +8.7 26
Discoverability 67.7 59.1 +8.6 26
Access Clarity 37.6 30 +7.6 26
Contract Governance 15.4 9.7 +5.7 26

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) 26% 18% +8
MCP server (first-party) 30% 16% +14
Agent Skills 0% 0% 0
OAuth scopes 11% 13% -2
Security 96% 99% -3
Arazzo workflows 11% 1% +10
Governance rules 67% 36% +31

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 Super.ai 61.3
  2. 2 Affinda 57.5
  3. 3 Nanonets 55.7
  4. 4 Instabase 54.7
  5. 5 Azure AI Document Intelligence 54.5
  6. 6 DocuPipe 53.1
  7. 7 ABBYY 53
  8. 8 ParseForMe 52.5
  9. 9 Mindee 51.1
  10. 10 Indico Data 49.3
Top by Agent Readiness
  1. 1 Extend 59.4
  2. 2 Nanonets 53
  3. 3 Affinda 51.5
  4. 4 ABBYY 45.9
  5. 5 ParseForMe 36.1
  6. 6 Super.ai 33.4
  7. 7 Mindee 31.3
  8. 8 Sensible 31
  9. 9 Instabase 30.7
  10. 10 Xceptor 30.7
All 28 members of this roster resolve to a provider in the catalog; 26 carry a score (93%). The figures above describe the scored members only.
Coverage caveat. 20 of 26 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 14 November 2026, across 41591 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/intelligent-document-processing"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.