--- title: "OpenWeb Ninja × ZeroClick: real-time public web data any AI agent can buy | ZeroClick Blog" url: https://zeroclick.ai/blog/openwebninja-public-web-data-any-ai-agent-can-buy fetched_at: 2026-10-26T08:47:40.983Z --- # 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/i6djhrxskd6f/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/i6djhrxskd6f/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/i6djhrxskd6f/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/i6djhrxskd6f/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/i6djhrxskd6f/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/i6djhrxskd6f/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/i6djhrxskd6f/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/i6djhrxskd6f/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`. # OpenWeb Ninja × ZeroClick: Real-Time Public Web Data Any AI Agent Can Buy **Blog** · October 22, 2026 · 8 min read · Partnership By [Daniel Baum](https://x.com/realdanbaum), VP GTM --- Most of what an AI agent gets asked to find is public, and almost none of it is easy to use. Which dentists in Austin list a phone number and an email? What does a data engineer make in Denver? Is the grill cheaper at Walmart or Home Depot this morning? What did that Zillow listing just drop to? The answers sit in search results, map listings, product pages, and job boards that were built for people to read. An agent has had two ways to get at them: fetch the page and parse it, or go the developer's route, with an account, an API key, and a monthly subscription that a person set up. [OpenWeb Ninja](https://www.openwebninja.com) has built its business turning those pages into APIs. Each API returns clean JSON from a named source, for teams that need the data but don't want to deal with web scraping. Today ZeroClick is announcing a partnership that opens those APIs to any AI agent on the internet. OpenWeb Ninja's catalog is live as an agent storefront at [agents.openwebninja.com](https://agents.openwebninja.com/llms.txt). An agent can register once, fund a balance over open payment rails, and call any of 50+ APIs for as little as $0.003 a request. --- ## The Data, Not the Scraping OpenWeb Ninja calls itself the web data and search results API stack for AI engineers, app developers, and go-to-market teams. It is based in Sunnyvale, California, and was co-founded by Tzachi Benayoun (CEO) and Adam Benayoun (CTO). The idea is simple: pick the public sources that matter and keep each one running as an API. - **Search and SERP data** from Google and Bing, including Google's AI Overviews and AI Mode - **Local business data, reviews, directions, and traffic** from Google Maps, Yelp, and Waze - **Jobs** from LinkedIn, Indeed, Glassdoor, ZipRecruiter, and Monster through JSearch, with salary data alongside - **Products, prices, and reviews** from Amazon, Walmart, eBay, Costco, Wayfair, and Home Depot - **Property listings** from Zillow and Redfin - **Stock and currency data** from Google Finance - **News, events, books, images, short videos, and app store listings** each have an API of their own Every API returns the same clean JSON. Most requests come back in one or two seconds. Every API includes a free tier for testing. By its own count, OpenWeb Ninja is used daily by Fortune 500 companies and more than 50,000 developers. Customers rate it 4.8 out of 5 on G2 and Trustpilot. OpenWeb Ninja also got to agents early. Its APIs ship as tools for Claude, Cursor, and other coding agents. There is an agent skill that turns a plain-language request into the right API call. It already runs a lane where an agent can pay for a single call in USDC with nothing but a wallet. An agent could already find OpenWeb Ninja, pick an API, and pay for one request. What it could not do was everything around that request: hold a credential it could reuse, keep a balance instead of paying call by call, let its human pay by card, start on a free allowance, or be found by agents that were not already looking. --- ## What the Partnership Does OpenWeb Ninja's 50+ APIs, more than 200 endpoints in all, are live today as an agent storefront at [agents.openwebninja.com](https://agents.openwebninja.com/llms.txt). Each endpoint takes the same request a developer sends OpenWeb Ninja's API directly, with every parameter from its docs. An agent discovers the storefront, reads the machine-readable catalog and the live pricing manifest, registers a free credential, buys credits over x402, MPP, or card, and calls against its balance. The agent does not have to work out which API it needs. The storefront's seller advisor takes a goal in plain language, for example "Search Google Maps for dentists in Austin TX and get their phone numbers and emails", and returns: - the endpoint to call (Local Business Data search in this case) - the request to send - what it will cost - the next step Nothing is bought until the agent decides to proceed. An agent that arrives without a wallet is not stuck. The storefront's guide walks it through creating one at no cost, or hands its human a checkout link. ZeroClick handles the commerce around every request: agent identity, payment on open rails, metering, and transaction-level analytics on every sale. Revenue settles directly to OpenWeb Ninja's account. The credential an agent registers here works at every ZeroClick storefront. Claiming it with a verified email keeps what the agent buys. Discovery comes built in. The storefront is already listed on [zero.xyz](https://zero.xyz/), with x402scan, mppscan, and more to follow. OpenWeb Ninja already points agent traffic at the storefront from [openwebninja.com](https://www.openwebninja.com), from its llms.txt to its homepage. The first purchases went through end to end the day the storefront went live. --- ## Three Tenths of a Cent a Request OpenWeb Ninja prices every API by the request. The storefront keeps that model exactly as it is. | API type | Price per request | |---|---| | Most APIs | $0.003 | | ChatGPT, Copilot, Gemini, Google AI Mode, EV charging station finder | $0.005 | Credits are prepaid from $0.50. Fifty cents covers more than 160 requests. An agent whose human has claimed its credential with a verified email starts with 50 free requests. That shape fits the way an agent works. Consider some real examples: - **Price comparison across 6 retailers** (Amazon, Walmart, eBay, Costco, Wayfair, Home Depot): 6 requests, under $0.02 - **Job market monitoring** (20 JSearch queries every morning): $0.06 a day, or $1.80 a month - **Sales prospect list** (100 local business lookups + 100 website contact scrapes): $0.60 The agent reads every price from the manifest at call time, not from a rate card. --- ## Shared Philosophy OpenWeb Ninja's promise to developers has always been simple: clean, reliable data, with none of the scraping to build or maintain. It has kept 50+ sources fast, stable, and in the same shape so that a team could ship on them without running a scraper of its own. Then it noticed that its next customer was not a team at all. It packaged its APIs as tools for agents, published an MCP server and an agent skill, and let agents pay as part of the request. Selling to AI agents is the next step of the same idea: if agents are going to answer real questions from the live web, the data they depend on has to be something 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. OpenWeb Ninja kept its product, its prices, and its per-request model exactly as they were. What changed is who can pay: any AI agent, on OpenWeb Ninja's own domain, with or without a human in the loop. For existing OpenWeb Ninja customers, nothing changes. API keys, plans, and the developer platform at [openwebninja.com](https://www.openwebninja.com) work as they always have. The storefront is a new way in, built for agents. --- ## Get Started If your agent needs real-time public data, whether that is search results, local business listings, job postings, product prices, or property data, point it at **[agents.openwebninja.com](https://agents.openwebninja.com/llms.txt)**. OpenWeb Ninja has its own write-up of the storefront, with a worked advisor call, at [openwebninja.com/blog/zeroclick-agent-storefront](https://www.openwebninja.com/blog/zeroclick-agent-storefront). If you are a developer who wants the full platform with an API key, start at **[openwebninja.com](https://www.openwebninja.com)**. If you are ready to sell your own product to AI 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)**.