# How to use BlitzAPI with your AI agent

Get more done with your agent · How-to · Published 2026-10-22. Canonical page: https://zeroclick.ai/resources/how-to-use-blitzapi-with-your-ai-agent

BlitzAPI gives your AI agent B2B data on demand: account lists, decision makers, job postings, company profiles and verified work emails. Each result returned costs $0.001, and a call that finds nothing costs nothing. BlitzAPI sells through ZeroClick. Your agent registers a free credential at the [BlitzAPI storefront](https://agents.blitz-api.ai) and buys Credits once by card. Credits start from $0.50, and a card purchase starts at $0.60. Your agent then calls the API and pays for each result out of that balance.

## Key takeaways

- Register a free agent credential, buy the Credits plan with `POST /plans/{planId}/purchase`, and send every API call to `https://agents.blitz-api.ai` with your bearer token.
- Budget $1 per 1,000 results. Searches and lookups that come back empty draw nothing.
- BlitzAPI takes card payments only: a person pays a hosted checkout, or a browser agent pays it with a Link Pay Token.
- Claim the credential to a real email address soon after buying, because an anonymous credential that nobody claims lapses within days and takes its Credits with it.

## What BlitzAPI is

BlitzAPI is a B2B data API for go-to-market builders. It covers more than 550 million professional profiles, 65 million companies, 65 million verified work emails and 100 million job postings, behind one API. Every month BlitzAPI tests itself against other providers on the same real LinkedIn profiles and publishes the full results. Its work emails are checked against live mail servers before delivery and checked again at least every 30 days.

That makes it a good fit for the work agents are handed. A sales, recruiting or research agent usually needs one answer quickly: who fits this profile, which accounts are hiring, what is this contact's work email. BlitzAPI charges only for what it finds, so the agent can query broadly, accept misses and keep its spend tied to results.

An agent storefront is the machine-readable version of a business. At one URL, an agent reads what is for sale, the live prices and the exact payment steps, then buys without a person filling in forms. BlitzAPI's storefront is a transparent proxy in front of its own API. It handles identity and payment, then forwards each call. For how storefronts work, see [What is an agent storefront?](https://zeroclick.ai/resources/what-is-an-agent-storefront)

## What agents use BlitzAPI for

BlitzAPI sells five services. Each one matches jobs an agent is commonly given.

| Job your agent is given | Service | What comes back |
|---|---|---|
| Build a list of target accounts by industry, headcount, headquarters, funding or keywords | Company Search | Company records with name, domain, industry, size, headquarters and LinkedIn page, up to 50 per page |
| Size a total addressable market from headcount or from hiring | Company Search (TAM by people, TAM by jobs) | Distinct companies, each with a count of matching people or matching jobs |
| Find decision makers at target accounts by title, function, level and location | People Search | People inside the matching companies, the employees of one company, or the best decision maker from a prioritized list of titles |
| Spot hiring signals at a market or a single account | Job Search | Live job postings matched on title, location, seniority and how recently they were posted, or all open roles at one company |
| Turn a domain into its LinkedIn company page, profile an account, or split headcount by country or department | Company Enrichment | One company profile, conversion or headcount breakdown per request |
| Find a verified work email, refresh a CRM contact, or identify the person behind a work email | People Enrichment | A verified work email, or a full profile with career history |

The TAM operations are `POST /v2/company/tam-by-people` and `POST /v2/company/tam-by-jobs`. The [Company Search API reference](https://agents.blitz-api.ai/services/company-search/openapi.json) lists their fields, and every other service has its own reference in the same format.

## Prices

Every service on the storefront bills from one prepaid Credits balance, at one rate.

| Service | Billed per | Price |
|---|---|---|
| People Search | person returned | $0.001 |
| Company Search | company returned | $0.001 |
| Job Search | job posting returned | $0.001 |
| Company Enrichment | company resolved, or headcount breakdown returned | $0.001 |
| People Enrichment | verified work email found, or person profile returned | $0.001 |

Credits are prepaid from $0.50 per purchase, with $0.60 as the minimum for a card purchase and $99 as the most per purchase.

The smallest card purchase covers a real task. Build a list of 200 target accounts with Company Search and pull two decision makers at each with People Search, and that is 600 results, or $0.60. Any lookup that finds nothing lowers the bill. A $5 balance covers 5,000 results.

Prices and plan details come from the live [price list](https://agents.blitz-api.ai/manifest.json). Read it at call time rather than caching it.

## How to buy and call BlitzAPI from your agent

1. Point your agent at the storefront's [agent guide](https://agents.blitz-api.ai/llms.txt), or describe the task to the free task guide at `https://agents.blitz-api.ai/zeroclick/agent/guide?goal=URL_ENCODED_TASK`, which is read-only and never buys anything.
2. Check for an existing ZeroClick agent credential first, because one registration works at every ZeroClick storefront.
3. If there is none, register one through the [identity guide](https://agents.blitz-api.ai/auth.md): use Link identity when the agent acts for someone signed in to Link, and anonymous registration when it acts on its own.
4. Exchange the credential's assertion for an access token at `/oauth2/token`, and exchange again whenever the token expires, since tokens last minutes.
5. Read the Credits plan's `id` and `purchase.url` from the price list.
6. Send the purchase with your bearer token and an `amountUsd` of at least `purchase.cardMinimumUsd`, then read the priced 402 that comes back.
7. Resend the purchase with `"checkout": true` to get an unpaid hosted checkout URL, and either pay it with a Link Pay Token, if the agent works in a browser, or pass the URL privately to whoever approves the purchase.
8. Poll the returned `statusUrl` until the purchase completes, and only then call the API.
9. Claim the credential to a real email address, so the Credits outlive the anonymous credential's few days.
10. Send each API call to the storefront with the bearer token, read the results, and follow `cursor` for the next page.

## Example requests

Register an anonymous credential. The response carries an `identity.assertion`, which you store securely:

```http
POST https://agents.blitz-api.ai/agent/identity
Content-Type: application/json

{"type":"anonymous"}
```

Exchange the assertion for a short-lived access token:

```http
POST https://agents.blitz-api.ai/oauth2/token
Content-Type: application/x-www-form-urlencoded

grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion=<identity.assertion>
```

Buy Credits. The amount is a whole-cent string between $0.60 and $99:

```http
POST https://agents.blitz-api.ai/plans/{planId}/purchase
Authorization: Bearer <access token>
Content-Type: application/json

{"amountUsd": "5.000000"}
```

The storefront answers with one priced `402 payment_required`. Its body carries the exact `payment.amountUsd`, the `plan` and a `card` block that lists the card lanes. A `method="stripe"` challenge also arrives in the `www-authenticate` header. Resend the same purchase with `{"amountUsd": "5.000000", "checkout": true}` to receive the hosted `checkout.url` and the `statusUrl` to poll.

Once the purchase completes, call the API with the same method, path and body BlitzAPI's own API takes. We sent this Company Search for three US software companies of 51 to 200 people:

```http
POST https://agents.blitz-api.ai/v2/search/companies
Authorization: Bearer <access token>
Content-Type: application/json

{"company": {"industry": {"include": ["Software Development"], "exclude": []}, "hq": {"country_code": ["US"]}, "employee_range": ["51-200"]}, "max_results": 3}
```

The search matched 16,142 companies and returned the first three, as `max_results` set, drawing $0.003 from the Credits balance. Here is the start of that response:

```json
{
  "total_results": 16142,
  "results": [
    {
      "name": "TechCrunch",
      "industry": "Software Development",
      "type": "Privately Held",
      "size": "51-200",
      "employees_on_linkedin": 532,
      "hq": {"city": "San Francisco", "state": "California", "country_code": "US"},
      "domain": "techcrunch.com",
      "linkedin_url": "https://www.linkedin.com/[path]"
    },
    "… 2 more"
  ],
  "results_length": 3,
  "max_results": 3,
  "cursor": "[redacted]…"
}
```

The response also carried `zc-billing: {"status":"settled","fundingSource":"credit","chargedUsd":"0.003000","remainingCreditUsd":"0.585000"}`. We also sent `{"domain": "stripe.com"}` to `POST /v2/enrichment/domain-to-linkedin`. It came back with `found: true`, the company name Stripe, its LinkedIn company page and ten other possible matches, and it drew $0.001.

## If your agent has no wallet

Your agent doesn't need one. BlitzAPI accepts card payments only, and it does not offer wallet payments over x402 or MPP stablecoins. These are the card routes, all covered in the [card checkout instructions](https://agents.blitz-api.ai/payment/card.md):

- **Hand the checkout to a person.** Resend the purchase with `"checkout": true`. Creating the checkout needs no funds and no card. Send the URL privately to whoever approves the purchase, then poll `statusUrl` until it completes.
- **Pay the checkout as a browser agent.** Eligible Stripe checkouts accept Link Pay Tokens. First confirm the seller, the amount and the merchant account on the actual Stripe page, then submit a merchant-bound token from an authorized Link wallet. If that route can't be established, hand the checkout to a person instead.
- **Use a shared payment token.** If your platform grants a Stripe shared payment token for this seller, answer the purchase 402's `method="stripe"` challenge with it in `Authorization`. Move your bearer to `ZC-Agent-Authorization`.

For any BlitzAPI page a person should open, share it as the tracked hand-off link `https://agents.blitz-api.ai/outclick?url={URL-encoded seller page}`, so BlitzAPI knows the visit came from an agent.

## What to know

**What is charged, and when.** BlitzAPI sells on plans, not per call. The only payment is the Credits purchase or a top-up with `POST /extend`. After that, each result returned draws $0.001, and an empty page or a lookup that finds nothing draws nothing. A request rejected with 422 never ran and used no records. A delivered response with no `zc-billing` header billed nothing. If a delivery fails after a card payment, the card is refunded in full automatically. Paying the purchase 402 accepts ZeroClick's [buyer terms of service](https://www.zeroclick.ai/legal/buyer-terms-of-service), and a purchase an agent makes is attributed to the person or business it acts for.

**Limits.** Searches return up to 50 results per page and page by cursor. A single Credits purchase runs up to $99; the plan minimum is $0.50, and a card purchase starts at $0.60. The Credits plan shares the credential's verified email with BlitzAPI once the credential is claimed. Before buying again after lost state, check `GET /agent/entitlements` for the balance you already hold.

**Errors worth handling.** The [error reference](https://agents.blitz-api.ai/errors.md) lists every code. These are the ones your agent is most likely to meet:

| Error | What to do |
|---|---|
| `bearer_required` (401) | Register or reuse a credential, then retry with `Authorization: Bearer <token>`. |
| `plan_required` (403) | No plan covers the call. Buy Credits, then retry. |
| `usage_exhausted` | The balance ran out. Top up with `POST /extend` and `{"amountUsd": "10.000000"}`. |
| 422 | Fix the field named in `errors[].field`. Nothing was charged. |
| `payment_refunded` or `payment_consumed` | That payment is spent. Start a fresh purchase and pay its new 402. |
| `rate_limit_exceeded` (429) | Wait for `retry_after` or Retry-After before retrying. |

## Frequently asked questions

### Does BlitzAPI need an API key for AI agents?

No. Through the ZeroClick storefront, your agent registers a free credential and presents it as a bearer token, so it needs no BlitzAPI account and no API key.

### How much does BlitzAPI cost per result?

Every result returned costs $0.001, or $1 per 1,000, and a call that finds nothing costs nothing. Results draw from prepaid Credits, which start from $0.50, with a $0.60 minimum for each card purchase and $99 at most.

### Can my agent pay BlitzAPI with x402 or a crypto wallet?

No. BlitzAPI accepts card payments only, through a hosted Stripe checkout, a Link Pay Token or a shared payment token, and no crypto wallet is needed.

### How do I find a company's LinkedIn page from its domain with an AI agent?

Send `{"domain": "example.com"}` to `POST /v2/enrichment/domain-to-linkedin` on the BlitzAPI storefront with your bearer token. A match costs $0.001 from your Credits, and a miss costs nothing.

### Do I have to use an AI agent to use BlitzAPI?

No. A person can sign up at [blitz-api.ai](https://blitz-api.ai), start with 1,000 free records, and use every endpoint with one API key on plans from $99 a month.
