Plain HTTP over one facade.
Drive Mock Machines from any HTTP client over the REST API. It exposes scenarios and experiments as resources, so any client can browse a deployed scenario, run an experiment, and read back the results — a thin HTTP adapter over the same Lab → Workbench → Scenario → Experiment facade as the MCP server, holding no engine logic of its own.
The REST API is a thin HTTP adapter over the Mock Machines facade. It exposes scenarios and experiments as resources, so any HTTP client can browse a deployed scenario, run an experiment, and read back the results.
It is a sibling of the MCP server — both drive the same Lab → Workbench → Scenario → Experiment facade, and neither holds engine logic of its own.
Live and hosted — no local build or server to run. Every endpoint hangs off this base.
# Base URL — liveness probe at /health
https://api.mockmachines.dev The API is open for reading the curated preset scenarios anonymously — no token required. Creating, running, and deploying scenarios needs a bearer token, which scopes the work to your own private workbench. The MCP connector is the sibling adapter, and the read-only studio is a browser UI over this same API.