The engineering story: deliberately conventional tools, a tested OpenAPI core, and a repository a newcomer can navigate in an afternoon.
Typed end to end. Components organized by surface — endpoint views, schemas, notes, AI — with shared hooks for routing, theming and persistence.
One deliberately inlined production bundle (dist/index.js) so static deployments never worry about chunk filenames — guarded by a verification script on every build.
Utility-first styling over a CSS-variable theming system, with the Phosphor icon set throughout.
The industry-standard editor powers raw JSON bodies, schema inspection and code viewing.
Optional engine validation and external reference resolution, with errors surfaced as scoped diagnostics rather than fatal failures.
Specs, response history, notes, panel widths and workspace state persist through a resilient storage layer with a localStorage fallback.
| Path | Contents |
|---|---|
| src/ | The application — components, hooks, contexts, pages, types and utilities |
| src/utils/openapi/ | The OpenAPI engine: parsing, normalization, validation, references, serialization and capabilities |
| src/utils/runner/ | Request planning, execution, response handling and the recursive body-form logic |
| server/ | The hardened AI gateway (ai-gateway.ts) and its policy module |
| proxy-agent/ · ai-gateways/ | Proxy agent (spec download + request proxy) and AI gateway reference implementations in six and nine frameworks |
| scripts/ | Build support: SPA fallback, single-bundle verification, UI contracts, the builder CLI |
| tests/ | Unit suites plus the Playwright browser suite |
| docker/ · site/ | Docker packaging and this website |
The suite covers the OpenAPI normalization matrix, parameter serialization, Swagger 2.0 conversion, async behavior and conformance — plus a Playwright browser suite over the real UI.
