Summary
Client code stops being written against a stale copy of the spec.
The spec is pulled from the Apifox project on demand and refreshed on request, so an assistant writing a request body is reading the definition your team edits rather than a file committed months ago. $ref targets resolve through their own call, which keeps a spec that has been split across files fully readable.
What it is
Three tools over one Apifox project's OpenAPI Spec: read the spec, read the files its $ref entries point at, and re-download the latest copy from the server.
What you get
- The project's OpenAPI Spec read in full
- The files behind $ref entries fetched, several at a time by path
- The spec re-downloaded from the server when it has moved on
Requirements
An Apifox access token in `APIFOX_ACCESS_TOKEN` and the id of the project to read. npx on your PATH.