--- title: "BlitzAPI × ZeroClick: GTM data any agent can buy | ZeroClick Blog" url: https://zeroclick.ai/blog/blitzapi-gtm-data-any-agent-can-buy fetched_at: 2026-10-25T20:21:53.586Z --- # 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/z84xsqbn1caj/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/z84xsqbn1caj/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/z84xsqbn1caj/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/z84xsqbn1caj/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/z84xsqbn1caj/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/z84xsqbn1caj/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/z84xsqbn1caj/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/z84xsqbn1caj/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`. # BlitzAPI × ZeroClick: GTM Data Any Agent Can Buy **Lindsey Pozzuto** · Sr. Director, GTM · October 15, 2026 · Partnership --- - [The GTM data layer](#the-gtm-data-layer) - [What the partnership does](#what-the-partnership-does) - [A tenth of a cent a result](#a-tenth-of-a-cent-a-result) - [Shared philosophy](#shared-philosophy) - [Get started](#get-started) --- Ask an agent to find the right buyer at a target account and it has to do what every growth engineer does: define the market, find the person, and prove the email is real before anything gets sent. The data behind that work has been sold the way software is sold to people: pick a monthly plan, create an API key, wire it into a stack. [BlitzAPI](https://blitz-api.ai) built its data engine for the people who assemble those stacks — GTM builders who want companies, people, verified emails, and hiring signals as blocks they can combine however they like. Today we are announcing a partnership that puts those blocks within reach of any AI agent on the internet: BlitzAPI is live as an Agent Storefront at [agents.blitz-api.ai](https://agents.blitz-api.ai/llms.txt), on BlitzAPI's own domain, where an agent can buy fifty cents of credit with a card and pay a tenth of a cent for each result that comes back. ## The GTM data layer BlitzAPI is the API-first data engine for GTM builders. Instead of another all-in-one tool, it gives teams the blocks to build their own systems: company search, people search, enrichment, verified work emails, phone numbers, job postings, and identity resolution, all behind one API. The infrastructure underneath holds more than a billion records: - 550M+ professional profiles - 65M+ companies - 100M+ job postings - 65M+ verified work emails - 45M+ US phone numbers Its standard for an email is strict. Every address is proven against live mail servers and re-tested at least every 30 days. An address that cannot be proven comes back Not Found instead of a guess. BlitzAPI was also built for a world where software does the building. BlitzAPI ships an MCP server, agent Skills, Python and TypeScript SDKs, and integrations for Clay, n8n, and Make. The company wrote the reason into its manifesto: "Agents explore, retry, make mistakes and iterate." A data product that punishes iteration does not fit how agents work, so BlitzAPI built for coverage and throughput, and for letting humans and AI, in its own words, "try an idea, change it, and run the second idea too." It is built in Paris by a small team with a simple view of go-to-market: the best systems are not bought, they are built. ## What the partnership does BlitzAPI is live today as an agent storefront at [agents.blitz-api.ai](https://agents.blitz-api.ai/llms.txt), on BlitzAPI's own domain. Five services cover the catalog: Company Search, People Search, Job Search, Company Enrichment, and People Enrichment — eighteen endpoints in all. Each one is the same request a developer would send BlitzAPI's API directly. An agent discovers the storefront, reads the machine-readable catalog and the live pricing manifest, registers a free credential, and loads prepaid credit by card from fifty cents. It then draws down one result at a time: no BlitzAPI account, no API key to request, no contract. The storefront's seller advisor also takes a goal in plain language — the best-placed decision maker at each of twenty target accounts, for example — and returns the endpoint to call, the request to send, and what it will cost, before anything is bought. BlitzAPI takes cards only, no stablecoin wallets. An agent with a Link wallet can pay the Stripe checkout itself. An agent without one hands the checkout link to its human to approve. ZeroClick handles the commerce around every request: agent identity, card payment through Stripe, metering, and transaction-level analytics on every sale, with every charge created directly on BlitzAPI's Stripe account. Discovery comes built in: the storefront is listed on [zero.xyz](https://zero.xyz/), and BlitzAPI already points agent traffic at it from blitz-api.ai, from its llms.txt to its homepage. The first paid calls have already gone through end to end. ## A tenth of a cent a result On the storefront, every result costs a tenth of a cent, whatever kind of result it is: - A person returned by a search - A company that matches an ideal customer profile - A live job posting - A full profile for a LinkedIn URL - A company resolved from a domain - A verified work email All cost $0.001 each — a dollar per thousand. The meter counts what comes back, not what was asked. A search that returns forty people costs four cents. A lookup that comes back Not Found costs nothing. B2B data has usually been packaged for teams: a plan sized for a quarter, credits bought ahead of need, a seat for everyone who might log in. An agent does not buy that way. It has a task open right now, it needs exactly as many results as the task takes, and because prices live in the manifest rather than a rate card, it reads the current price at call time and decides for itself whether the next request is worth it. Run the numbers on a real errand. An agent asked to open conversations at twenty target accounts might run a waterfall search at each one to find the best-placed decision maker, then pull a verified work email for every person it found: twenty results and twenty emails, four cents of data, spent in seconds. The smallest purchase, fifty cents, covers that errand twelve times over. There is nothing to cancel afterward and no bundle to finish. And when the errand turns into a system that runs all day, the monthly plans BlitzAPI sells to teams — from $99 a month with an API key — are a step away at [blitz-api.ai](https://blitz-api.ai). ## Shared philosophy BlitzAPI's conviction fits on one line: we build the blocks, you decide what GTM looks like. It was written for growth engineers, and it reads just as well for agents. An agent assembling a prospect list is a builder too: it combines a company search, a people search, and an email lookup into a workflow nobody designed in advance, and it needs each block to be reachable, priced, and payable on its own. 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. The blocks were already there. What BlitzAPI added is a way for agents to reach them: on its own domain, in a form they can read, priced by the result, and payable with or without a human in the loop. ## Get started If your agent needs GTM data — company and people search, verified work emails, hiring signals — point it at **[agents.blitz-api.ai](https://agents.blitz-api.ai/llms.txt)**. If you are a GTM engineer or a revenue team that wants the same API with a key, start at **[blitz-api.ai](https://blitz-api.ai)**. 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)**. For the full picture from BlitzAPI's side, including a cost simulator that shows when pay-as-you-go beats a plan, read their guide: [How AI agents find, buy, and use B2B data](https://www.blitz-api.ai/guides/ai-agents).