Every frontend build has the same stall: the UI is ready, the API isn't, and the team is stuck pretending with hardcoded stubs that drift from the real contract. The waiting is expensive and the stubs become lies.
I built MockDeck for the moment someone says "we could just mock it" and nobody wants to write the mock by hand.
30-second takeaway
- Mocking an API by hand is the tax nobody budgets for, so it never gets done well.
- One-line description → OpenAPI 3, Postman, or raw routes, with realistic sample responses.
- The frontend ships while the backend is still a spec.
The stub that becomes a lie
Hand-written mocks start honest and rot fast. The real API changes, the mock doesn't, and now the UI passes against a contract that no longer exists. The team discovers the gap at integration, which is the most expensive place to find it.
Generating the mock from a description means it's cheap to regenerate whenever the spec moves — and the frontend builds against something close to real.
What the tool does
Describe an endpoint and get a mock API spec — OpenAPI 3, Postman, or raw routes — with realistic sample responses so the frontend team can build before the backend is ready.
MockDeck runs in the browser, no account, no key.
FAQ
What is MockDeck?
A tool that generates a mock API from a one-line endpoint description, in OpenAPI, Postman, or raw route form. No account, no key.
Does it call my real backend?
No. It generates a mock from your description so the frontend can build against it.
Will the sample responses match my real data?
They're realistic placeholders from the description. You tune them to your schema — the point is cheap iteration, not a data clone.
Author's Process
This product was built with AI coding tools. The useful part was keeping it to one description in, multiple mock formats out.
Top comments (0)