llms.txt → Markdown docs → no key → the next three departures from Oslo S.
Destatis · Germany
Blocked
The page says “free of charge and without registering.” The API says Code 15: your access data cannot be recognised.
This is how your API is met now: not by a developer reading your portal, but by software that has never heard of you.
02 / 20
How I looked: outside-in, the same yardstick as the market
~200
public bodies, agencies, cities and platforms
28 + EU
countries
~38,000
commercial providers scored on the same rubric
Machine-readable contract · documentation · onboarding · authentication · versioning · terms · support · discovery and agent-readiness signals. Only what you can find without a phone call.
03 / 20
Two populations, not one
Level
Bodies
Median Kin Score
Agent readiness
State-owned operators
9
53.6
23.8
Independent intermediaries
7
46.0
39.7
Shared national platforms
10
35.8
20.7
National bodies
121
12.3
8.3
Regional
15
11.8
4.9
Municipal
33
9.6
3.9
The long tail is open-data portals, not APIs. Cities that run API programmes sit apart: Amsterdam 41.7 · Gent 40.3 · Kanton Zürich 37.5 · Hamburg 35.1.
04 / 20
The gap is whether there is a contract, not how good it is
26%
of government bodies publish a machine-readable contract
36%
of commercial providers do
40.4 vs 43.8
median score once there is one: government vs commercial
With a contract, government is ahead on contract quality and operational transparency, and behind on access: sign-up, plans, support, getting started.
05 / 20
Domain by domain: where government leads, and where it lags
Domain
Best government
Commercial counterpart
Weather
Met Office 63.6
Tomorrow.io 57.9 · OpenWeatherMap 57.4
leads
Transport
Entur 69.6
Transitland 53.1
leads
Mapping
Ordnance Survey 58.0
Mapbox 51.0 · TomTom 44.4
leads
Payments
PagoPA 69.0
Stripe 82.7 · Adyen 73.5
lags
Health
NHS England 48.1
Epic 62.5 · Redox 62.3
lags
Company data
KVK 57.6
Dun & Bradstreet 60.7
lags
Where government is the natural operator, its best APIs beat the market. Where the market has been at it longer, government trails.
06 / 20
Often the best “government API” isn’t the government’s
Spain · company register
80.3
OpenMercantil republishes the BORME registry with an OpenAPI at its root, an llms.txt and no key. It beats every official register we scored, and Dun & Bradstreet.
Germany · federal APIs
bund.dev
The de facto federal API catalog is a volunteer civic project, signed “die Zivilgesellschaft™.”
When the state doesn’t publish the contract, someone else does. The question is whether you want to be that someone.
07 / 20
National strategies: on paper, or in the artifacts?
Country
Bodies
Publish a contract
Median
Reading
Netherlands
5
4
46.1
shows up
Estonia
3
3
39.6
shows up
Norway
5
4
37.5
shows up
Czechia
3
3
36.8
shows up
United Kingdom
34
15
17.6
where there’s a service
Sweden
9
1
13.1
surprise [verify]
Germany
14
1
12.4
guidance only
Italy
24
2
9.8
visible from inside
Where a strategy comes with a mandate and a shared platform, it shows up body by body.
Italy
PagoPA scores 69.0, among the best in Europe. Yet only 2 of 24 Italian public bodies show a contract publicly.
The interoperability guidelines are real. The APIs travel through PDND, between accredited administrations. From the outside, the strategy is almost invisible.
09 / 20
The law already asks for APIs: High-Value Datasets
Implementing Regulation (EU) 2023/138: since June 2024, these six categories must be free, machine-readable and available via APIs. Member states report them to data.europa.eu, so we can compare what is reported with what answers.
10 / 20
What member states report
29,582
datasets flagged High-Value
65%
reported by Germany alone, mostly map services
115
for companies & ownership, EU-wide
6
member states report none
Poland, Hungary, Romania, Bulgaria, Slovenia and Cyprus report nothing. The Netherlands, the quality leader, reports 30. Reporting is not quality, and quality is not reporting.
11 / 20
What answers when you call the reported endpoints
A real API26%
A file or data payload31%
An HTML page22%
Nothing (dead)21%
One in five legally reported endpoints doesn’t answer. For companies, 2 of 65 sampled answered as an API.
12 / 20
The standards Europe actually runs on
OGC WMS19,085
OGC WFS4,767
INSPIRE Atom1,118
OGC API Features~388
OpenAPInot in top 40
Plus SDMX, PxWeb and JSON-stat, NeTEx, SIRI and GTFS, DATEX II, DCAT-AP, NGSI-LD, Esri REST. Europe’s public data is many standards, not one.
The bridge
The next generation of Europe’s geodata, OGC API, is described in OpenAPI.
6 of the 7 OpenAPI endpoints in the sample were OGC API Features services. As Europe migrates off WMS and WFS, its geodata lands in OpenAPI governance.
14 / 20
What separates the APIs people can build on
Practice
Top tier (40+, n=21)
Everyone else (n=136)
Publishes a machine-readable contract
100%
13%
Documents its authentication
100%
9%
Privacy and terms reachable from the API
90%
8%
Servers resolve to a real host
84%
10%
A named support channel
76%
10%
Documented error behaviour
74%
3%
Publish the contract. Say how auth works. Make the servers real. Document errors. Put a human behind it.
15 / 20
16 agent runs against European government APIs
11
got a real answer
5
blocked at a registration wall
0
found the API through /.well-known/api-catalog
2
had a useful llms.txt, and one isn’t a government
Discovery is still web search, and 11 of 16 agents leaned on something they already knew. A genuinely cold agent would do worse.
16 / 20
Signals that mislead machines
Well-known files that answer 200 with an HTML page: present to a naive probe, empty in reality.
A production Swagger UI serving the petstore demo.
“Swagger” links that point at nothing in a national catalog.
Pages that say “open, no registration” over APIs that say “key required”.
A person shrugs these off. An agent believes them, or gives up.
17 / 20
Governments already write API rulesets. Separately.
Logius · NL API Design RulesVNG Realisatie · Haal CentraalEntur · API guidelinesPagoPADevelopers Italia · OAS checkerpubliqHMCTS
Seven public bodies in five countries, each maintaining its own ruleset on the same open-source linter format, mostly encoding the same decisions.
OpenLint
A shared, specified, vendor-neutral home for API governance rules.
A ruleset specification any tool can implement · rulesets that run unchanged · hosted by Open Source Europe · built in the open. openlint.org
19 / 20
Beyond OpenAPI: the governance layer every standard is missing
Standard
Conformance today
Shared governance rules
OpenAPI · OGC API
OGC TEAM Engine
OpenLint
OGC WMS / WFS · INSPIRE
INSPIRE Reference Validator
none
SDMX · JSON-stat
SDMX validators
none
NeTEx · SIRI · GTFS
GTFS validator, NeTEx profiles
none
DCAT-AP
SHACL shapes
none
Validators answer “does this conform?” Governance is everything a body decides on top. That has no shared home yet. The OpenLint format is rules over structured documents, not OpenAPI alone.
20 / 20
What every team in this room can do on Monday
Publish the contract
Document authentication
Make the servers real
Document errors
Put a human behind it
Serve /.well-known/api-catalog
Write an llms.txt
Say “key required” where it is
Ask me for your personalized checklist: the same rubric, itemized for your API.