stuntman / providers / recording

Recording

No spec and no plugin? Record the provider's sandbox through Stuntman and it writes the plugin for you.

Stands in for

  • Any HTTP provider with a sandbox
  • Undocumented partner APIs
  • Unfinished plugins (record only unknown calls)

Everything Recording gives you

  1. 01

    Record through the sandbox

    Each call goes to the upstream and back; the app gets the real answer and Stuntman keeps the pair.

  2. 02

    Secrets never kept

    Auth headers, keys and password fields become secret://; e-mails, card numbers and CPFs become synthetic ones.

  3. 03

    Every call or only new

    mode=unknown sends only calls no route answers, to finish a plugin that is almost done.

  4. 04

    Stops by itself

    After stop_after (default 30 min) or max calls (default 500). Pause and resume at any time.

  5. 05

    Review before writing

    Calls grouped into routes like /v2/shipments/{id}, one answer per status, the most frequent success as default.

  6. 06

    Ids and dates as templates

    Changing ids become random_id(), dates now(), and values the app sent are echoed back.

  7. 07

    Rules suggested

    A field only the error calls lacked becomes a rule: when !body.destination.postal_code, answer invalid.

  8. 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

Start a recording: the Recording screen in Stuntman
1Record the real provider

One of the ways to start a service, next to a spec or the catalog.

1 of 5
2The upstream

The provider's sandbox: Stuntman sends each call there and keeps a copy.

2 of 5
3Every call or only unknown

Record from zero, or let the routes answer and send only the rest.

3 of 5
4Never kept

Credentials go to secret://; card numbers, CPFs and e-mails are replaced with synthetic ones.

4 of 5
5Sandbox keys only

The key reaches the provider as the app sent it and may use its quota.

5 of 5
  1. Record the real provider

    One of the ways to start a service, next to a spec or the catalog.

  2. The upstream

    The provider's sandbox: Stuntman sends each call there and keeps a copy.

  3. Every call or only unknown

    Record from zero, or let the routes answer and send only the rest.

  4. Never kept

    Credentials go to secret://; card numbers, CPFs and e-mails are replaced with synthetic ones.

  5. Sandbox keys only

    The key reaches the provider as the app sent it and may use its quota.

While it records

While it records: the Recording screen in Stuntman
1Time left

The recording stops by itself; Stop and review ends it now.

1 of 5
2Calls kept, secrets masked

Pause sends nothing more to the sandbox; calls then get the routes' answers or 404.

2 of 5
3A PDF kept as a file

Binary answers up to 5 MB are saved next to the plugin.

3 of 5
4No answer from the sandbox

A timeout gives the app a 502 and is left out of the review.

4 of 5
5What was kept

authorization stored as secret://globex-token, never the real value.

5 of 5
  1. Time left

    The recording stops by itself; Stop and review ends it now.

  2. Calls kept, secrets masked

    Pause sends nothing more to the sandbox; calls then get the routes' answers or 404.

  3. A PDF kept as a file

    Binary answers up to 5 MB are saved next to the plugin.

  4. No answer from the sandbox

    A timeout gives the app a 502 and is left out of the review.

  5. What was kept

    authorization stored as secret://globex-token, never the real value.

The review becomes a plugin

The review becomes a plugin: the Recording screen in Stuntman
1Routes found

Uncheck what the plugin should not have, such as a health check.

1 of 5
2How paths were grouped

Ids in paths became {id}; split them back if they are different routes.

2 of 5
3Create the plugin

Writes routes and answers; Record more adds to the same recording.

3 of 5
4Default answer as a template

Ids and dates became templates; fields equal to the request echo it.

4 of 5
5Rule suggested

Tells the invalid answer apart from created by the field its calls lacked.

5 of 5
  1. Routes found

    Uncheck what the plugin should not have, such as a health check.

  2. How paths were grouped

    Ids in paths became {id}; split them back if they are different routes.

  3. Create the plugin

    Writes routes and answers; Record more adds to the same recording.

  4. Default answer as a template

    Ids and dates became templates; fields equal to the request echo it.

  5. 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 error

    The provider's own 422 or 404, on the next calls

    force_answer invalid | not_found
  • Answers no rule reaches

    A recorded answer kept without a rule, given only on demand

    force_answer
  • The timeout the sandbox gave

    The upstream that never answered, now on cue

    force_answer timeout
  • Network and server failures

    Reset, empty reply, 500, 503 or an HTML page

    force_answer
  • Slow provider

    Latency on every answer of the recorded service

    set_service latency
  • No route

    While paused or after the limit, unknown calls get 404 no route

    pause_recording, list_unmatched

Why not the real sandbox

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.

you

Record the shipping sandbox while our integration tests run, then turn it into a plugin.

start_recording{"service": "globex-shipping", "upstream": "https://sandbox.shipping.globex.example", "stop_after": "30m"}
→ ok recording; point the app at http://localhost:8028/globex-shipping
stop_recording{"service": "globex-shipping"}
→ ok 3 routes, 5 answers, 1 rule suggested
make_plugin{"service": "globex-shipping"}

MCP tools

  • start_recordingSends the service's calls to the sandbox and keeps each pair
  • recording_statusState, calls kept, time left; review=true shows the review
  • pause_recordingPauses, or resumes with resume=true
  • stop_recordingStops and returns the review
  • make_pluginWrites the plugin from the review
  • get_pluginThe plugin YAML it wrote
  • list_api_callsRecorded calls, newest first
  • force_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