API Documentation
Automated API documentation without an OpenAPI specMost API doc platforms assume you already have an OpenAPI file. A researched map of what actually produces a reference doc when you don't: collection imports, AI write-ups, traffic discovery, and code-derived catalogs.7 min readOpenAPI articles and guides
OpenAPI in the real world: generating specs from existing code, keeping them true on every commit, and what to do when there is no spec at all.
5 posts, newest first · UpdatedAI Agents
API discovery platforms and marketplaces for AI agents in 2026A researched map of how AI agents and the teams building them find and call APIs at scale outside of MCP: public marketplaces, unified-API platforms, and OpenAPI-driven agent tool generation, and where each one stops short of governing who gets to call what.8 min readContracts
How teams maintain API contracts without a manual specA precise map of the tools people reach for to keep an API contract true without hand-writing one: schema-first frameworks, code-reading generators, contract testing, and drift detection, and where each one actually stops.8 min readOpenAPI
How to generate an OpenAPI spec from existing codeFour working ways to get an OpenAPI 3.1 spec out of a codebase that never had one, what each approach misses, and how to keep the result true.4 min readEngineering
How Elva reads a repo: from route handlers to OpenAPI 3.1Static analysis, framework fingerprints, and the messy middle where code and spec disagree.11 min readShip notes, monthly
One email with what shipped and what we learned. Unsubscribe anytime.
Ship APIs anything can call
Humans, tests, partners, agents. One catalog, one contract, one place.