Elva

This is super cool! I’m particularly interested in the “checks agent readiness” part - sounds like expanding into AX which is super critical.

Curious what are the parameters that Elva uses to determine agent readiness?

Elva’s approach to API contracts and governance looks useful for agent-facing APIs. How do you handle versioning and backward compatibility when a code change would break an existing MCP tool or consumer contract?

That YouTube thumbnail with Kill Bill concept is genius!

The MCP part is what really stood out to me here. Making APIs easier for agents to discover and actually use is a very real problem. Elva looks like a solid step in that direction. Congrats Ana and team!

"more API calls from agents than humans" is a real shift and the per-audience access split (developer vs partner vs agent) makes sense as a response to it. the part I'd want to poke at before adopting this is scope creep - once an agent has an MCP server with real auth, what stops it from chaining calls in ways nobody explicitly scoped for, versus a human hitting endpoints one at a time in Postman?

Solid product. Is there a CLI for it? If so, how can I use it. Can't wait to integrate this into my current workflow.

Do you support agent keys for different agents, so you can see which agent did what?

As the code base changes, when APIs change, how do the reviews get done: automatically flagging differences, or requiring approval every time?Btw, Congratulations @ana_robakidze & @mariam_lekveishvili1 ✌️

It is pretty straightforward to set up and get running. I like the MCP setup and the way it lets you test how the API works with agents. Seems like a useful tool for teams working on making their APIs agent-ready. Congrats on the launch!

How does this fit with a team that already has docs somewhere else, can you publish into an existing setup?

MCP is very smooth. I also really like the API spec grader, it really gives you an idea about what to improve and in what direction. Good luck on your launch! I will definitely be using this later.

Just tested it and it's very smooth. The MCP server generation especially, hadn't seen that anywhere else. Does the tool set scale well for an API with a lot of endpoints, or does an agent get overwhelmed?

Solid MCP host. When one server serves different audiences, how do you keep auth and usage analytics separate?

Hey Product Hunt, Ana here 👋Four years ago, I was fed up with Postman and wanted to replace it. I started with docs as a side project. That became Theneo. We got into YC, and today 20,000+ companies use it.Through Theneo, we’ve seen how messy API management gets. Now some of our customers get more API calls from agents than humans, while the way they manage those APIs has barely changed.That’s why we built Elva. We started with a few customers, and today we’re opening it up to everyone.You can connect your repo and Elva builds your API catalog, maps how it’s used, and checks AI readiness (fyi no spec required). From there, create contracts around actual use cases: choose the endpoints and fields a customer, partner, or agent needs. Publish to docs platforms like Theneo or Mintlify, mocks, or hosted MCP servers. When your code changes, review the updates or sync them automatically under your publishing rules.For MCP, we handle hosting and auth. You can test across models, see which tools are slow or failing, and collect feedback directly from agents when they get stuck.Would love for you to try it with your own repo. Does it cover how you actually manage your APIs? What are we missing?