It's always the "it depends" kind of answer.
In bigger companies, you have teams dedicated to API governance, whatever they say, it's how it's done. In early-stage startups, you have full-stack folks doing end-to-end design, test, integrate with UI, document, etc. The trickiest ones are the ones that are in between these two stages. It's where it gets messy, and you MUST have something in place to serve as an API contract. Swagger dominates that, imho, Postman collections and docs are used a bit differently in my experience.
I'm helping build https://voiden.md which serves as a unified place for API spec, test, and documentation, but there are also plenty of API tools that focus solely on endpoint execution.
Hi, thx for the feedback!
Testing the settings (including different themes and font sizes as we speak).
Some tweaks are been made on the responses side as well.
As per the rest of your comments, some of these things have been discussed or touched upon, others have been just added to the discussion board :)
I'm helping build Voiden: https://voiden.md
But am thinking of a LOT these days, really, saw a bunch of interesting APIs on https://apyhub.com/catalog recently, so might go on and tackle a few of these.
I mean, IF the API is primarily tailored for UI presentation, there's already a text/html that you can use. I don't see the real problem here. Unless it's a type of API that has multiple purposes. In which case you got to tailor the response/presentation based on the needs.
Either way, the time needed to build a HTML elements will be eventually spent somewhere, on the server or on the client side. Server provides you with the data, you pick the form in which it is sent, and then work around the presentation layer.
I'm helping up the team behind https://voiden.md so I can tell you, it's easy to present the HTML even in the API clients, let alone the website itself.
A TL;DR of it is that for teams behind APIs, building, documenting, and testing APIs feels all over the place nowadays. It's a pain, it wastes time, causes errors, and frustrates everyone involved.
This post dives into why API tooling is such a headache, why the industry keeps making it worse, and how Voiden attempts to make life easier for developers.
Totally agree on this. There are things that belong in cloud, even a 3rd party one. Not everyone has a luxury of self-hosting. But keeping API secrets in any 3rd party cloud is just insane imho.
Something internal, or did you publish it?
What would you say is the most important stuff to you? Only simple API testing, or you gotta take care of the specing and documenting it as well.
Pay-per-seat works well when no proper competition to go against it.
What we built with http://voiden.md should be free forever, with monetization on plugins, but only the ones that introduce costs to the team.
The blessing was that the team was already profitable on another tool, and VC-independent, so nobody shoved some dumb design decisions down anyone's throat.
I mean, isn't that a good thing?
At least there won't be any security concerns during the outage. (:
People are just used ot it. Even with all the bloat. I'm helping up the http://voiden.md folks in an attempt to build an actual API devtool, not a tab+click API SaaS platform.
A helping hand to Ebiose AI here.
I’m super excited to see the project go open source.
There is already some literature about improving agents through the evolutionary process (not only AlphaEvolve). And others are talking about AIs that build other AIs, which is sometimes called ADAS, for Automatic Design of Agentic Systems.
We have already experienced this, notably on math problems.
But here, with the community, the goal is really to trigger the self-improving process.
The only way to do so is to challenge Ebiose with real use cases so that reusable agent components emerge organically and evolve over time.
TL;DR Voiden, a free, offline API workspace, decided to say no to SaaS "Teams" features because they're:
1) bloated,
2) expensive, and
3) break developer workflows.
Git is the real collaboration engine. It's free, familiar, and tied to your codebase.
Much appreciate the feedback! Took it to the team already. I waited to get a confirmation for your question before answering, so here it is: it's built on top of tiptap + codemirror.
I'm helping build https://voiden.md/ We just dropped a major beta, FOSSing it by the end of the year.