Use case, Email verification

Email verification API for your agent. One call per address.

Send an email address. Read deliverability status and catch-all flag back. Your agent picks the provider, and you pay per call.

Give this to your agent
set up looot - https://looot.ai/skill.md

The job

What the Email verification API gives your agent

A verifier answers one question before you send: will this address bounce. Your agent sends the address, the provider checks the syntax, the mail server and the mailbox, and a status comes back. Several providers sell this check, and they do not return the same fields.

The part that matters most is the catch-all flag. Some domains accept mail for any name, so a clean check proves little. Most providers here report it, and a few add a confidence score or a typo suggestion, so your agent can fix jane.doe@exmaple.com before it spends anything else.

You give

an email address

jane.doe@example.com

You get

  • Deliverability status
  • Catch-all flag
  • Mail provider
  • Confidence score
  • Typo suggestion

Sample calls

The request and what comes back

Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.

Request
{"endpointId":"icypeas-email-verify","input":{"email":"jane.doe@example.com"},"wait":30}
ResponseSample output
// POST /v1/runs, then read run.status and run.result
// result: waits up to 60 seconds and returns FOUND or NOT_FOUND with a certainty and the MX details, with catch-all detection

The prompt

Copy one prompt, give it to your agent.

Edit the names and numbers, paste it, and the agent runs the job and shows the cost.

  • One run is one address.
  • 1 steps across 7 providers.
  • Runs on demand, whenever you ask.
Prompt: Email verification API
Use looot to check whether jane.doe@example.com can receive mail, and tell me if the domain accepts every address. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

Give this to your agent
Setup command
set up looot - https://looot.ai/skill.md

Before you start

Settle these before the first run

  • Verify the address you plan to send to, not the one you guessed. A found address that was never verified is the usual cause of a bounce.
  • Treat catch-all as its own result. Keep those rows apart and decide per campaign whether to send.
  • Run the cheap check on the whole list first. Spend more only on rows the first provider could not settle.

FAQ

Questions people ask

Send the address to a verification endpoint and read the status. Your agent picks the provider, and each one answers in its own fields. The endpoint's page lists the exact input, which is one email field for every provider on this page.

For agents
use case
Email verification API
run
address
schedule
on demand
step
Verify the address: icypeas leadmagic tomba hunter zerobounce findymail anysite
setup
https://looot.ai/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04
markdown /use-cases/email-verification-api.md

Try Email verification with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.

Start your workspace See agent recipes