What does this actually generate from my spec?
A spec describes an API that may not be built yet. This reads the spec — OpenAPI 3.0, OpenAPI 3.1 or Swagger 2.0 — and stands up a real hosted mock for its supported endpoints in one step, each returning an example response taken from the spec or synthesised from its schema. The mock answers real HTTP requests for 24 hours, so you can develop or demo against the supported API surface before any of it exists.
Which spec versions are supported?
OpenAPI 3.0, OpenAPI 3.1 and Swagger 2.0, in JSON or YAML. The mock serves GET, POST, PUT, PATCH and DELETE operations
Where do the response bodies come from?
From the response example in the spec when there is one; otherwise a realistic body is synthesised from the response schema and its field names
Do path parameters work?
Yes. A templated path such as /users/{id} matches any value in that segment, so a real id resolves to the endpoint example
How long does the mock last?
It answers for 24 hours, then expires