---
title: "Keenable × ZeroClick: independent web search any AI agent can buy | ZeroClick Blog"
url: https://zeroclick.ai/blog/keenable-independent-web-search-any-ai-agent-can-buy
fetched_at: 2026-10-27T14:04:43.436Z
---

# 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/ta38umcj0h62/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/ta38umcj0h62/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/ta38umcj0h62/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/ta38umcj0h62/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/ta38umcj0h62/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/ta38umcj0h62/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/ta38umcj0h62/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/ta38umcj0h62/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`.

# Keenable × ZeroClick: Independent Web Search Any AI Agent Can Buy

**Lindsey Pozzuto**, Sr. Director, GTM · October 27, 2026 · Partnership

Every AI agent that answers from the live web depends on a search index, and almost no one who builds agents owns one. The agent sends its search tool a question, gets back ten links and a snippet each, and builds its answer from whatever that index chose to show it. The index was built, in most cases, to rank pages for people, and the agent's question is the last thing it was designed around. [Keenable](https://keenable.ai) is building the other kind: independent web search infrastructure for AI, with its own crawler, its own index of more than 100 billion documents, and its own ranking — an index that, in Keenable's words, gets better the more agents use it.

This partnership lets any AI agent on the internet buy into that index. Keenable's web search infrastructure is live as an agent storefront at [zeroclick.keenable.ai](https://zeroclick.keenable.ai/llms.txt), on Keenable's own domain. An agent can register once, fund a balance over open payment rails, and search or read a page for four tenths of a cent per request.

---

## An Index Built to Be Searched by Agents

Keenable came out of stealth in August with $26 million in seed funding led by Accel, with Conviction and angel investors alongside. The founding team has built web-scale search before. Co-founder and CEO Andrey Styskin ran search and ads at Yandex, then led web infrastructure at Amazon's AGI group. Co-founder and chief scientist Matthias Petri was a principal applied scientist at Amazon AGI, where he built the web grounding service behind Alexa.

By Keenable's own account, its index covers more than 100 billion documents, answers in under 250 milliseconds at the 95th percentile from US East, and is already in production at several AI labs and inference providers.

An agent gets two calls:

- **Web Search** takes a query and returns ranked results with a title, a URL, a snippet, and the dates each page was published and indexed. It can be restricted to a site, windowed by publish or index date, or run against the index as it stood at a point in time.
- **Page Fetch** takes a URL and returns the page as clean markdown with its title, author, and publish date, from Keenable's indexed copy or live from the source. An optional extraction prompt returns only the answer to an instruction instead of the whole page.

Around those two calls, Keenable has built the surface an agent builder expects: an MCP server, a CLI, keyless public endpoints for trying it, and published integrations for LangChain, LlamaIndex, OpenRouter, Vercel's AI SDK, Claude, ChatGPT, n8n, and more than a dozen others.

Its newest product, **Keenable SELECT**, treats a slice of the web as a table. A web query language pulls thousands of pages, extracts the fields it needs, and computes the answer over the rows, with each row naming the page it came from.

Keenable also got to agents as customers early. It already runs a lane where an agent can pay for a single request in USDC with nothing but a wallet, and its public endpoints answer without a key at all. An agent could already find Keenable, call it, and pay for one search. What it could not do was everything around that search: hold a credential it could reuse, keep a balance at Keenable's credit rate instead of paying a premium call by call, let its human pay by card, or be found by agents that were not already looking.

---

## What the Partnership Does

Keenable's web search infrastructure is live today as an agent storefront at [zeroclick.keenable.ai](https://zeroclick.keenable.ai/llms.txt), on Keenable's own domain. Each call takes the same request a developer sends Keenable's API directly, with every parameter from its docs.

An agent can:

1. Discover the storefront and read the machine-readable catalog and the live pricing manifest.
2. Register a free credential.
3. Buy credits over x402, MPP, or card.
4. Call against its balance at fifty requests a second with no hourly cap.

The storefront's seller advisor takes a goal in plain language — for example, everything a given company has published about its pricing in the last year — and returns the call to make, the request to send, what it will cost, and the next step, before anything is bought. 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, with revenue settling directly to Keenable'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 and mppscan to follow. Keenable already points agent traffic at the storefront from [keenable.ai](https://keenable.ai): its pricing page tells agents that Keenable sells to them, and its [developer docs](https://docs.keenable.ai/pay-per-request) walk through buying credit there. The first purchases went through end to end before this post was written.

---

## Four Tenths of a Cent a Request

Keenable prices by the request: $4.00 per 1,000 for developers who sign up. The storefront gives an agent that same rate without an account.

- A web search: $0.004
- A page fetch: $0.004
- Every call bills as one request, whatever it returns. A search that returns 50 results costs the same as one that returns 5.
- A request that fails costs nothing.
- Credits are prepaid from $0.50. Fifty cents covers 125 requests.

That shape fits the way an agent actually researches. Some examples:

- **One careful research task** — one search to find candidates, five fetches to read them, one search to check recent publications — is 7 requests, under $0.03.
- **Daily topic monitoring** — 20 searches every morning restricted to relevant sites — costs $0.08 per day, or $2.40 per month.
- **A comparison table built from 200 pages** costs $0.80.

The agent reads the price from the manifest at call time, not from a rate card. There is nothing to cancel when the task is done.

---

## Shared Philosophy

Keenable's founding bet is that search built for people is not enough for agents, and that the fix is search infrastructure of its own — an index and new retrieval primitives built for AI, rather than a better wrapper around someone else's. "The bottleneck is not only intelligence, it is also access," its team wrote when it introduced SELECT, and access is what Keenable has spent its first year building.

Selling to AI agents is the next step of the same idea: if agents are going to be the ones doing the searching, the index 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. Keenable kept its product, its prices, and its per-request model exactly as they were. What changed is who can pay: any AI agent, on Keenable's own domain, with or without a human in the loop.

---

## Get Started

- **Agent looking to search the web or read a page:** point it at [zeroclick.keenable.ai](https://zeroclick.keenable.ai/llms.txt).
- **Developer who wants the full platform** with an API key, the MCP server, and 100,000 free requests a month: start at [keenable.ai](https://keenable.ai).
- **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).
