{{ message }}
Repository navigation
[Superseded by #1707] docs(scrape): document zero data retention for Alexandria calls - #1688
Open
mintlify[bot] wants to merge 1 commit into
Open
mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
Contributor
Author
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Documents that
alexandriascrape calls now acceptzeroDataRetention: true, and covers the errors that come with it:zero_data_retention_unsupported(400),response_not_retained(409) on anx-request-idreplay, andduplicate_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
alexandriaexecution. Now onlydomainToolsreturns 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.