
I’m getting ready for APIdays Paris in December, where I’m moderating the EU government track and giving its keynote on what Europe’s government APIs look like from the outside, the way a developer, a business or an AI agent meets them. Part of that work has been reading the public API surfaces of about 170 government agencies, ministries and public platforms across Europe. One thing stood out, and it belongs here first.
Governments already govern their APIs with rulesets
When a public body takes API governance seriously, it reaches for the same tool. Here are rulesets I found published in public bodies’ own repositories, all in the Spectral format OpenLint carries forward:
- Logius maintains the Dutch government’s API Design Rules, and ships a Spectral linter with them. As we wrote last week, developer.overheid.nl now runs that tooling on OpenLint.
- VNG Realisatie, which builds shared services for Dutch municipalities, keeps a ruleset in Haal-Centraal-common for the Haal Centraal APIs.
- Entur, Norway’s national public transport platform, publishes its API guidelines with a Spectral ruleset alongside.
- PagoPA, the Italian state company behind pagoPA, the IO app and the PDND interoperability platform, lints contracts in repositories like pn-mandate and interop-be-monorepo.
- Developers Italia built its OAS checker for the Italian public administration’s interoperability guidelines on the Spectral engine.
- publiq, which runs Flanders’ culture and leisure data platform, keeps rulesets per API in its API docs.
- HM Courts & Tribunals Service in the UK lints at least some of its API contracts in the repository, for example this crime hearing results API.
That’s seven public bodies in five countries. It’s a floor, not a census, because I only counted what I could trace to the body’s own repository.
Each one is on its own
Every one of these rulesets is maintained separately. Most of them encode the same handful of decisions: use OpenAPI 3, describe your errors, version consistently, document authentication, name things one way. Each team wrote those rules again, keeps them current again, and carries the risk of a tool it doesn’t control.
That last part isn’t theoretical. This summer’s Spectral supply chain incident is why developer.overheid.nl moved. Every team on that list depends on the same format, and until OpenLint none of them had a say in where it went.
What OpenLint changes
OpenLint gives this work a shared, vendor-neutral home:
- A specified format. The ruleset specification means a ruleset gives the same result in every tool that implements it, so a national standard doesn’t depend on one linter.
- Rulesets that work unchanged. The Dutch rulesets ran on OpenLint without changes. Every ruleset in that list should too, and we’d like to hear if one doesn’t.
- Sharing instead of rewriting. Once the format is stable, the common rules can live in one open place, with each government layering its own on top.
- A neutral home. OpenLint is hosted by Open Source Europe, so no single vendor holds it.
Come find us in Paris
If your agency publishes API design rules, or lints contracts in a pipeline, I’d like to talk before or during APIdays Paris. Bring your ruleset. We’ll run it on OpenLint and tell you what happens. Until then, you can try the migration from Spectral, join office hours on Thursdays, or start a thread in Discussions.
