Data Processing
Providers using this tag (28)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 3 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (6)
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
Developing 2 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Companies reaching this through an API (6)
These companies publish an API, specification or operation carrying “Data 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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 24 providers in the APIs.io catalog tagged Data Processing, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Operational Transparency | 30.8 | 13.2 | +17.6 | 24 |
| Developer Ergonomics | 38.5 | 24.5 | +14 | 24 |
| Contract Quality | 31.2 | 18.6 | +12.6 | 24 |
| Access Clarity | 40.8 | 30 | +10.8 | 24 |
| Discoverability | 63.4 | 59.1 | +4.3 | 24 |
| Contract Governance | 13.6 | 9.7 | +3.9 | 24 |
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% | 18% | -2 |
| MCP server (first-party) | 16% | 16% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 13% | +3 |
| Security | 96% | 99% | -3 |
| Arazzo workflows | 12% | 1% | +11 |
| Governance rules | 56% | 36% | +20 |
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 Google Cloud Dataflow 74.3
- 2 Amazon EMR 71.9
- 3 Amazon Ground Station 71.8
- 4 AWS Kinesis 70.7
- 5 Google Cloud Dataproc 70.4
- 6 Nuix 67
- 7 Amazon Data Pipeline 65
- 8 Relativity 48.2
- 9 Argo Workflows 45.4
- 10 Spring Batch 34.6
- 1 AWS Kinesis 45.6
- 2 ApyHub 44.3
- 3 Amazon Ground Station 43.2
- 4 Google Cloud Dataflow 41.6
- 5 Amazon Data Pipeline 38.4
- 6 Google Cloud Dataproc 36.5
- 7 Nuix 35.1
- 8 Amazon EMR 34
- 9 Relativity 28.2
- 10 Spring Batch 24.3
Coverage caveat. 14 of 24 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.