Credits and billing
Only the SMTP check costs a credit. All the other checks are free and have no quota.
The billing rule
A credit is debited if, and only if, both conditions are met:
- SMTP was enabled for the call (on the API key, the widget's key, or the batch option);
- the final verdict is not unknown.
| Case | Credit |
|---|---|
| Key without SMTP | 0 |
| SMTP enabled, verdict valid, risky or invalid | 1 |
| SMTP enabled, invalid verdict obtained before the dialogue (wrong syntax, domain without a server) | 1 |
| SMTP enabled, unknown verdict (accept-all, greylisting, timeout) | 0 |
| SMTP enabled, noreply address without a conclusive answer (final verdict risky) | 1 |
| Address on the allowlist or blocklist | 0 (SMTP does not run) |
Verified typo correction (typoCorrection) | 0 (free check) |
| Suggestion and enrichment endpoints | 0 |
| Integration: list clean-up, new contact or single contact verified | Same rules as above (SMTP enabled by default) |
| AI assistant: single or batch verification | Same rules as above, depending on the connection's SMTP setting |
| AI assistant: B2B email finder | 0 (quota of 20 searches per day) |
A verdict obtained before the SMTP dialogue is billed because the result is final and usable: an address without a mail server will never receive mail.
Plans
| Plan | Price | SMTP credits |
|---|---|---|
| Free | €0 | 100 welcome credits on sign-up, once only |
| Starter | €29 excl. VAT / month | 25,000 credits per month, not carried over from one month to the next |
| Pro | €99 excl. VAT / month | 100,000 credits per month, not carried over from one month to the next |
The monthly allowance is credited at each subscription renewal. Whatever has not been used is lost when the period ends: it is not added to the next allowance. Pack credits, on the other hand, are never lost.
There is no overage billing. Once the allowance is used up, calls with SMTP receive 402 until you top up with a pack, usable straight away, or upgrade from Starter to Pro. Subscriptions have no commitment: cancellation takes effect at the end of the paid period and can be reversed until then.
Change plan
You change plan from Credits in the dashboard.
| Direction | Takes effect | Billing | Credits |
|---|---|---|---|
| Starter → Pro | Immediately: a new monthly period starts the same day | Pro is billed straight away, minus the unused part of Starter for the current period | Pro's 100,000 credits replace what is left of the Starter allowance as soon as payment is confirmed |
| Pro → Starter | At the next renewal | No refund; Starter is billed at renewal | You keep the Pro allowance until the end of the period, then receive 25,000 credits per month |
If payment for an upgrade does not go through (authentication requested by the bank, card declined), the subscription stays on Starter and no Pro credits are opened. Purchased packs are never affected by a change of plan.
Credit packs
Available to buy at any time from Credits in the dashboard, from 1,000 to 5,000,000 credits, with a decreasing unit price. Purchased credits never expire.
The up-to-date catalogue (plans, packs, prices excl. VAT) is public:
curl https://api.yeswecheck.fr/v2/billing/catalog
{
"currency": "eur",
"taxBehavior": "exclusive",
"plans": [
{ "code": "starter", "name": "Starter", "amountCents": 2900, "monthlyCredits": 25000, "unlimited": false, "purchasable": true },
{ "code": "pro", "name": "Pro", "amountCents": 9900, "monthlyCredits": 100000, "unlimited": false, "purchasable": true }
],
"packs": [
{ "name": "Pack 1 000 crédits", "credits": 1000, "priceCents": 500, "unitPriceCents": 0.5, "purchasable": true }
]
}
Excerpt; the full response contains every plan and every pack.
Consumption order
Your balance can combine three kinds of credits. They are consumed in this order, from the most perishable to the most durable:
| Order | Source | Expiry |
|---|---|---|
| 1 | Monthly subscription allowance | At renewal |
| 2 | Free credits (welcome, goodwill gesture) | Depends on the case |
| 3 | Purchased packs | Never |
So your purchased credits are never consumed while some of the month's allowance remains.
Track the balance
- In every verification response with SMTP:
metadata.credits.used(0 or 1) andmetadata.credits.remaining(balance after the call). Without SMTP,remainingis 0: it is not filled in. - In the dashboard: balance, transaction history, invoices.
- Through alerts (Settings → Notifications), each one adjustable and can be turned off: balance running low, low balance, balance used up. An alert is sent once per episode and re-arms when the balance goes back up.
With an API key, GET /v2/me returns the organisation balance and the key's usage, without debiting any credit (the Get credit balance module of the Make app); an AI assistant reads it with the get_credits tool of the MCP server.
Insufficient balance: 402
When SMTP is requested and the balance is zero, the call is refused before any check:
HTTP/1.1 402 Payment Required
Content-Type: application/json
{
"statusCode": 402,
"message": "Insufficient credits for SMTP validation",
"code": "INSUFFICIENT_CREDITS",
"timestamp": "2026-10-15T09:12:44.512Z",
"path": "/v2/email/validate"
}
Test code, not message. To keep verifying without SMTP until you top up, keep a second key without SMTP as a fallback.
429, not 402If the account has credit but the key has reached its daily or monthly cap, the response is 429 API_KEY_BUDGET_EXCEEDED. Topping up makes no difference. See Error codes.
In batch processing, a used-up balance does not stop the job: the remaining rows are verified without SMTP.
VAT, invoices and refunds
See the billing FAQ.