Skip to content

docs(interact): document zero data retention sessions - #1584

Merged
micahstairs merged 2 commits into
mainfrom
claude/interact-zdr-docs
Oct 9, 2026
Merged

micahstairs merged 2 commits into
mainfrom
claude/interact-zdr-docs

Conversation

@claude

@claude claude Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Requested by Micah Stairs · Slack thread

Before: The docs said Zero Data Retention was available only for scrape and search. Nothing in the Interact or Browser pages, or in the Interact endpoint references, mentioned zeroDataRetention, though the API has accepted it on Interact since early October.

After: features/interact.mdx has a Zero Data Retention section. It covers how to enable ZDR on POST /v2/scrape/{scrapeId}/interact and POST /v2/interact, automatic ZDR when interacting with a ZDR scrape, the policy sticking to the session, the team-enablement requirement (403), the recordings/profiles restriction (400), the 409 when asking for ZDR on an existing non-ZDR session, and the url fallback when a ZDR scrape's replay context is unavailable. features/browser.mdx gets a short ZDR subsection. The endpoint references (browser-create.mdx, scrape-execute.mdx) list the new parameters and error cases, and enterprise.mdx now lists Interact among the ZDR surfaces. The pricing sections in features/interact.mdx and features/browser.mdx, and the Interact row in billing.mdx, now state the ZDR surcharge: +2 credits per browser minute, so code-only sessions bill at 4 credits/min and prompt sessions at 9, with the same one-minute minimum. A ZDR scrape still carries its own +1 credit/page surcharge.

How: The support docs are checked against the API code that shipped in firecrawl/firecrawl#4915. The gating and the 403/409 errors are in getBrowserZDR (apps/api/src/lib/browser-lifecycle.ts), the 400 for recordings/profiles is in createBrowserSession, the request fields are in controllers/v2/browser.ts and controllers/v2/scrape-browser.ts, and ZDR scrapes skip the stored replay context in services/logging/log_job.ts. Only the English source files are edited.

The pricing depends on the API change in firecrawl/firecrawl (the ZDR surcharge PR, branch claude/interact-zdr-surcharge). On main today, ZDR sessions bill at the standard 2 and 7 credits/min. Merge this after that change ships.

🤖 Generated with Claude Code

https://claude.ai/code/session_013R47uwW8MefsRuLhpzaiq2

Interact accepts zeroDataRetention on POST /v2/interact and on
POST /v2/scrape/{scrapeId}/interact (firecrawl/firecrawl#4915). Document
how to enable it, the team-enablement requirement (403), the
recordings/profiles restriction (400), the 409 on an existing non-ZDR
session, inheritance from ZDR scrapes, and the url fallback when a ZDR
scrape's replay context is unavailable.

Interact ZDR pricing is intentionally left out pending a pricing decision.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013R47uwW8MefsRuLhpzaiq2
@mintlify

mintlify Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
firecrawl 🟢 Ready View Preview Oct 9, 2026, 8:01 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

ZDR Interact sessions add 2 credits per browser minute: 4 credits/min for
code-only sessions and 9 credits/min for prompt sessions, with the same
one-minute minimum. A ZDR scrape keeps its own +1 credit/page surcharge.

Depends on the Interact ZDR surcharge change in firecrawl/firecrawl.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013R47uwW8MefsRuLhpzaiq2
@micahstairs
micahstairs marked this pull request as ready for review October 9, 2026 20:01
@micahstairs
micahstairs merged commit e6ea457 into main Oct 9, 2026
1 check passed

This branch was successfully deployed

1 active deployment
staging — 17a8367b Deployed Oct 9, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants