Guide 7 min read
Onboarding your organisation's APIs to spec0, step by step
A practical walkthrough: get your specs in from GitHub or the CLI, put them under governance, register who consumes them, and make them queryable by your agents.
ReadBlog
Writing on the consumer side of APIs.
Deep dives on API governance, drift, ownership, and what changes when the heaviest reader of your APIs is an agent. Written from the trenches, not the megaphone.
CLI 9 min read
Agents can't click your dashboard, but they can drive your CLI
Every internal tool now has a class of user that cannot see a screen. The CLI, long treated as the fallback interface, is the one they can operate, and most CLIs were never built to be operated.
Read Leadership 8 min read
Engineering leaders cannot see their own API landscape
How many APIs do we have, which are healthy, where is the coupling risk? The questions a director should read off a screen are instead answered by asking around.
Read Agents 8 min read
Pasting your OpenAPI spec into Cursor costs 150k tokens and is stale by lunch
Handing an agent the whole spec so it knows one endpoint is the wrong unit of work: you pay for the entire document on every turn, and the copy is a snapshot the moment you paste it.
Read Mock servers 9 min read
A hand-built mock is a second API you have to keep in sync, and you won't
A mock exists to unblock the people waiting on your API. The moment you maintain it by hand it becomes a second source of truth, and the people building against it are building against a fiction.
Read Ownership 8 min read
API ownership belongs to teams, not people
Ownership pinned to a person is a fact with an expiry date. The first reorg, the first resignation, and the record of who owns what is quietly wrong.
Read Drift 9 min read
Your OpenAPI spec stopped matching production months ago
Nothing forces a spec to change when the code does, and nothing breaks when it doesn't, so the document quietly stops describing the API while everyone keeps trusting it.
Read API governance 10 min read
Nobody knows who consumes your APIs, and that is why governance fails
Every API governance failure I have watched up close comes back to one missing fact: the list of who depends on the thing you are about to change.
Read