Skip to main content
Set zeroDataRetention: true per call. Stophy reads the page live and keeps no copy. Billing still leaves a record, and some jobs hold results briefly so you can collect them. See Pricing for what it adds.
The answer has the usual shape, with data.metadata.cacheState set to miss because no stored copy was read. Read the content from this response. A normal scrape can be read for 24 hours with GET /v1/scrape/{id}. This one answers 404 notFound.

Where to send it

Monitors do not take it, because a monitor keeps a snapshot to compare with the next one.

What changes

  • Stored copies. None is read or made, so every read is live.
  • Results. GET /v1/scrape/{id} answers 404, and the scrape cannot be interacted with. Open the page in a session from POST /v1/browser instead.
  • Jobs. A crawl, batch or extract keeps its results for 1 hour after it finishes instead of 24. A webhook delivery for it is recorded without its payload.
  • Agent. The prompt, steps and result are held for one hour at most.
  • Logs. GET /v1/logs shows the request ID, endpoint, method, status and cost, not the content.
  • Browser sessions. No replay, no recording, and no profile, because a profile keeps cookies.
  • Interact. If the scrape’s session is already open without the flag, stop it with DELETE /v1/scrape/{id}/interact and start again.
Your app stays responsible for what it stores and logs from the answers.

Refusals

All are 400 invalidRequest. Remove the setting that needs a stored copy and send again.
  • A screenshot format, a screenshot or pdf action, or onlyCleanContent on scrape, search, extract, crawl or batches.
  • threadId on agent.
  • profile or recording on a browser session.
  • Any monitor.