MockBase
Free Mock API Server with a Live Inspector
MockBase is a hosted mock API server that gives you a real, live HTTPS endpoint before your backend even exists — no signup required to try it. Point your frontend, mobile app, or test suite at a MockBase URL and it answers exactly how you configure it: conditional responses, stateful CRUD, deliberate failures, and a live inspector showing every request as it arrives. It supports REST, GraphQL, and SOAP, and every save is versioned so a bad edit is always one click from undone.
Features
Conditional matching — route on query params, headers, a JSON body path, a GraphQL operation name, or a SOAP envelope element, with priority ordering
Dynamic templating — sandboxed Jinja2 to echo the request, mint a UUID, or stamp a timestamp
Stateful CRUD — a POST is actually there when you GET it, Redis-backed, no code
Chaos injection — fail requests on purpose: slow timeouts, truncated bodies, empty responses, or a dropped connection
Rate limit simulation — deterministic 429s after N requests in a window
Live request inspector — every call streams over WebSocket, copyable as cURL, fetch, axios, and more
OpenAPI import/export — scaffold routes from a spec or regenerate one from a mock
Mock as code — a personal API key drives a CLI and an MCP server for CI/AI-agent workflows
Use Cases
Building the frontend while the backend team is still designing the API
Testing retry logic, timeouts, and error states that a happy-path backend never triggers
Writing integration tests against a stable, versioned endpoint instead of a flaky shared dev server
Demoing a product to stakeholders before any real data exists
Reproducing a third-party API's behavior for local development, without hitting their rate limits
Giving an AI agent or CI pipeline a mock it can create, edit, and inspect on its own via the CLI or MCP server
Comments
Hey! Maker here. I built MockBase because I kept hitting the same wall on every project: the frontend is ready to go, but the backend isn't — and "just wait" or "hardcode some JSON" both get old fast, especially once you need to test what happens when the real API times out, rate-limits you, or your app is expected to survive a request in a weird order. So instead of another static mock tool, I wanted something that behaves like a real API would: different responses depending on what you send it, state that actually persists between calls, and the ability to break it on purpose — a slow timeout, a truncated response, a dropped connection — since those are the paths that never get tested until they happen in production. It's still very much a living project, so if you hit something that doesn't work the way you'd expect, or there's a use case I haven't thought of, I'd genuinely like to hear about it here.
Premium Products
Sponsors
Buy
Comments
Hey! Maker here. I built MockBase because I kept hitting the same wall on every project: the frontend is ready to go, but the backend isn't — and "just wait" or "hardcode some JSON" both get old fast, especially once you need to test what happens when the real API times out, rate-limits you, or your app is expected to survive a request in a weird order. So instead of another static mock tool, I wanted something that behaves like a real API would: different responses depending on what you send it, state that actually persists between calls, and the ability to break it on purpose — a slow timeout, a truncated response, a dropped connection — since those are the paths that never get tested until they happen in production. It's still very much a living project, so if you hit something that doesn't work the way you'd expect, or there's a use case I haven't thought of, I'd genuinely like to hear about it here.
Premium Products
New to Fazier?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2025. All Rights Reserved