The rest of APIs.io is the supply side: which APIs are published, and how good they are on the Kin Score. Insights is the demand side. We read companies’ own job postings for the APIs, tools, standards and regulations they name, then join what they name back to the providers in the catalog. Q3 2026 is the first quarter: 343,299 postings from 984 companies, 775 of them in the Fortune 1000 and 209 of them API providers already in the catalog.
Every number is a count of companies whose postings name the term at least once, not a count of mentions. A company with a hundred matching postings counts once.
What the first quarter says
| Term | Companies | Share of 984 | Fortune 1000 | API providers |
|---|---|---|---|---|
| Amazon Web Services | 639 | 64.9% | 61.3% | 78.5% |
| Microsoft Azure | 633 | 64.3% | 65.3% | 60.8% |
| Salesforce | 619 | 62.9% | 60.9% | 70.3% |
| Kubernetes | 522 | 53.0% | 48.0% | 71.8% |
| Claude | 380 | 38.6% | 33.3% | 58.4% |
| Apache Kafka | 334 | 33.9% | 32.5% | 39.2% |
| GraphQL | 217 | 22.1% | 21.7% | 23.4% |
| Model Context Protocol (MCP) | 102 | 10.4% | 11.0% | 8.1% |
| OpenAPI | 99 | 10.1% | 11.0% | 6.7% |
Three readings stand out. Claude is named by 58.4% of the API providers and 33.3% of the Fortune 1000, the widest gap between the two groups in the table. GraphQL is named by more than twice as many companies as OpenAPI. And MCP and OpenAPI land within three companies of each other, 102 and 99, with the Fortune 1000 naming both more often than the API providers do. API Evangelist takes the specification side of this apart in its companion piece, Nine Hundred Eighty-Four Companies Hiring And Ninety-Nine Of Them Say OpenAPI.
A job posting shows hiring intent, not production use. Every term is matched on whole words and checked against a sample of the postings before it is quoted. Because this is the first quarter, nothing here is rising or falling yet. The Q4 pull runs in November and is the first that will report movement.
The join only the catalog can make
A list of what companies hire for is useful. What makes Insights an APIs.io product is the join. match_providers takes the services a company names in its postings and returns the catalog providers that publish them, ranked by Kin Score. company_gaps shows where a company is thin against its peers.
If you run an API, you can look up the accounts you sell to and see whether their postings already name your product, or a competitor’s, and where your listing ranks in match_providers for them. If you build on APIs, you can see which services and standards employers ask for, with the providers behind each one a click away in the catalog.
What you can ask it
Insights is part of the Understanding plan, served by the same REST API and MCP server as the rest of APIs.io. REST lives under /api/v1/insights/*. On MCP there are eight tools: insights_overview, find_company_insights, insights_dimensions, insights_adoption, insights_industries, get_company_insight, company_gaps and match_providers.
Takeaway
The catalog shows what APIs exist. Insights shows who is hiring for them. Start with the Q3 2026 numbers on the Insights page, then pick a plan on /developer/plans/ to run match_providers against the accounts you care about.