Everything Recording gives you
- 01
Record through the sandbox
Each call goes to the upstream and back; the app gets the real answer and Stuntman keeps the pair.
- 02
Secrets never kept
Auth headers, keys and password fields become secret://; e-mails, card numbers and CPFs become synthetic ones.
- 03
Every call or only new
mode=unknown sends only calls no route answers, to finish a plugin that is almost done.
- 04
Stops by itself
After stop_after (default 30 min) or max calls (default 500). Pause and resume at any time.
- 05
Review before writing
Calls grouped into routes like /v2/shipments/{id}, one answer per status, the most frequent success as default.
- 06
Ids and dates as templates
Changing ids become random_id(), dates now(), and values the app sent are echoed back.
- 07
Rules suggested
A field only the error calls lacked becomes a rule: when !body.destination.postal_code, answer invalid.
- 08
Binary answers as files
A PDF label or an image up to 5 MB is kept next to the plugin and sent as it came.
The screens
Each number is a control or a reading on the real screen. Everything you can click there, your agent can do with a tool.
Start a recording

One of the ways to start a service, next to a spec or the catalog.
The provider's sandbox: Stuntman sends each call there and keeps a copy.
Record from zero, or let the routes answer and send only the rest.
Credentials go to secret://; card numbers, CPFs and e-mails are replaced with synthetic ones.
The key reaches the provider as the app sent it and may use its quota.
- Record the real provider
One of the ways to start a service, next to a spec or the catalog.
- The upstream
The provider's sandbox: Stuntman sends each call there and keeps a copy.
- Every call or only unknown
Record from zero, or let the routes answer and send only the rest.
- Never kept
Credentials go to secret://; card numbers, CPFs and e-mails are replaced with synthetic ones.
- Sandbox keys only
The key reaches the provider as the app sent it and may use its quota.
While it records

The recording stops by itself; Stop and review ends it now.
Pause sends nothing more to the sandbox; calls then get the routes' answers or 404.
Binary answers up to 5 MB are saved next to the plugin.
A timeout gives the app a 502 and is left out of the review.
authorization stored as secret://globex-token, never the real value.
- Time left
The recording stops by itself; Stop and review ends it now.
- Calls kept, secrets masked
Pause sends nothing more to the sandbox; calls then get the routes' answers or 404.
- A PDF kept as a file
Binary answers up to 5 MB are saved next to the plugin.
- No answer from the sandbox
A timeout gives the app a 502 and is left out of the review.
- What was kept
authorization stored as secret://globex-token, never the real value.
The review becomes a plugin

Uncheck what the plugin should not have, such as a health check.
Ids in paths became {id}; split them back if they are different routes.
Writes routes and answers; Record more adds to the same recording.
Ids and dates became templates; fields equal to the request echo it.
Tells the invalid answer apart from created by the field its calls lacked.
- Routes found
Uncheck what the plugin should not have, such as a health check.
- How paths were grouped
Ids in paths became {id}; split them back if they are different routes.
- Create the plugin
Writes routes and answers; Record more adds to the same recording.
- Default answer as a template
Ids and dates became templates; fields equal to the request echo it.
- Rule suggested
Tells the invalid answer apart from created by the field its calls lacked.
Break it on purpose
The failures you need to test, exactly when you ask: from the screen or by a tool call, each one shown on the timeline with who caused it.
A recorded errorThe provider's own 422 or 404, on the next calls
force_answer invalid | not_foundAnswers no rule reachesA recorded answer kept without a rule, given only on demand
force_answerThe timeout the sandbox gaveThe upstream that never answered, now on cue
force_answer timeoutNetwork and server failuresReset, empty reply, 500, 503 or an HTML page
force_answerSlow providerLatency on every answer of the recorded service
set_service latencyNo routeWhile paused or after the limit, unknown calls get 404 no route
pause_recording, list_unmatched
Why not the real sandbox
Sandbox needed once
After make_plugin the provider is no longer called; tests run offline and in CI.
Real shapes, no secrets
Answers are the provider's own, with credentials and personal data masked before saving.
Failures the sandbox hides
The recorded plugin takes force_answer, latency and expired tokens like any other.
A plugin you can read
Routes, answers and rules in plain YAML, edited in the route editor.
Your AI agent drives it
Claude Code, Codex or any MCP client connects to /mcp (or calls /api over plain HTTP), sets the stand-in up, breaks it on cue and reads what your app did.
Record the shipping sandbox while our integration tests run, then turn it into a plugin.
MCP tools
start_recordingSends the service's calls to the sandbox and keeps each pairrecording_statusState, calls kept, time left; review=true shows the reviewpause_recordingPauses, or resumes with resume=truestop_recordingStops and returns the reviewmake_pluginWrites the plugin from the reviewget_pluginThe plugin YAML it wrotelist_api_callsRecorded calls, newest firstforce_answerGives any recorded answer on the next calls
The same over HTTP
- POST
/api/plugins/{service}/recording - GET
/api/plugins/{service}/recording - POST
/api/plugins/{service}/recording/pause - DELETE
/api/plugins/{service}/recording - POST
/api/plugins/{service}/recording/plugin
- HTTP only: no WebSockets or server-sent events. One recording per service; the provider has 30 s to answer.
- State is not inferred: add keep and lookup by hand when a read must return what was created.