CharonITE started as a weekend fix for a familiar problem — In the current world your platform runs on API's which plays a key role in the ecosystem maintaining the collection and manually configuring them is a huge task and time consuming for the Developers and current tools store your data out of your platform in Cloud which questions your Data security .
Every team we talked to had the same story: a wiki page or a Postman collection that used to be accurate, gradually falling out of sync as services were added, routes changed, and services got swapped in and out.
Meanwhile, CharonITE's Admin API already holds the current, correct answer — it just isn't in a shape anyone can hand to a teammate or drop into a request tool.
CharonITE is deliberately narrow in scope. Here's what guides the decisions we do make.
CharonITE only ever issues GET ,Create requests to your Admin API. It can't modify, or delete anything on your gateway — there's no code path that does.
Collections export as Postman v2.1 JSON on purpose. We'd rather target a format your other tools already open than invent our own.
CharonITE doesn't phone home. What it fetches from your Admin API stays on your machine unless you choose to share the exported file.
A tool that reads your API surface should be predictable. We'd rather ship fewer features than ship ones that surprise you.
CharonITE is MIT-licensed. Read the code, file an issue, or send a patch.