Elva

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?

@ana_robakidze Really neat how Elva automatically syncs publishing rules whenever code changes. Curious to know how are you seeing most teams handle mock endpoints during agent testing? Upvoted and rooted for your success today!

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.

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