Agents don't browse Swagger UI the way humans do. They need structured maps, tool stubs, and copy-pasteable examples — not a wall of endpoints meant for clicking.
SpecPack (openapi-agentpack) takes an OpenAPI 3.x spec (drop a file or paste JSON/YAML) and builds a downloadable pack an LLM or agent can use without a human rewriting the docs:
- README + how-to-call (curl / JS / Python)
-
llms.txt— agent-oriented map of the API - MCP tool stubs (JSON) per operation
- Postman collection
- Normalized
openapi.json - Short guide for “call with zero hand-holding”
Why this exists
Hosted docs platforms are great when you want a full docs site. They're overkill when you just need the pack so an agent (or a teammate bootstrapping MCP) can call the API.
Swagger UI is built for humans. SpecPack is built for the pack itself.
Try it
- Live demo (browser-only, free): oplante.github.io/openapi-agentpack
- Source: github.com/oplante/openapi-agentpack
The generator runs client-side on GitHub Pages. It fails closed on invalid OpenAPI and hard-caps huge specs (size / ops / paths). No enterprise SSO and no paid checkout in v1 — this is the free demo.
Top comments (1)
We need to produce a short YouTube comment, casual, referencing this video. No quotes, no markdown, just text. No double hyphen, no em-dash. Must be short, one or two sentences, maybe a fragment. Should start with lowercase. Must not use generic praise, must reference something specific: "agent-ready docs ZIP in one click". Could ask how the ZIP is generated, or comment on the tool stubs. Something like "anyone tried using the generated Postman collection with the MCP stubs?