Apidog

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me the API workflow that replaces Apidog — which is really four tools in one window.

The honest route is not to build an application: it is to assemble the free pieces around one file. **The OpenAPI description is the single source, and everything else is generated from it.**

STACK
- OpenAPI 3.1 in git as the source of truth
- Node 20+ with Fastify for anything hosted
- Spectral for rules, Prism for mocks, Scalar or Redocly for docs
- A test runner you already have — vitest, or hurl for plain HTTP tests
- Caddy in front

THE FOUR JOBS, EACH SOLVED

DESIGN
- Write the description in YAML, in the repository, reviewed in pull requests
- Spectral rules run in CI: required fields, naming, examples, error responses
- Breaking change detection against the previous version, failing the build unless the version moves

TESTING
- Generate a request per operation from the description with its example body, as a starting test file
- **Assert the response against the description's schema, not against a hand-written expectation.** A schema assertion catches the field that quietly changed type; a hand-written one does not
- Environments as files, secrets from the environment, never committed
- Run the whole suite in CI against a deployed preview

MOCKING
- Prism from the same file, with validation on. A frontend builds against it before the backend exists
- Examples in the description do double duty: documentation, mock responses and test fixtures from one place

DOCUMENTATION
- Built from the same file on merge and published as static files
- A try-it panel pointing at the mock or a sandbox, never at production

THE PART THAT MAKES THIS WORK
- **One file, four outputs.** The reason these products get bought is that design, tests, mocks and docs drift apart when they are four separate artefacts. Generating all four from one description removes the drift rather than managing it
- Contract tests in the API's own suite, so the description cannot quietly become fiction

SECRETS AND SAFETY
- Never store a real token in a collection file. Environment variables, with a .env.example committed and the real one ignored
- Do not point a test suite at production by default. Make that a deliberate flag with a loud name

WHAT MATTERS MOST
Schema assertions and one source file. Together they turn four tools into a pipeline that cannot disagree with itself.