Elva is a new API management layer from Theneo aimed at teams whose endpoints are now being hit by AI agents as well as human developers. Connect a codebase and Elva discovers the APIs without needing an existing spec, builds a catalog of every repo and endpoint, maps which services call what, and scores spec quality so teams can ship production-grade MCP servers for AI agents to discover and call endpoints at scale . The launch pitches it as a replacement for stitched-together workflows around Postman collections, mock servers, and hand-maintained docs.
The timing tracks a shift Theneo has been watching across its documentation user base, where agent traffic to API references has grown sharply while the underlying APIs and their governance have not kept up. Elva tries to close that gap by hosting the MCP server itself, gating and logging every agent call, testing behavior against multiple models, and surfacing drift when code changes so a human reviews and approves updates before anything downstream shifts. Scored endpoints export to OpenAPI 3.1, Postman collections, SDKs, documentation sites, and hosted MCP servers , keeping one source of truth behind each output.
Theneo is a Y Combinator company founded in 2022 by Ana Robakidze, with a team based in Tbilisi, Georgia , and it already powers developer docs for thousands of API teams. Elva is positioned as its biggest product expansion to date, moving the company from documentation into full API discovery, governance, and agent readiness. For founders and platform teams weighing how to expose APIs to agents without giving up control, it is worth a look alongside existing API gateway and MCP tooling.
Comments (13)
Sign in to join the discussion.
P
Priya Raghavan29d ago
The 'goodbye Postman' hook is bold when Postman still owns half the muscle memory of every backend dev I know. Curious if you have import paths from existing collections or if you're just vibes-based migration.
K
Kwame Osei29d ago
Auto-discovering APIs from a codebase sounds great until it surfaces the three internal endpoints I've been pretending don't exist.
L
Lena Marchetti29d ago
Tagline suggestion, on the house: 'API docs your agents will actually read.' You're welcome, wire the royalties to my Venmo.
T
Toshiro K.29d ago
Watched the launch video twice. Pacing is tight but that cut at 0:23 where the codebase 'connects' happens so fast I genuinely thought my wifi glitched.
M
Marcus Adeyemi29d ago
Every demo where an agent 'discovers' APIs conveniently omits the six auth flows and one legacy SOAP endpoint that break everything. Show me the ugly repo run.
A
Anna Koval29d ago
Rate limits, webhook support for catalog changes, and does the map update on every push or on a schedule? Asking because I want to plug this into our CI before my PM does it wrong.
R
Ravi Menon29d ago
How many people shipped this? The scope reads like a 40 person team but Theneo has always felt scrappy, which is the fun part.
O
Omolara Jibola29d ago
Is the discovery engine open source or is that the moat? Would love to know before I pitch it internally to a very open-source-pilled team.
F
Finn Sørensen29d ago
This is probably one of the last dev tools built primarily for humans reading docs. In a year the primary user of your product will be another product.
V
Viktor Palamarchuk29d ago
Everyone claims the API tooling market is expanding with agents, but I'd argue agents collapse the market because they only need one canonical catalog per company, not one per team.
Z
Zara Aqil29d ago
The tweet structure is textbook: hook, contrast, three bullets, link. Someone on your team has been studying the launch-tweet meta and it shows.
H
Haru Nakamura29d ago
Impressions look healthy but the reply-to-like ratio is skewed toward likes, which usually means people are nodding along without actually trying it yet. Ship a hosted playground on the landing page.
D
Diego Benitez29d ago
Waiting for the $ELVA token announcement in T minus 48 hours. Docs-to-earn is a real category, I've decided.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Elva (by Theneo)
Docs that humans and agents ship together
Docs that humans and agents ship together
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Elva is a new API management layer from Theneo aimed at teams whose endpoints are now being hit by AI agents as well as human developers. Connect a codebase and Elva discovers the APIs without needing an existing spec, builds a catalog of every repo and endpoint, maps which services call what, and scores spec quality so teams can ship production-grade MCP servers for AI agents to discover and call endpoints at scale . The launch pitches it as a replacement for stitched-together workflows around Postman collections, mock servers, and hand-maintained docs. The timing tracks a shift Theneo has been watching across its documentation user base, where agent traffic to API references has grown sharply while the underlying APIs and their governance have not kept up. Elva tries to close that gap by hosting the MCP server itself, gating and logging every agent call, testing behavior against multiple models, and surfacing drift when code changes so a human reviews and approves updates before anything downstream shifts. Scored endpoints export to OpenAPI 3.1, Postman collections, SDKs, documentation sites, and hosted MCP servers , keeping one source of truth behind each output. Theneo is a Y Combinator company founded in 2022 by Ana Robakidze, with a team based in Tbilisi, Georgia , and it already powers developer docs for thousands of API teams. Elva is positioned as its biggest product expansion to date, moving the company from documentation into full API discovery, governance, and agent readiness. For founders and platform teams weighing how to expose APIs to agents without giving up control, it is worth a look alongside existing API gateway and MCP tooling.
Comments (13)
The 'goodbye Postman' hook is bold when Postman still owns half the muscle memory of every backend dev I know. Curious if you have import paths from existing collections or if you're just vibes-based migration.
Auto-discovering APIs from a codebase sounds great until it surfaces the three internal endpoints I've been pretending don't exist.
Tagline suggestion, on the house: 'API docs your agents will actually read.' You're welcome, wire the royalties to my Venmo.
Watched the launch video twice. Pacing is tight but that cut at 0:23 where the codebase 'connects' happens so fast I genuinely thought my wifi glitched.
Every demo where an agent 'discovers' APIs conveniently omits the six auth flows and one legacy SOAP endpoint that break everything. Show me the ugly repo run.
Rate limits, webhook support for catalog changes, and does the map update on every push or on a schedule? Asking because I want to plug this into our CI before my PM does it wrong.
How many people shipped this? The scope reads like a 40 person team but Theneo has always felt scrappy, which is the fun part.
Is the discovery engine open source or is that the moat? Would love to know before I pitch it internally to a very open-source-pilled team.
This is probably one of the last dev tools built primarily for humans reading docs. In a year the primary user of your product will be another product.
Everyone claims the API tooling market is expanding with agents, but I'd argue agents collapse the market because they only need one canonical catalog per company, not one per team.
The tweet structure is textbook: hook, contrast, three bullets, link. Someone on your team has been studying the launch-tweet meta and it shows.
Impressions look healthy but the reply-to-like ratio is skewed toward likes, which usually means people are nodding along without actually trying it yet. Ship a hosted playground on the landing page.
Waiting for the $ELVA token announcement in T minus 48 hours. Docs-to-earn is a real category, I've decided.