Documentation

Slurry docs

Slurry hosts living simulations of third-party APIs. Each one keeps state, changes on a schedule, fires signed webhooks and fails when you tell it to.

QuickstartFrom account to first request against a living simulation in five steps.
SimulationsCollections, the behaviour plan, reset and fast-forward.
Management APICreate and control simulations from scripts and CI.
MCP serverConnect Claude Code, Claude Desktop or Cursor and let agents drive.
WebhooksPayload format, signature verification and retries.
RulesFixed responses, errors, latency, conditional matches and chaos.
Security and accessIP allow-lists, simulation keys and account keys.

Three endpoints

Everything in Slurry is reached through one of three addresses. Simulations use simulation keys (slurry_sim_); the management API and MCP server use account keys (slurry_acct_), created under Settings in the dashboard.

endpoints

https://<name>.slurry.io          # your simulation (simulation key)
https://api.slurry.io/v1          # management REST API (account key)
https://api.slurry.io/mcp         # MCP server, Streamable HTTP (account key)