Email Verification API

Email Verification Icypeas API

Verify an email address. A valid negative verdict is a successful, billable result.

$2.40/1k req, pay per request, no subscription.

What the API returned
{
"status": "FOUND",
"email": "marcus.oyelaran@driftlinelabs.com",
"certainty": "ultra_sure",
"mxProvider": "Google Workspace",
"mxRecords": [...],
"createdUtc": 1732646400,
"modifiedUtc": 1732646415,
"scanId": "scn_6e21a8b4f0",
... 10 more fields
}
Uptime
71.56%
30d · 1,315 calls
Requests
1,315
30d · weekly, last 12 wks
Response
6.4s
median · 30d

Pricing

Email Verification Icypeas API pricing

You pay
$24.00
$2.40/1k req, only for what you use. No monthly plan.
Your first 41 requests are free with the $0.10 starting balance.

Try it

Get Email Verification icypeas in one request

Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 13 of 21 fields. See every field

{
  "found": true,
  "data": {
    "status": "FOUND",
    "email": "marcus.oyelaran@driftlinelabs.com",
    "certainty": "ultra_sure",
    "mxProvider": "Google Workspace",
    "mxRecords": [
      "aspmx.l.google.com",
      "alt2.aspmx.l.google.com"
    ],
    "createdUtc": 1732646400,
    "modifiedUtc": 1732646415,
    "scanId": "scn_6e21a8b4f0",
    "scanName": "__icypeas__individual",
    "scanUser": "usr_3f9d21",
    "scanOrder": 0
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-11-05 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • emailstring

    marcus.oyelaran@driftlinelabs.com

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

datadata

Normalized verification result.

  • certaintystring

    ultra_sure

    Confidence rating for the address, returned verbatim as the source spells it (ultra_sure in the captured response). It is not remapped to another verdict vocabulary.

  • createdUtcnumber

    1732646400

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • emailstring

    marcus.oyelaran@driftlinelabs.com

    The verified email address as the source returned it.

  • firstnamestring

    First name carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not.

  • fullnamestring

    Full name carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not.

  • genderstring

    Gender carried by the source's scan record, returned verbatim. Present only when that record holds identity data, which the verification path usually does not; the source's UNKNOWN sentinel is reported as absent.

  • lastnamestring

    Last name carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not.

  • linkedinUrlstring

    LinkedIn profile URL carried by the source's scan record. Present only when that record holds identity data, which the verification path usually does not.

  • modifiedUtcnumber

    1732646415

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • mxProviderstring

    Google Workspace

    Mail provider detected from the address domain's MX records.

  • mxRecordsstring[]

    MX record hosts published by the address domain.

  • phonesany

    Phone numbers carried by the source's scan record, passed through in whatever shape the source returns them. Empty in the captured response and absent when the source holds none, so this field is not type-constrained.

  • saasServicesany

    SaaS services carried by the source's scan record, passed through in whatever shape the source returns them. Empty in the captured response and absent when the source holds none, so this field is not type-constrained.

  • scanIdstring

    scn_6e21a8b4f0

    The source's own identifier for the scan record behind this verification, surfaced so a result can be traced back to it at the source.

  • scanNamestring

    __icypeas__individual

    The source's own label for the kind of scan record it created, returned verbatim (__icypeas__individual in the captured response). It is not a person's name.

  • scanOrderinteger

    0

    Position the source assigned to this record within the scan it belongs to; 0 for a single-address verification.

  • scanUserstring

    usr_3f9d21

    The source's own identifier for the account that ran the scan.

  • statusstring

    FOUND

    Scan outcome for the address, returned verbatim as the source spells it (FOUND in the captured response; the scan also reports NOT_FOUND). This is not the good/risky/bad vocabulary used by email.verify.

top level
  • foundboolean

    true

    Whether the source returned a completed verification. A negative verdict is a successful, billable result.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the Email Verification Icypeas API

The AnyAPI Email Verification Icypeas API returns Email Verification icypeas data as normalized JSON from one POST call to /v1/run/email_verification.icypeas. Verify an email address. A valid negative verdict is a successful, billable result. AnyAPI returns one normalized schema whichever source serves it. It costs from $2.40 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 71.6% of Email Verification icypeas calls through AnyAPI succeeded, with a median response time of 6.4 seconds across 1,315 measured calls.

It costs from $2.40 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Verify an email address. A valid negative verdict is a successful, billable result. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 71.6% of Email Verification icypeas calls through AnyAPI succeeded, with a median response time of 6.4 seconds across 1,315 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 41 Email Verification Icypeas calls at $0.0024 each.

Send a POST request to https://api.getanyapi.com/v1/run/email_verification.icypeas with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.