[Superseded by #1707] docs(scrape): document zero data retention for Alexandria calls by mintlify[bot] · Pull Request #1688 · firecrawl/firecrawl-docs · GitHub
Skip to content

[Superseded by #1707] docs(scrape): document zero data retention for Alexandria calls - #1688

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
autopilot/4d1f83f7
Open

mintlify[bot] wants to merge 1 commit into
mainfrom
autopilot/4d1f83f7

Conversation

@mintlify

@mintlify mintlify Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Documents that alexandria scrape calls now accept zeroDataRetention: true, and covers the errors that come with it: zero_data_retention_unsupported (400), response_not_retained (409) on an x-request-id replay, and duplicate_request (409) when the ZDR setting differs.

It also removes a false line from the API reference. The reference said teams with zero data retention get a 403 on alexandria execution. Now only domainTools returns that 403.

Based on Alexandria: zero data retention for provider tools, which forwards ZDR to Exchange and stops refusing forced-ZDR teams outright.

Needs a human look: the per-provider 400 depends on firecrawl/exchange#936, which was not merged when the source PR landed. If that change isn't live yet, hold this PR until it ships. The extra +1 credit Exchange plans to charge is left out until it is confirmed.

@mintlify

mintlify Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor Author

@mintlify mintlify Bot changed the title docs(scrape): document zero data retention for Alexandria calls [Superseded by #1707] docs(scrape): document zero data retention for Alexandria calls Oct 23, 2026
@mintlify

mintlify Bot commented Oct 23, 2026

Copy link
Copy Markdown
Contributor Author

This branch was successfully deployed

1 active deployment
staging — 939ef1b6 Deployed Oct 21, 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.

1 participant