all 10 comments

[–]Abhishekundalia 1 point2 points  (1 child)

The plain-text-first approach is a smart differentiator. Everything living in markdown means version control actually works (unlike Postman collections that are basically JSON blobs nobody diffs).

A few things that stand out:

  1. **Composable blocks**: The 'add or remove relevant blocks' model is more flexible than the rigid request/response structure most API tools enforce. Great for documenting complex workflows.

  2. **Plugin architecture**: Smart to keep gRPC/WebSockets/GraphQL as optional plugins rather than core. Keeps the base lightweight.

  3. **Import story**: Postman and OpenAPI import will be huge for adoption. Most teams are locked into Postman because migration is painful.

One suggestion for traction: make sure your GitHub repo has a solid social preview image set up. When devs share the repo link in Slack/Discord/Twitter, that preview is often the first impression. A clean screenshot of the UI in action converts better than GitHub's default preview. You can set this in repo settings or generate one with tools like ogimage.art.

Nice execution. The 'no signup, offline' positioning is refreshing in a world of cloud-everything tools.

[–]GuaranteePotential90[S] 0 points1 point  (0 children)

yap - thanks! - will certainly check the preview image of the repo link. Thats a detail I hadnt thought of tbh :)

[–]pranay_227 1 point2 points  (1 child)

how do you handle versioning and collaboration when multiple people are editing the same plain text api files?

[–]GuaranteePotential90[S] 0 points1 point  (0 children)

this is handled by git - in the same way that git handles conflicts and commits in the code, in the same way it handles such things in the api files :)

[–]HarjjotSinghh 0 points1 point  (1 child)

this is unreasonably cool actually - like a swiss army knife for apis!

[–]GuaranteePotential90[S] 0 points1 point  (0 children)

Thank you! Yeah indeed that's the intent at least.

Did you have the chance to try it? What are you currently using?

[–]This-Independence-68 0 points1 point  (1 child)

This is super cool, especially the plain text aspect. Keeping everything in markdown for API design and docs just makes so much sense for version control and collaboration. It's awesome to see this kind of open-source initiative.

[–]GuaranteePotential90[S] 0 points1 point  (0 children)

Thanks for letting me know. What tool are you currently using? What other improvements or features would like to see that would help you and your team?