Say you are choosing which companies to build against. You want to know who in a market actually works with whom, and how deep those ties go. So you open the apis.io markets section, which was regenerated on 2026-10-20 and now covers 110 markets: 104 bedrock markets, measured by depth and structure, and 6 frontier markets, measured by movement between weekly snapshots.
Before you read a single leaderboard, you should know what the page is telling you about itself. Across those markets there are 6,932 provider-to-market memberships. In 2,452 of them, or 35.4%, the provider declares nothing about its integrations that the catalog can read. The section records those as undeclared and gives them no number. The post calls this the most important thing the section shows, and says the page is right to show it rather than guess.
Here is how the memberships break down. 2,508 are Own, meaning the provider names at least one integration itself. 1,406 are Covered, meaning they are visible only because an aggregator, regulator, standard or partner contract names them. 566 are Distribution only, listed only on cloud marketplaces the provider sells through. And 2,452 are Undeclared: nothing readable, so no number.
Each market page reads its providers by who they integrate with and how deep those integrations go. It also reads places where the market publishes its own structure: partners' contracts, connector catalogs, regulators' registers and standards bodies' member lists. Leaders are grouped by position, such as gravity, core, standard, coverage, regulated and long-tail, and depth is compared only within a position. The whole layer is labelled provisional and unweighted. It is not part of the Kin Score composite or of Agent Readiness, so you should not read it as one more input to those scores.
Now look at the two ends of the range. Payments is the best-declared market. Of its 25 providers, 72% declare their own integrations and none are undeclared. Stripe holds the gravity position at depth 69.3, with 926 integrations, 802 of them inbound. The post's reading is that this is what a market looks like when other companies invest in building on its leader. If you are picking partners here, you have real numbers to work with.
Drones and airspace is the opposite. It has 139 providers and 81.3% of them are undeclared. Only 3 declare their own integrations, and 21 are covered. The post says this is not for lack of effort on the catalog's side: the market lists nine structural sources, from the FAA's LAANC supplier list to InterUSS and GUTMA membership. In this industry, the regulator's register says more about who works with whom than the companies do. If you were hoping to rank drone companies by integration depth, the page will not let you, and that is the honest answer. Fourteen of the 110 markets have no undeclared members at all.
Then comes the part where the catalog turns on its own record. Across all markets, 391 structural sources were readable and 368 were not. Some pages are client-rendered, some redirect, some time out, and the source notes say which. The coverage file behind the taxonomy keeps 74 industries in some market, leaves 5 partial and 2 uncovered.
There is a deployment gap too. The live index currently links 98 markets. Twelve were regenerated locally but are not yet deployed. Space-satellite, agent-skills (the largest cohort, at 556), stablecoins-tokenization, xr-graphics, quantum-computing and seven others return 404 on apis.io today. Until the next deploy, the section has fewer markets live than the build produced. If you go looking for one of those and hit a 404, that is why.
So what do you take away? The markets section is useful because it refuses to make up a number for the 35% it cannot read. A blank is information. It tells you either that a provider has not published its integrations in a form anyone can read, or that the catalog has not yet worked through the source that would show them.
The post names three things that would shrink that share. Providers can publish their integration lists in a machine-readable form. The catalog can work through the 368 unreadable sources. And the twelve built markets need to be deployed. One more caveat to carry with you: integration workflows and their phrasing on these pages are generated by API Evangelist and are labelled that way.
Read the original: https://apis.io/2026/10/27/the-markets-section-cannot-read-a-third-of-its-own-cohort/