Zendesk for StartupsUp to 2 years free for startups + AI Agents & Copilot
Promoted
Launching today
Elva
Goodbye, Postman. Your APIs have new consumers
45 followers
Goodbye, Postman. Your APIs have new consumers
45 followers
Developers use your APIs. Now agents do too. Elva discovers APIs from code, lets you choose what each audience can use, and runs your MCP servers with auth and analytics. Track agent activity and review changes as your code evolves
Theneo
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?
Solid MCP host. When one server serves different audiences, how do you keep auth and usage analytics separate?
@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!
Theneo
@tehreem_fatima5 thanks, and honestly it depends on team and size of organization. Some have automatic sync, others have very extensive governance in place. You might have several reviewers or approvers before changes are published. Depends on organization, teams, use case (internal, partner, public)