factory API Evangelist Product
Market Reports
Every provider in a market, scored on one public rubric.
The Kin Score is applied to every API provider in a market against the same rubric applied to exemplars such as Stripe. It is calculated straight from the machine-readable evidence each provider publishes — the OpenAPIs, the scopes, the security posture, the agent surfaces — so every comparison is made on identical terms. The report gives you the full distribution, the leaders and what they did to get there, the incumbents worth watching, and a standards-and-regulation read on whether the market is moving by choice or by mandate. A market can be an industry, an industry inside one country, or a cohort built on a technology choice — the same instrument either way.
Who buys it
Operators who need to know where they stand against their peers, and investors who need an independent read on how far a market has actually shipped.
Why this exists
Analysts read websites and view demos. Vendors grade themselves. From the outside, a claim and a contract look identical — a company can say "we have an API" for years before anyone checks whether a developer, or an agent, can download the contract, price it, and call it.
That is what an independent read is for. Every provider in the market is put on a level playing field, scored on one public rubric, so the comparison is on identical terms for everyone in it.
What's in every one
Every provider in the market, scored on the same rubric — then the sections that take you from the number to a decision:
- The state of the market — the finding that frames everything
- The resource taxonomy — what these APIs actually expose, and who ships which surface
- The composite score, facet by facet — and which facet is really carrying the market
- Agent-readiness across twelve dimensions — potential versus what is actually shipped
- Provenance — what the providers published, and what was derived
- The blueprint — what the leaders satisfied that the field hasn't
- Standards and regulation — which standards get claimed, and who ships a conformant contract
- Security, auth, scopes, and consent
- Provider-by-provider intelligence — leaders, absent incumbents, and the tail
- The investable thesis
How the scoring works
The Kin Score is applied to every API provider in a market against the same rubric applied to exemplars such as Stripe. It is calculated straight from artifacts a machine can read — the OpenAPI definitions, the scopes, the security posture, the plans and rate limits, the agent surfaces a provider publishes. Marketing claims don't move the number in either direction, which is what makes the comparison fair to everyone in the cohort. Where a provider hasn't published an artifact yet, the report names the one that would move them.
Where a score rests on an artifact API Evangelist generated rather than one the provider published, the report says so in its own section. You can see exactly how much of a market's apparent maturity is real.
A market isn't always a sector
Some of the most useful questions cut across industries. Does an architecture keep the promise it was funded on, once you test it against evidence? What do a thousand real public pipelines say about how teams actually govern, as opposed to how they say they do? Which venture portfolios are genuinely ready for agents that act? Same rubric, same artifact reads, same provenance discipline — over a cohort assembled by a technology choice rather than by sector.
The third cut is the area — not who a company sells to, but what its API actually does. Gateways, portals, observability, monetization, webhooks, SDKs. It reads a market the way an engineer picking a tool reads it, and it routinely shows that a single familiar label has quietly become several markets with different buyers.
The cohort is the hard part. A cohort built by tag match produces a confident wrong answer, which is why these are constructed deliberately and the construction is disclosed. When a single word turns out to cover three unrelated markets with three unrelated buyers, the report says so and scores the tiers separately — that inversion is often the finding itself.
Country is a facet, not a different product
The same industry in two countries is often two different markets, because the regime underneath them differs — a mandate produces one shape, and its absence produces another. Where that's true, the industry is scored per country and the reports are written to be read side by side. Where it isn't, the industry is scored globally.
What you get
The data bundle is the evidence behind every number — layered per-entity data, an APIs.json manifest, a conversation primer, and a data dictionary — packaged to drop straight into the AI tool of your choice. Converse with the research you bought, check any claim against the source, and take it further than the PDF.
41 published
The State of Spectral in API Pipelines
What 1,005 real public pipelines reveal about how teams actually govern their APIs — and the blueprint almost none of them have reached.
The State of Australian Banking APIs
What fifty Consumer Data Right banks actually publish, scored — and what it means for the operators who run them and the investors who back them.
The State of Market Data APIs
What the market data providers actually publish, scored — and where the durable value hides in a commoditizing feed.
The State of UK Banking APIs
What sixty UK banks and building societies actually publish, scored — from the CMA9 Open Banking mandate to the challengers, building societies, and private banks arou...
The Agentic Readiness of Venture
The twenty-five most important venture funds, ranked on one axis — whether their portfolios are ready for agents that act.
The State of US Banking APIs
What 113 US banks, credit unions, neobanks, and banking-rails providers actually publish, scored — the one open-finance market with no mandate, and the widest split in...
The State of Canadian Banking APIs
What 42 Canadian banks, credit unions, caisses, and fintechs actually publish, scored — the emptiest banking market measured, where the rails outrank the banks.
The State of US Payments APIs
What sixty-eight US payment companies actually publish, scored — the deepest, most agent-instrumented payments estate on earth, and the market with no mandate and no f...
The State of UK Payments APIs
What thirty-two UK payment companies actually publish, scored — the open-banking payment-initiation heartland, and the market that hides its own crown jewels.
The State of Australian Payments APIs
What twenty Australian payment companies actually publish, scored — the NPP-native market where the signature resource is PayID, and the agent surface is almost entire...
The State of Canadian Payments APIs
What fourteen Canadian payment companies actually publish, scored — the thinnest, most concentrated market, where the fintechs out-API the incumbents and the rails.
The State of US Healthcare APIs
What seventy-seven US healthcare companies actually publish, scored — the FHIR mandate that inverted the market, and the sector where consent is invisible.
The State of UK Healthcare APIs
What thirteen UK healthcare organizations actually publish, scored — the single-payer market where the incumbent leads and the challengers orbit.
The State of Australian Healthcare APIs
What twelve Australian healthcare organizations actually publish, scored — where the challengers out-execute the national agency, and one built the incumbents' FHIR.
The State of Canadian Healthcare APIs
What ten Canadian healthcare organizations actually publish, scored — the market with no FHIR-native challenger class, where a practice-management vendor tops the field.
The State of US Insurance APIs
What seventy-nine US insurance organizations actually publish, scored — the market with no mandate, where one company in the country publishes bind.
The State of UK Insurance APIs
What thirty-five UK insurance organizations and the London Market actually publish, scored — where a 337-year-old market beat every regulator to open APIs.
The State of Australian Insurance APIs
What twenty Australian insurance organizations actually publish, scored — the country with the machinery for open insurance and no obligation to use it.
The State of Canadian Insurance APIs
What twenty Canadian insurance organizations actually publish, scored — the only market with a real API certification programme, and its largest carrier is Not Yet Rated.
The State of Telecom APIs
What eighty-three telecom organizations worldwide actually publish, scored — the industry that built a real open standard and then published 351 specifications with no...
The State of US Real Estate APIs
What forty-five US real estate organizations actually publish, scored — the only industry that successfully mandated a machine-readable contract on itself, and the two...
The State of UK Real Estate APIs
What twenty-four UK real estate organizations actually publish, scored — the market with no MLS, no standard and no mandate, and the best-published real estate sector ...
The State of Australian Real Estate APIs
What eighteen Australian real estate organizations actually publish, scored — the market that mandated the rail instead of the schema, and got an API that carries prod...
The State of Canadian Real Estate APIs
What fourteen Canadian real estate organizations actually publish, scored — four facets at a clean sweep of zeros, and the fifth consecutive sector in which Canada fin...
The State of Headless APIs
What one hundred and eight headless CMS, commerce and browser providers actually publish, scored — the architecture whose entire promise is that the API is the product...
The State of Australian Energy APIs
What twenty-four Australian energy organizations actually publish, scored — proof that a statutory data mandate transplants from one industry to another, and what it c...
The State of US Energy APIs
What sixty US energy organizations actually publish, scored — the market with the best standard, the largest scale, no obligation, and the lowest average of the four.
The State of UK Energy APIs
What twenty-six UK energy organizations actually publish, scored — the market that mandated the pipes instead of the data, and got exactly what it compelled.
The State of Canadian Energy APIs
What eighteen Canadian energy organizations actually publish, scored — one province mandated Green Button, and the country's best API belongs to a utility nobody compe...
The State of US Travel APIs
What thirty US travel and aviation organizations actually publish, scored — the sector where switching cost IS the commercial structure, and the published surface is i...
The State of UK Travel APIs
What fourteen UK travel and aviation organizations actually publish, scored — the country that proved mandates work, in the one sector it never mandated.
The State of Australian Travel APIs
What eleven Australian travel and aviation organizations actually publish, scored — the control group, and the lowest contract-quality reading in this entire research ...
The State of Canadian Travel APIs
What nine Canadian travel and aviation organizations actually publish, scored — the country that authored the travel industry's flagship standard, and the market where...
The State of Artificial Intelligence APIs
4,904 AI companies scored — the industry selling agents produces a machine-readability distribution indistinguishable from the average of every other industry in the c...
The State of Developer Tools APIs
The best-scoring industry in the catalog — first of twenty-five — and it publishes idempotency at the same 2.8% rate as the worst. The gap was never competence.
The State of Cybersecurity APIs
The second-best-scoring market in the catalog — and 72% of it will not tell you how to report a vulnerability, now that the EU Cyber Resilience Act requires exactly that.
The State of API Management
What thirty-five API management platforms, gateways and data planes actually publish, scored — the market that sells other people their API practice, measured on its o...
The State of Supply Chain APIs
The industry that moves the physical economy publishes idempotency at 1.2% — thirteen companies out of 1,124 — in the one market where a retried request dispatches a s...
The State of Compute & Hardware APIs
The companies that rent the chips score 36.5. The companies that design and fabricate those same chips score 10.7. NVIDIA scores 31.1 and NVIDIA NIM scores 75.7.
The State of Digital Health APIs
The market with the best standard and the most mandates publishes consent as a machine-readable surface at 3.4% — the same rate as the rest of the catalog, in the one ...
The State of Data & Analytics APIs
One of the best-scoring markets in the catalog — and the segment selling "know your data" is the worst-scoring segment inside it, publishing a contract 13.4% of the ti...
Your market not here yet?
Market Reports are built one cohort at a time, and the queue is driven by demand. Tell me the industry — and the country, if the regulatory regime changes the answer — or the technology cohort nobody has measured.