API Evangelist

Keynote: What Europe’s Government APIs Look Like From the Outside-In

APIdays Paris 2026 · EU Government Track

Kin Lane
API Evangelist
[email protected]

01 / 20

An agent meets two government APIs

Entur · Norway

5 calls

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

LevelBodiesMedian Kin ScoreAgent readiness
State-owned operators953.623.8
Independent intermediaries746.039.7
Shared national platforms1035.820.7
National bodies12112.38.3
Regional1511.84.9
Municipal339.63.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

DomainBest governmentCommercial counterpart
WeatherMet Office 63.6Tomorrow.io 57.9 · OpenWeatherMap 57.4leads
TransportEntur 69.6Transitland 53.1leads
MappingOrdnance Survey 58.0Mapbox 51.0 · TomTom 44.4leads
PaymentsPagoPA 69.0Stripe 82.7 · Adyen 73.5lags
HealthNHS England 48.1Epic 62.5 · Redox 62.3lags
Company dataKVK 57.6Dun & Bradstreet 60.7lags
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?

CountryBodiesPublish a contractMedianReading
Netherlands5446.1shows up
Estonia3339.6shows up
Norway5437.5shows up
Czechia3336.8shows up
United Kingdom341517.6where there’s a service
Sweden9113.1surprise [verify]
Germany14112.4guidance only
Italy2429.8visible 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

GeospatialEarth observation & environmentMeteorologicalStatisticsCompanies & ownershipMobility
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

PracticeTop tier (40+, n=21)Everyone else (n=136)
Publishes a machine-readable contract100%13%
Documents its authentication100%9%
Privacy and terms reachable from the API90%8%
Servers resolve to a real host84%10%
A named support channel76%10%
Documented error behaviour74%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

StandardConformance todayShared governance rules
OpenAPI · OGC APIOGC TEAM EngineOpenLint
OGC WMS / WFS · INSPIREINSPIRE Reference Validatornone
SDMX · JSON-statSDMX validatorsnone
NeTEx · SIRI · GTFSGTFS validator, NeTEx profilesnone
DCAT-APSHACL shapesnone
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

  1. Publish the contract
  2. Document authentication
  3. Make the servers real
  4. Document errors
  5. Put a human behind it
  6. Serve /.well-known/api-catalog
  7. Write an llms.txt
  8. Say “key required” where it is
Ask me for your personalized checklist: the same rubric, itemized for your API.

Thank you

Kin Lane  •  [email protected]