How Elva reads a repo: from route handlers to OpenAPI 3.1
Static analysis, framework fingerprints, and the messy middle where code and spec disagree.
25 stories
Static analysis, framework fingerprints, and the messy middle where code and spec disagree.
Everything that shipped this month, including the schema editor and per-key usage.
Partners, internal teams, the public, and agents all need different views of the same endpoints. Contracts make that explicit.
Description coverage, schema completeness, auth clarity, and the weights behind the grade.
Per-agent activity, tool-level latency, and catching the schema gap before Claude does.
Half the APIs that matter have no OpenAPI file. The catalog has to start from code, not from paperwork.
Ninety days of production MCP traffic in numbers: retry storms, timeout cliffs, and why one ambiguous error string cost more than any outage did.
Showing 25 of 25 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