How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

_done email verifier API

The email verifier API from _done -- 1 operation. POST /verify takes one email address and returns a deliverability verdict (valid/risky/invalid), splits username and domain, and flags free-provider domains and role accounts. Verified 2026-09-03: the spec resolves, an invented control path 404s, and an unpaid POST /verify answers 402 -- the x402 door works as the catalog describes. Submitted by the provider via apis.io/add (1a293a63); the build gate parked it as a curated-record collision and it was merged by hand, which is the designed path.

_done email verifier API is one of 28 APIs that _done publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Email Verification. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://email-verifier.underscoredone.com.

1 operations 1 paths 4 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://email-verifier.underscoredone.com
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

_done email verifier API declares 1 security scheme for authenticating requests. An API key is passed in the header as SIGN-IN-WITH-X (siwx).

  • siwx — CAIP-122 wallet signature for repeat access after payment

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Network 1
POST
/verify
Verify if an email address is real and safe to send to
verify_email_verify_post body → 200422402400

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Response (7 properties), ValidationError (5 properties), Request (1 property), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
Request
object
1 property 1 required
Response
object
7 properties 6 required
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

done-email-verifier-validator-api-openapi.yml Raw ↑

Other APIs _done publishes across the network.

_done Catalog
_done asn lookup API
_done cors headers API
_done Data API
_done directory submission API
_done Dmarc API
_done dns lookup API
_done domain age API
_done domain availability API
_done Ens API
_done hacker news API
_done http headers API
Where this information came from

This is an independent, third-party profile of _done email verifier API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.