SODAX SDKDigital asset flows you can build and deploy with AI.
Promoted
Launching today
Elva
Goodbye, Postman. Your APIs have new consumers
141 followers
Goodbye, Postman. Your APIs have new consumers
141 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
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.
Theneo
@mark_smith_1 yes, we have a CLI, its in our docs + we have more updates coming from our CLI + incorporating with your agents
How does this fit with a team that already has docs somewhere else, can you publish into an existing setup?
Theneo
@nika_buliskeria2 Hey Nika, yes, while we would love for you to use @Theneo by default, we offer other doc sites like @Mintlify and soon also Readme and other tools will be added
@ana_robakidze Nice, that flexibility matters. Does publishing to Theneo or Mintlify keep everything in sync going forward, or is it more of a one-time export?
Theneo
@nika_buliskeria2 yes its an automatic sync. you can add additional governance checks as well, depending on your use case. and can have approval process, which currently Mintlify dooesnt have any governance for their api specs, so this additional layer could be helpful
@ana_robakidze That sounds amazing! I will give it a try
@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)
Dial
"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?