Historical
Historicalhistorical
Providers using this tag (100)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Developing 19 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 57 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 3 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 22 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 100 providers in the APIs.io catalog tagged Historical, 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 | 13.2 | 11.3 | +1.9 | 100 |
| Contract Quality | 19.3 | 17.5 | +1.8 | 100 |
| Discoverability | 60.7 | 60.4 | +0.3 | 100 |
| Contract Governance | 6.2 | 6.4 | -0.2 | 100 |
| Developer Ergonomics | 16 | 17.9 | -1.9 | 100 |
| Access Clarity | 18.7 | 22.3 | -3.6 | 100 |
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) | 12% | 16% | -4 |
| MCP server (first-party) | 4% | 7% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 6% | 9% | -3 |
| Security | 62% | 88% | -26 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 25% | 13% | +12 |
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 Financial Modeling Prep 72.8
- 2 Polygon 71.5
- 3 8x8 67.1
- 4 Tomorrow.io 66.6
- 5 Factset 64.8
- 6 Kaiko 57.5
- 7 Datadog 57.1
- 8 MISO 54
- 9 CryptoCompare 53.8
- 10 Azure Maps 48.4
- 1 CryptoCompare 60.2
- 2 Polygon 57.3
- 3 Factset 52.8
- 4 Financial Modeling Prep 44
- 5 8x8 43.3
- 6 Datadog 38.3
- 7 Flightradar24 32.7
- 8 MISO 31.5
- 9 Trading Economics 30
- 10 CurrencyAPI 28.7
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/historical"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/historical"
curl "https://apis.io/api/v1/cohorts/tag/historical/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.