---
title: "How to use Tuski with your AI agent | ZeroClick"
url: https://zeroclick.ai/resources/how-to-use-tuski-with-your-ai-agent
fetched_at: 2026-11-06T11:23:58.007Z
---

# 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/28z2hf152yzd/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/28z2hf152yzd/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/28z2hf152yzd/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/28z2hf152yzd/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. If the Link CLI is already installed and signed in for that person, you can use their Link account for identity as well as payment, sharing their email only if they agree: follow [Link identity setup](https://agents.zeroclick.ai/zcj/28z2hf152yzd/auth.md#link-identity-preview) through issuance, presentation, registration and token exchange. Otherwise register anonymously; no Link setup is needed, and the person can claim the identity later.

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

# How to use Tuski with your AI agent

*October 22, 2026 · 10 min read*

Tuski checks a list of email addresses and gives each one of eight verdicts and a 0–100 quality score, backed by real bounce signals. It costs $0.01 per address. Tuski sells through ZeroClick: your agent creates a job at the [Tuski storefront](https://agents.tuski.ai), pays one priced 402 for the whole job, then reads status and results at no charge, with no signup and no API key.

**In short:**

- Send your list to `POST /api/v1/email-validation/jobs` on `https://agents.tuski.ai` with an `Idempotency-Key` header, and pay the single 402 that prices the job.
- The job is priced per address when it is created. Reading status and results costs nothing.
- Prepaid Credits bring the price from $0.01 down to as low as $0.0036 per address.
- An agent without a wallet can pay by card for jobs of $0.50 or more, buy Credits by card, or hand the purchase to a person.

## What Tuski is

Tuski builds AI-powered lead intelligence for revenue teams. Its validation runs every address through syntax, domain, and MX checks, screens for disposable domains and typos, then sends controlled probe messages and classifies the delivery-status notifications that come back. See the product at [tuski.ai](https://tuski.ai).

That fits the work an outreach, sales, or CRM agent is given. Such an agent often holds a list it built or was handed, and it needs to know which addresses are real before anything else happens. Tuski answers with evidence rather than a guess. Because jobs run asynchronously, your agent can create a job, carry on with other work, and collect verdicts as they land.

An agent storefront is the machine-readable version of a business: a URL where an agent reads what is for sale, the live prices, and the payment steps, then buys without anyone filling in forms. It sits in front of Tuski's own API as a transparent proxy that takes payment and forwards the request. For how storefronts work, see [What is an agent storefront?](https://zeroclick.ai/resources/what-is-an-agent-storefront)

## What agents use Tuski for

The storefront sells one service, Email Validation, which covers these jobs:

- **Validate a lead list before an agent sends.** Submit the addresses as a JSON list and get a verdict and score for each.
- **Clean a CSV export from a CRM.** Pass the export in as CSV text, with its header row intact and one column of addresses, and export results back as CSV.
- **Catch typos and disposable addresses.** Typo and burner domains are flagged before any probe is sent.
- **Separate shared inboxes.** Role addresses such as info@ and sales@ get their own verdict, so your agent can segment them.
- **Re-check a list.** Set `fresh_probe` to `true` to send a fresh probe to every address, even one with a recent result.

Each address gets one of eight headline verdicts:

| Verdict | What it means |
|---|---|
| deliverable | The probe completed with no bounce during the validation window |
| invalid | Hard bounce |
| catch-all | Several probes, no bounce observed; a heuristic flag for review |
| full box | The mailbox reported it is full |
| role | A shared inbox pattern |
| no MX | The domain has no mail server |
| burner | A known disposable-mail domain |
| typo | A likely misspelled domain |

The `verdict` field can also read `no_reply`, `blocked`, `unknown`, `soft_temp`, `routing_error`, `other_bounce`, or `not_judged` for rarer outcomes. The [API reference](https://agents.tuski.ai/services/email-validation/openapi.json) lists every field.

## Prices

| Plan | Price per address | Minimum purchase |
|---|---|---|
| Pay per address | $0.01 | none; one payment per job |
| Credits 500 | $0.006 | $3 |
| Credits 10,000 | $0.0055 | $55 |
| Credits 25,000 | $0.004 | $100 |
| Credits 50,000 | $0.0036 | $180 |

Reading a job's status, fetching its results, and cancelling it are free on every plan. At the stated rates, $3 on Credits 500 covers 500 addresses at $0.006, and $180 on Credits 50,000 covers 50,000 at $0.0036. A list of 10,000 addresses costs $100 pay as you go, or $55 on Credits 10,000.

Prices come from the live [price list](https://agents.tuski.ai/manifest.json), and every 402 states the exact amount before your agent pays. Read it at call time rather than caching it.

## How to buy and call Tuski from your agent

1. Point your agent at the Tuski storefront. Its [agent guide](https://agents.tuski.ai/llms.txt) links the catalog, the payment steps, and the API reference.
2. Prepare the addresses as a list of up to 100,000 entries, or as CSV text whose header row names an email column.
3. Send `POST /api/v1/email-validation/jobs` with a new `Idempotency-Key` and no payment header. The storefront answers with a 402 that prices the job.
4. Check the 402's `payment.amountUsd` against your budget before paying.
5. Pay the challenge from your wallet with x402 (USDC on Base) or MPP (USDC on Tempo), or by card when the job costs $0.50 or more.
6. Retry the identical request, with the same body and `Idempotency-Key`, plus the payment proof. Keep the `job_id` and `projected_finish_at` from the response.
7. Poll `GET /api/v1/email-validation/jobs/{job_id}`, which is free. Space the polls out, because the `wait` parameter is ignored on storefront requests, which return immediately.
8. When the status reads `done`, fetch `GET /api/v1/email-validation/jobs/{job_id}/results` page by page until `has_more` is false, or ask for `format=csv`.
9. Filter the rows by verdict and score for the task your agent was given.

## Example requests

Send the unpaid request first. This one submits two placeholder addresses:

```http
POST https://agents.tuski.ai/api/v1/email-validation/jobs
Content-Type: application/json
Idempotency-Key: <unique key for this job>

{"emails": ["a@example.com", "b@example.com"]}
```

The 402 body carries `payment.amountUsd`, the `plan`, and a `protocols` block with a challenge for each rail. The signable challenges also arrive as headers, so a standard x402 or MPP client can settle them without reading the body:

```http
HTTP/1.1 402 Payment Required
payment-required: <x402 challenge>
www-authenticate: <MPP challenge>
```

Resend the same request with the proof. On x402 the signed payload goes in `x-payment`; on MPP, send `Authorization: Payment <credential>` instead:

```http
POST https://agents.tuski.ai/api/v1/email-validation/jobs
Content-Type: application/json
Idempotency-Key: <same key>
x-payment: <signed x402 payload>

{"emails": ["a@example.com", "b@example.com"]}
```

A created job returns 201 with these fields and types, and a `zc-billing` header reconciles what was authorized against what was charged:

```json
{"job_id": "integer", "total": "integer", "queued": "integer", "long_queue": "boolean or null", "projected_hours": "number or null", "projected_finish_at": "string or null"}
```

Read the job's progress with a status call, which is free:

```http
GET https://agents.tuski.ai/api/v1/email-validation/jobs/{job_id}
```

When reading the status of a job drawn on a plan held by a ZeroClick agent credential, the response carries the job's id, status, total and queued counts, a counter for each outcome from `valid` through `other_bounce`, and an `eta` object with fields including `resolved`, `queued_remaining`, `sends_per_hour`, and `finalize_after_sec`.

Fetch results in pages of up to 5,000 rows:

```http
GET https://agents.tuski.ai/api/v1/email-validation/jobs/{job_id}/results?format=json&limit=1000&offset=0
```

The JSON page holds `job_id`, `rows`, `count`, `limit`, `offset`, and `has_more`. A CSV page has no `has_more`, so read the `X-Total-Count` header and follow the `Link` header's `rel="next"` instead.

## If your agent has no wallet

- **Create a wallet.** Your agent can set one up itself, free and with no signup, then follow the steps above. It can also pay through Zero, ZeroClick's own payment layer for agents, which pays services per call over x402 or MPP.
- **Pay a job by card.** Card works for any pay-as-you-go job priced at $0.50 or higher, which at $0.01 an address means a job with at least 50 addresses. Follow the 402's card block: POST to its `payUrl`, poll its `statusUrl` until complete, then retry the job with a `zc-payment-id` header. The [card checkout instructions](https://agents.tuski.ai/payment/card.md) cover hosted checkout, Link Pay Tokens for browser agents, and shared payment tokens over MPP.
- **Buy Credits.** Register a free agent credential with the [identity guide](https://agents.tuski.ai/auth.md), then send `POST /plans/{planId}/purchase` with `Authorization: Bearer <token>` and an amount such as `{ "amountUsd": "3.000000" }`, paying by wallet or card (`checkout: true` returns a hosted checkout URL). Each plan's id and `purchase.url` are in the price list. Covered calls then carry your bearer instead of a fresh payment, and `POST /extend` tops up the balance.
- **Hand off to a person.** Share any Tuski page as `https://agents.tuski.ai/outclick?url={URL-encoded seller page}`, or send the checkout URL privately to whoever approves the purchase.

Credits plans request the credential's verified email, which is shared with Tuski at purchase, or later once the credential is claimed.

## What to know

**What the storefront covers.** It sells Email Validation only. The company research, the MCP server, and the subscription prices on tuski.ai belong to Tuski's own channel for people.

**What is charged, and when.** The job is priced per address when it is created. Paying the 402 completes the purchase under ZeroClick's buyer terms. Status, results, and cancel calls cost nothing.

**Verdicts take time.** Probe sends are paced, so results arrive over time. `long_queue` is true when a job is expected to take more than 48 hours, and `projected_hours` is null when no mailbox can send.

**What a verdict means.** Deliverable means no bounce was observed during the validation window. The quality score is a relative signal, not a delivery guarantee.

**Cancelling.** Cancel refunds one credit per unsent address, and sent addresses still get their verdict. For a job paid through the storefront, `zeroclick_refund_note` explains that the refund landed in Tuski's shared wallet, not your agent's.

**Limits.** A job takes up to 100,000 addresses and a body of up to 26,214,400 bytes.

The [error reference](https://agents.tuski.ai/errors.md) lists every code. These are the ones your agent is most likely to meet:

| Error | What to do |
|---|---|
| 422, missing `Idempotency-Key` | Add the header and resend. |
| 409, idempotency conflict | Use a new key for a different list. Reuse a key only to replay the same job. |
| `payment_request_mismatch` (409) | The paid retry differed from the priced request. Get a new 402 and pay that. |
| 413, request too large | Split the list into smaller jobs. |
| 429, rate limited | Wait for `Retry-After`, then poll again. |
| `bearer_required` (401) | Register an agent credential before buying Credits. |
| `usage_exhausted` | Top up the Credits balance with `POST /extend`. |

## Frequently asked questions

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

No. Through the ZeroClick storefront your agent pays each job with a signed payment, which also identifies it, so no signup or API key is needed.

### How much does Tuski email validation cost?

Pay as you go costs $0.01 per address. Credits plans cost from $0.006 down to $0.0036 per address. Status and results reads cost nothing.

### Can my agent pay Tuski with x402?

Yes. The x402 challenge arrives in the `payment-required` header for USDC on Base, and your agent retries the same request with the signed payload in `x-payment`.

### How long does an email validation job take?

Small lists usually finish the same day. Large ones can take several days because Tuski paces its probe sends to protect deliverability. The job's `projected_finish_at` gives the expected finish time.

### Is a deliverable verdict a guarantee of delivery?

No. It means no bounce was observed during the validation window. Tuski describes its quality score as a relative signal rather than a delivery guarantee.

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

No. A person can sign up at [tuski.ai](https://tuski.ai) with no card to start, then pay as you go with credits that never expire or subscribe monthly, for example 150,000 credits for $150, and automate with a Tuski API key or its MCP server.

---

## More in Get more done with your agent

- [How to use PickPoint with your AI agent](https://zeroclick.ai/resources/how-to-use-pickpoint-with-your-ai-agent) - PickPoint sells geocoding, address search, and routing to AI agents through ZeroClick at $0.25 per 1,000 requests, on prepaid credit from one cent.
- [How to use Unsiloed AI with your AI agent](https://zeroclick.ai/resources/how-to-use-unsiloed-with-your-ai-agent) - Unsiloed AI parses, extracts, classifies, and splits documents for AI agents through ZeroClick, from $0.02 a page, paid per call with a free credential.
- [How to use Vimmerse with your AI agent](https://zeroclick.ai/resources/how-to-use-vimmerse-with-your-ai-agent) - Vimmerse sells image, video, and audio generation to AI agents through ZeroClick, at $0.03 a credit per call, with the exact credits quoted before you pay.

[All resources](https://zeroclick.ai/resources#get-more-done)
