Repository navigation
fix(extract): describe Extract as generally available, on any prepared domain - #37
Merged
Merged
Conversation
…and help The README on npm, the extract help text, the skills and the capability registry still described extract=auto as a "domain-gated open beta". That has not been true since the gate was removed: Extract works on any domain Zenrows has prepared, with any active key, and a domain that isn't prepared yet answers REQS007, which the CLI already falls back from to Autoparse. Say that instead, and replace "contact Zenrows support to enable this domain" in the AUTH010 and REQS007 errors with the self-serve path (POST /v1/extract/prepared-domains). Copy only; no behaviour changes. The npm page updates on the next publish (1.5.1). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rom the touched copy
…lable Extract is out of beta, so stop labelling it that way: the README commands table, the capability and skill registries (extract status is now `available`), the `extract --help` text, code comments, the docs and the skills, workflow and template that describe it. Pricing wording stays as is: extract=auto is still described as currently free. Batch keeps its beta label; it is unchanged here. See https://docs.zenrows.com/extract/introduction Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AnderRV
reviewed
Oct 13, 2026
| - **experimental** — exists but not yet promoted to a stable status. | ||
| - **beta** — open beta; usable by any key. Product-specific limits (e.g. Extract | ||
| domain coverage) are handled by adapters / API errors, not by blocking the CLI. | ||
| - **beta**: usable by any key. Product-specific limits (e.g. Batch access) |
Member
There was a problem hiding this comment.
@jonathan-zenrows do we want to use Batch as a beta example?
If we don't have any in beta and don't plan to, we might just remove the line.
Contributor
Author
AnderRV
reviewed
Oct 13, 2026
| "available-but-needs-confirmation", | ||
| // Open beta: any key can call; product-specific limits (e.g. Extract domain | ||
| // coverage, Batch 403) are handled by the adapters / API errors, not here. | ||
| // Beta: any key can call; product-specific limits (e.g. Batch 403) are |
Contributor
Author
There was a problem hiding this comment.
Same commit: the comment no longer uses Batch as an example. The beta value itself stays in the set, since the status enum still defines it.
AnderRV
approved these changes
Oct 13, 2026
AnderRV
left a comment
AnderRV
left a comment
Member
There was a problem hiding this comment.
Approved, but please check the comments
No primitive is in beta once Extract and Batch are generally available, so drop the beta entry from the status legend in docs/capabilities.md and the Batch example from the comment on the usable statuses. The beta status value itself stays in the code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When Extract knows a kind of page but none of the fields come back filled, the API answers 422 with code no_data_extracted. The request is not charged, and repeating it returns the same answer. The CLI treated every 422 as a failed fetch and suggested escalating with --js-render --premium-proxy, which reads as if the site could not be reached. It now returns that answer to the extract adapter as an empty result: one request, no Autoparse fallback, a warning that says no data was found and how to check the page rendered fully, and `noDataExtracted: true` in --json output. Under --validate it fails with EXTRACT_VALIDATION_FAILED. Other 422s keep the existing handling. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e-copy # Conflicts: # README.md # agent-plugin/skills/zenrows/SKILL.md # docs/capabilities.md # skills/zenrows/SKILL.md
…led fetch An Extract request whose fetched page was a block or error page answers 422 blocked_document (not charged). The CLI reported it as "Protected Fetch failed with HTTP 422". It now says what happened and suggests the stronger fetch that can get past it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
2 participants
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.
What
Brings the CLI's description of Extract in line with how it works today, everywhere the CLI ships it: the README (what npm shows),
zenrows extract --help, the skills (CLI and agent-plugin), the capability registry anddocs/capabilities.md.extractasavailable.403 REQS007; the CLI still falls back to Autoparse there.POST /v1/extract/prepared-domains, instead of contacting support.See https://docs.zenrows.com/extract/setup#domain-coverage.
Testing
npm run typecheck: cleannpm test: 359/359 passzenrows extract --helpshows the new default-mode lineAfter merge
Publish a new patch version so the npm page picks up the README.
Replaces #36, which closed when its branch was renamed.
🤖 Generated with Claude Code