Aggregator
Aggregatoraggregator
Providers using this tag (31)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 5 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 →
Strong 1 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 31 providers in the APIs.io catalog tagged Aggregator, 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 | 42.4 | 17.5 | +24.9 | 31 |
| Developer Ergonomics | 34.4 | 17.9 | +16.5 | 31 |
| Discoverability | 74.5 | 60.4 | +14.1 | 31 |
| Access Clarity | 30.9 | 22.3 | +8.6 | 31 |
| Operational Transparency | 19.2 | 11.3 | +7.9 | 31 |
| Contract Governance | 9.5 | 6.4 | +3.1 | 31 |
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) | 32% | 16% | +16 |
| MCP server (first-party) | 16% | 7% | +9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 19% | 9% | +10 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 13% | 13% | 0 |
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 Infobip 71
- 2 Nokia Network as Code 65.7
- 3 Route Mobile 57.2
- 4 Akoya 53.8
- 5 VaultRE 52.8
- 6 Syniverse 52.3
- 7 CoinGecko 50.9
- 8 Beeper 48.1
- 9 Rarible 46.8
- 10 Varo Bank 43
- 1 Infobip 47.7
- 2 Nokia Network as Code 43
- 3 Route Mobile 35.8
- 4 Syniverse 35.8
- 5 VaultRE 33.3
- 6 Calyptia 29.7
- 7 Rarible 28.1
- 8 NewsBlur 27.9
- 9 Beeper 26.8
- 10 Overlay 25.4
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/aggregator"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/aggregator"
curl "https://apis.io/api/v1/cohorts/tag/aggregator/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.