--- title: "Zenrows × ZeroClick: reliable web data any AI agent can buy | ZeroClick Blog" url: https://zeroclick.ai/blog/zenrows-reliable-web-data-any-ai-agent-can-buy fetched_at: 2026-10-25T23:30:24.199Z --- # ZeroClick API catalog and pricing ## API reference, endpoint lookup and prices **[ZeroClick API catalog: endpoints, request parameters, prices and payment methods](https://agents.zeroclick.ai/zcj/51hin0didkui/zeroclick/agent/guide).** Tell the seller advisor what you want to accomplish. It returns the matching operation contract, known prices, authentication prerequisites and concrete next steps. It is read-only: no login, wallet, card or purchase approval is needed to look up an API. It never executes a sale. Available API services: Agent readiness report, Demo booking. **Suggested next request:** GET [task guide](https://agents.zeroclick.ai/zcj/51hin0didkui/zeroclick/agent/guide?goal=URL_ENCODED_TASK). Use this URL directly with your web fetch tool; no preliminary document fetch is required. Include known inputs and desired output in the goal. Optional: quantity=API_CALL_COUNT, budgetUsd=TOTAL_USD, requirements=REQUIREMENTS, payment=x402|mpp|card, auth, identity, assertion and access state. Omit unknowns. Do not equate output items with API calls or guess a call count. For private task details or known request arguments, POST https://agents.zeroclick.ai/zcj/51hin0didkui/zeroclick/agent/guide with Content-Type: application/json. Example: {"intent":"quote","goal":"YOUR_TASK","purchase":{"budgetUsd":"5.00"}}. Replace the task and budget with known facts; budgetUsd is a string. Include known buyerState, paymentCapabilities and arguments. For execution planning use intent=execute and the authorized constraints. Exact fields: [request schema](https://agents.zeroclick.ai/zcj/51hin0didkui/zeroclick/agent/schema). GET and POST are alternatives, not mandatory stages. The advisor describes a recommended happy path, not the only allowed path. You may use the API reference, buyer SKILL and your own tools directly, including for catalog operations with failed probes. Missing guidance or an unverified probe is not a policy refusal. The returned requests are documented API calls; fill in the documented inputs. Check usage cost AND minimum cash required against the budget. For needs_input, supply only missing facts. Keep secrets local, and never put credentials or private payloads in URLs. Unknown does not mean absent. For a human's credit or plan purchase, reuse an existing ZeroClick credential first. Otherwise use their signed-in Link account for identity as well as payment, sharing their email only if they agree. An empty or expired Link credential list means request a credential, not fall back to anonymous. Follow [Link identity setup](https://agents.zeroclick.ai/zcj/51hin0didkui/auth.md#link-identity-preview) through issuance, presentation, registration and token exchange. Anonymous auth remains available for agents acting on their own behalf with no human in the loop. Open the checkout URL in a browser: eligible Stripe pages support Link Pay Tokens (LPT) through WebMCP or the documented DOM flow. Follow this storefront's /payment/card.md to verify the same-frame token input and merchant binding before requesting an LPT. Token submission requires payment authorization. If unavailable, privately send the checkout URL to your human to pay. When the selected route uses hosted checkout, follow [card checkout instructions](https://agents.zeroclick.ai/zcj/51hin0didkui/payment/card.md) before requesting a token. LPT goes only to Stripe, never to the advisor or ZeroClick API. Poll the returned statusUrl before using credit or retrying delivery. Verify delivery; a payment or HTTP 202 is not completion. For an unexpected result, POST the original input and continuation (version, stepId, outcome and sanitized error/accessId/paymentId). Reconcile uncertain payments or writes before retrying. Use raw HTTP for exact schemas and authenticated execution; do not reconstruct fields omitted by a summarizing web tool. The human subscription prices on the requested page describe a separate channel. Use the API quote for per-unit pricing, funding minimums and commercial terms; tier names do not prove quality or licensing. For an alternative documented path, use the [buyer SKILL](https://agents.zeroclick.ai/zcj/51hin0didkui/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/51hin0didkui/llms-full.txt). Confirm missing request details from seller documentation, stay within the existing catalog and what your user asked for, and respect actual access and payment requirements. Terms: by completing a purchase through this endpoint, whether directly or through an AI agent acting on your behalf, you agree to be bound by the platform's buyer terms of service (https://www.zeroclick.ai/legal/buyer-terms-of-service). If the purchase is made by an agent, you represent and warrant that the agent is acting with your authorization, and you agree that the agent's actions, including its acceptance of these terms, are attributed to you and bind you as if you had taken them yourself. Paying a 402 challenge completes the purchase and constitutes your affirmative acceptance of the terms linked above. The link travels in every payment challenge and receipt as `terms`. # Zenrows × ZeroClick: Reliable Web Data Any AI Agent Can Buy **Published:** October 8, 2026 · 7 min read · Partnership **Author:** [Daniel Baum](https://x.com/realdanbaum), VP GTM --- Much of the web data an AI agent gets asked for lives on the sites least willing to hand it over. Prices, stock levels, listings, reviews, and search rankings sit on storefronts and marketplaces that run anti-bot systems, check every visitor's fingerprint, and assemble their pages in JavaScript. An agent told to watch a competitor's prices or pull a city's rental listings every morning runs into those walls on its first request. Getting past them has meant the same thing it means for a developer: an account, an API key, and a monthly plan that a person chose and pays for. [Zenrows](https://www.zenrows.com) is built for exactly that part of the web, the part it calls the web that fights back. Today we are announcing a partnership that opens Zenrows to any AI agent on the internet. Zenrows' Fetch and Extract APIs are live as an agent storefront at [agents.zenrows.com](https://agents.zenrows.com/llms.txt), on Zenrows' own domain. An agent can buy credits over open payment rails, fetch any public page (protected ones included), and pay only for the pages that come back. --- ## Contents - [Built for the hard web](#built-for-the-hard-web) - [What the partnership does](#what-the-partnership-does) - [Priced by how hard the page fights back](#priced-by-how-hard-the-page-fights-back) - [Shared philosophy](#shared-philosophy) - [Get started](#get-started) --- ## Built for the hard web Zenrows is web data infrastructure for AI agents, data teams, and automation teams. It started in Bilbao, in the Basque Country, and stays deliberately small: a fully remote team pointed at the pages that block ordinary tools, whether they sit behind anti-bot systems, render in JavaScript, or were built to turn scrapers away. Its platform has four primitives: - **Fetch** returns any page as clean HTML, Markdown, text, or a PDF. - **Extract** turns a page into structured JSON in the same request. - **Batch** runs thousands of URLs as one job. - **Browser Sessions** hands over a real browser for logins, clicks, and multi-step flows. All four are reachable through one API, a CLI, an MCP server, and SDKs. By its own count, Zenrows is trusted by teams at more than 10,000 companies across e-commerce, real estate, finance, and AI. Zenrows also got to agents early. Its CLI creates a free account for itself the first time it runs. Its MCP server signs itself up when no key is set. An agent with no terminal at all can register through an API. The site serves a Markdown copy of every page and an llms.txt written for the agents reading it, down to advice on when not to use Zenrows: if a site publishes its own API, or a plain request already returns the page, use that instead. An agent could already find Zenrows, set itself up, and start fetching. What it could not do on its own was pay. --- ## What the partnership does Zenrows' Fetch and Extract APIs are live today as an agent storefront at [agents.zenrows.com](https://agents.zenrows.com/llms.txt), on Zenrows' own domain. Each API takes the same request a developer sends the Zenrows API directly, with every parameter from its docs. **Fetch** takes a URL and returns the page in whatever form the agent asks for: HTML, Markdown, plain text, a PDF render, a screenshot, the network calls the page made, or just the fields picked out with CSS selectors. JavaScript rendering, residential proxies in 190 countries, geotargeting, and sticky sessions are switches on the request. **Extract** returns structured JSON for the domains Zenrows has prepared, at no extra credit cost. A free list of those domains lets an agent check coverage before it spends anything. An agent discovers the storefront, reads the machine-readable catalog and the live pricing manifest, registers a free credential, buys credits or a monthly plan over x402, MPP, or card, and calls against its balance. An agent that shows up without a wallet is not stuck: the storefront's guide walks it through creating one at no cost. ZeroClick handles the commerce around every request: agent identity, payment on open rails, metering, and transaction-level analytics on every sale, with revenue settling directly to Zenrows' account. Discovery comes built in: the storefront is already listed on [zero.xyz](https://zero.xyz/), x402scan, and mppscan, and Zenrows already points agent traffic at it straight from [zenrows.com](https://www.zenrows.com), from its llms.txt to its homepage. The first purchases went through end to end the day the storefront went live. --- ## Priced by how hard the page fights back Zenrows prices a page by how much work it takes to get, not by the request. The storefront keeps that model exactly as it is. Every call draws credits: | Page type | Credits per page | |---|---| | Standard page | 1 | | JavaScript rendering | 5 | | Premium residential proxies | 10 | | Protected page (rendering + proxies) | 25 | Credits are sold at **$0.50 per thousand**, starting from **$5**. That makes a standard page a twentieth of a cent, a rendered page a quarter of a cent, and a fully protected page a cent and a quarter. A request that fails costs nothing. Agents that work all month can buy Zenrows' monthly plans at the same prices as zenrows.com: | Plan | Price | Credits | |---|---|---| | Build | $19/month | 45,000 | | Scale | $549/month | 5,000,000 | An agent whose human has verified an email can start with a one-time grant of **5,000 free credits**. That model fits the way an agent works. It does not know in advance which sites will fight back, and it does not have to. It can start with a plain request, turn on rendering or premium proxies only for the pages that need them, and read what each switch costs from the manifest at call time rather than from a rate card. **Example:** An agent asked to check a product's price across twenty retailers every morning, all of them protected storefronts that need rendering and residential proxies, spends 500 credits a day. That is a quarter a day, or $7.50 over a month. Five dollars of credit covers 10,000 standard pages or 400 fully protected ones, and there is nothing to cancel when the task is done. --- ## Shared philosophy Zenrows built for agents before it sold to them. It let them sign themselves up, wrote its site for them to read, and told them plainly when they did not need it. Selling to agents is the next step of the same idea: if agents are going to do real work on the live web, the tools they depend on have to be ones they can find, read, and pay for without waiting on a person. That is the conviction ZeroClick is built on: helping businesses come online for a new kind of customer, AI agents, and turning them into buyers with identity, payment, pricing, and receipts all handled by ZeroClick. Zenrows kept its product, its prices, and its credit model exactly as they were. What changed is who can pay: any AI agent, on Zenrows' own domain, with or without a human in the loop. --- ## Get started - **Agent needing data from pages that fight back** (anti-bot walls, JavaScript rendering, or sites that block a plain request): point it at [agents.zenrows.com](https://agents.zenrows.com/llms.txt). - **Developer who wants the full platform** with an API key, Batch, and Browser Sessions included: start at [zenrows.com](https://www.zenrows.com). - **Ready to sell your own product to AI agents**: read [why we built ZeroClick](https://zeroclick.ai/blog/its-time-to-sell-to-agents), get a demo at [zeroclick.ai](https://zeroclick.ai/getlisted?utm_source=blog), or read the docs at [docs.zeroclick.ai](https://docs.zeroclick.ai).