Elva

About Elva

Elva is an API management tool built by the team behind Theneo. It discovers APIs directly from code repositories, builds a catalog without requiring a spec, and lets teams create contracts that control which endpoints and fields are exposed to different audiences. The tool also runs hosted MCP servers with authentication and tracks agent activity as code evolves.

Review

Elva entered public launch this week after testing with a small group of customers. It addresses a specific shift the makers observed: some of their Theneo users now get more API calls from AI agents than from human developers. The tool tries to bridge the gap between traditional API management and the needs of agent-driven consumers, though it's early days for the product.

Key Features

• API discovery from code. Connect a repository and Elva scans the codebase to map out APIs, usage patterns, and check AI readiness without needing an OpenAPI spec.
• Audience-specific contracts. Choose which endpoints and fields a particular customer, partner, or agent gets access to, then publish to docs platforms, mocks, or MCP servers.
• Hosted MCP servers with auth. Elva runs MCP servers, manages authentication, and enforces permissions at the tool and resource level rather than just at the server boundary.
• Agent observability. Track which agents and users are calling which tools, see latency and error rates, and collect feedback directly from agents when something fails.
• Change review workflow. When code changes and APIs drift, Elva flags the differences. Teams can configure automatic sync or require manual approval with reviewer notifications.

Pricing and Value

Elva is listed as free at launch. The makers haven't published a long-term pricing model yet, so it's unclear whether the current free access is a limited-time launch offer or the permanent plan structure. Teams evaluating it for production use should clarify this directly.

Pros

• Discovers APIs from code without demanding a spec upfront, which reduces setup friction for teams with incomplete or outdated documentation.
• MCP hosting includes per-tenant authentication, scoped credentials, and separate usage analytics - shared infrastructure with isolated identity and observability.
• Agent readiness checks evaluate concrete factors like schema clarity, error handling, and whether an agent can complete real tasks end-to-end, not just whether the server validates.
• Change detection flags API drift and supports both automatic deployments and governed review flows with stakeholder notifications.
• CLI access is available and documented, with more CLI updates on the roadmap.

Cons

• The product just launched publicly this week, so there's no track record for stability at scale or long-term maintenance patterns.
• Pricing beyond the current free launch period isn't defined, making budget planning difficult for teams considering adoption.
• Teams that don't have AI agents consuming their APIs - or don't plan to - won't find much use for the MCP hosting and agent readiness features that form a large part of the tool.

Elva fits teams that already see agent traffic hitting their APIs and need a way to manage that alongside human consumers. It's also relevant for organizations preparing their APIs for agent consumption and wanting to test readiness before exposing endpoints. Smaller teams with straightforward, human-only API consumers likely won't need what Elva does right now, but those straddling the line between developer experience and agent experience will find the catalog-plus-contracts approach worth a look.

Open 'Elva' Website