How it works

From empty domain to working API

Give every project and scenario its own HTTPS mock domain. Define endpoints, switch between scenarios, and share ready-to-use URLs with your team.

D

Your own mock domain

Every project and scenario gets its own HTTPS mock domain with an auto-renewed certificate. Share the URL — no installs, no proxy setup.

E

Define endpoints

Map your API surface with methods, paths, status codes, and JSON responses. Paste real JSON or generate responses from a JSON Schema.

S

Build scenarios

A scenario is a named set of responses describing one state of your app — new-user payment-failed admin-user. Switch between them without redeploying anything.

C

Connect your app

Point your frontend's API base URL at the mock domain. Every teammate gets runtime URLs and environment variables for the scenario they need.

T

Watch every request

Request telemetry records what came in, which response matched, and where it came from — mock, proxy, or Mockeryn error — so failures are quick to debug.

A

Let agents build it

With Mockeryn MCP, AI coding agents can inspect your API client, create scenarios, preview a plan, and return runtime URLs to develop against.

Telemetry

See your mocks answer in real time

Every request is recorded with the matched scenario, the status code, and the source of the response.

  • request received and matched against scenario constraints
  • status code and response body returned
  • source: mock, proxy pass-through, or Mockeryn error
  • latency and headers for every hit
200 OK shop--populated-feed.mockeryn.com
GET /v1/feed
Status 200
Matched scenario populated-feed
Source mock 
{
  "items": 24,
  "scenario": "populated-feed",
  "served_by": "mock"
}