12 stories
We took routebase.dev from 87 to 100 on the open Agent-Friendly Docs Scorecard in one day. What failed, the four fixes, and the CDN header detail that nearly broke it.
We fetched 1,927 public OpenAPI specs again and compared each with its 2023 copy. About half had changed, and nine in ten breaking changes had no new major.
Repo or hosted is the wrong question. What decides whether your API has one contract or several is which copy the others derive from, and who runs that step.
Most style guides fail with too many rules, not too few. The work is deciding which rules stop a build, which leave a note, and which you will never enforce.
A linter flags a missing description, not a useless one, and the useless one is what an agent chokes on. What to write, what to leave out, and how to test it.
The Postman migration everyone postpones is mostly mechanical, and that is agent work. How an AI over MCP imports collections and rebuilds your assertions.
Every API contract decays once nothing enforces it. The four ways specs drift, why code generation does not save you, and how to make the spec true again.
Why every API needs exactly one error shape, how RFC 9457 Problem Details provides it, and the conventions that make it stick across every endpoint.
Six design decisions that make or break an API, from resource modeling, naming, and idempotency to pagination, error formats, and versioning, with examples.
AI agents are becoming API consumers. What that changes about API design, from descriptions as prompts and actionable errors to MCP as the new surface.
Two workflows for building APIs, and why the order you write the contract in changes everything downstream, from parallel work and review quality to drift.
What actually counts as a breaking change, why additive evolution beats version bumps, and how to run a deprecation your consumers will forgive.
Showing 12 of 12 stories
You're all caught up.
Get the top AI news and tools straight to your inbox every week.
Weekly · AI news
Join 15,000+ AI enthusiasts
