Catalog profiles
18,250API Tracker’s catalog coverage analysis dated 2026-10-21 found 18,250 provider profiles.
Provider profiles are not a count of API endpoints, active APIs or unique products.
Source & field definitions ↗API TRACKER RESEARCH · BY APIDECK
API statistics.
The catalog, measured.
Documentation, SDKs and specification resources across our provider catalog. Eight findings with downloadable evidence.
Analysis date: · Historical catalog fields · First edition
18,250Provider profiles
3,973With documentation URLs
846With SDK resource URLs
RECORDED RESOURCE COVERAGE
What developers can find in the catalog
Each bar counts profiles containing at least one qualifying URL. A profile can appear in multiple groups.
Eight findings you can reproduce
All denominators refer to the same 18,250 provider profiles in this export.
Developer documentation
3,973API Tracker’s catalog coverage analysis dated 2026-10-21 found 3,973 profiles with a recorded developer-portal URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗API references
1,454API Tracker’s catalog coverage analysis dated 2026-10-21 found 1,454 profiles with a recorded API-reference URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗04#sdks
SDK resources
846API Tracker’s catalog coverage analysis dated 2026-10-21 found 846 profiles with at least one SDK resource URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗Specification resources
46API Tracker’s catalog coverage analysis dated 2026-10-21 found 46 profiles with at least one structured specification URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗06#status
Status pages
1,541API Tracker’s catalog coverage analysis dated 2026-10-21 found 1,541 profiles with a recorded status-page URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗API changelogs
35API Tracker’s catalog coverage analysis dated 2026-10-21 found 35 profiles with a recorded API-changelog URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗08#limits
API limits documentation
110API Tracker’s catalog coverage analysis dated 2026-10-21 found 110 profiles with a recorded API-limits URL among 18,250 catalog profiles.
This measures recorded catalog links, not validated availability or the proportion of providers supporting this capability.
Source & field definitions ↗MCP ASSOCIATION REVIEW · OCTOBER 21, 2026
Which API profiles list an MCP implementation?
30Profiles with reviewed associations
24With an official implementation
6With an archived community reference
Our conservative review retains 30 explicit associations among 18,250 catalog profiles (0.16%). This is the reviewed subset of the legacy profile links, not a census of every provider offering MCP.
Official status applies to the specific implementation cited in our publisher collection, reviewed October 17. Community references are archived and are not evidence of active support. Unresolved identities and broad brand-name matches are excluded; missing associations mean unknown. Neither category proves endpoint availability or security.
Download every association, source URL and review date (JSON)
This supplement is separate from the eight frozen catalog-field findings above. Each profile is counted once; no brand-family or prefix matches are counted.
Source, definitions & limitations
Source: API Tracker’s local provider-catalog export, analyzed October 21, 2026. Identity-matched corrections from our reviewed profile dataset are applied to developer-portal and API-reference fields. This is not a new survey or live provider crawl. The 18,250-record export can differ from the hosted directory count because their observation dates and inclusion rules differ.
- Count each exact catalog profile ID once. Do not merge brands or count embedded API records as separate providers.
- Documentation, reference, status, changelog and limits use developerPortalUrl, apiReferenceUrl, statusUrl, apiChangelogUrl and apiLimitsUrl respectively. Accept HTTP(S) URLs without embedded credentials; deduplicate URLs within each field group.
- SDK coverage requires a URL in websiteUrl, githubUrl or url on an SDK record. It does not establish that the SDK is official, supported or downloadable.
- Specification coverage requires a url in apiTracker.specs or embedded apis[].specs. Other free-text links, specRepo and unresolved external API references are excluded. Files are not parsed or validated as OpenAPI.
- Missing fields remain unknown. URLs are not fetched for this analysis; syntax validation cannot establish correctness, liveness, API availability or security. Categories overlap and are not additive.
The download preserves each profile ID and the exact counted resource URLs. Source-export and correction-file hashes are included in the aggregate report. Catalog coverage percentages should not be quoted as API industry adoption rates.
Aggregate report & SHA-256 hashes · Reproduction script · Directory methodology
Cite this research
API Tracker by Apideck. “API statistics: documentation & SDK catalog coverage.” Analysis dated October 21, 2026. Cite the finding’s permanent link and retain its catalog-coverage qualification.
https://apitracker.io/api-statistics/2026-10-21This edition is frozen. Monthly editorial review can publish a new dated edition after a complete export and evidence review. Changes in catalog coverage are not automatically growth in the API market.
Suggest a correction →