Introduction
YesWeCheck verifies an email address and returns a verdict you can act on: can you write to it, and at what risk? Each verification runs a series of checks (syntax, DNS, disposable address, typo, trap domain, role account, noreply address, SMTP dialogue…) and returns the details of each one.
Four ways to integrate
Your backend calls POST /v2/email/validate and decides what to do with the address.
No server codeForm widgetA script tag with no secret: verification as the user types, a suggested correction, submission blocked if needed.
DashboardBulk processingA CSV or TXT file of up to 500,000 lines, exported as CSV, Excel, JSON or PDF.
MCP serverAI assistantsClaude, ChatGPT, Le Chat, Cursor or your own agents verify addresses and find B2B emails, with your rules and your credits.
What you can access with an API key
The public API, the one a server calls with a ywc_live_… key, covers verification and input assistance:
| Endpoint | Purpose | Authentication |
|---|---|---|
POST /v2/email/validate | Verify an address | API key |
POST /v2/email/enrich | Infer first name, last name, gender, presumed age | API key |
POST /v2/email/suggest/localpart | Suggest local parts from a name | API key |
POST /v2/email/suggest-firstname · suggest-lastname | Autocomplete a first name or last name | API key |
GET /v2/email/suggest/domain/countries | Countries covered by domain suggestions | API key |
POST /v2/email/suggest/domain | Autocomplete a domain (gmail.com, orange.fr…) | API key or widget |
POST /v2/email/suggest/typo-domain | Detect a typo in the domain | API key or widget |
POST /mcp | AI assistants' MCP server: verification, batches, B2B search, credits | API key or OAuth |
GET /v2/billing/catalog | Plans and credit packs, prices excl. VAT | None |
GET /health | API status | None |
Each endpoint is described in detail in the API reference.
Creating API keys, bulk processing, widgets, allow and block lists, validation policies and billing are all managed from app.yeswecheck.fr. Their HTTP routes only accept a dashboard session: an API key gets 401. So they are not part of the public API documented here. One exception: AI assistants start and track batches, and read the balance, through the MCP server's tools.
The essentials in five points
- One base URL:
https://api.yeswecheck.fr/v2. Only/health,/statusand the MCP server (/mcp) are served outside the/v2prefix. - One header:
Authorization: Bearer ywc_live_…. TheX-API-Keyheader is not read. See Authentication. - SMTP is set on the key, not in the request: a key created with SMTP enabled runs it on every call; a key without SMTP never runs it. See Checks.
- A credit is only charged if SMTP was enabled and the final verdict is not
unknown. All other checks are free. See Credits. - The verdict is in
result(valid,risky,invalid,unknown), along with ascorefrom 0 to 100. See Verdicts and score.
Useful links
| Dashboard | app.yeswecheck.fr |
| Platform status | status.yeswecheck.fr |
| OpenAPI specification | docs.yeswecheck.fr/openapi.yaml |
| Support | [email protected] |