Pre-launch · API in development

An email verification API that tells you why

One HTTPS call returns a verdict, a reason code and an explanation you can show your user, in English or Spanish. The API isn’t open yet: this page says what is planned, what it will cost and what you can test today.

Works today

  • Free web checker
  • Format, domain & mail servers
  • Disposable providers

At launch

  • REST API with keys
  • Mailbox check (no email sent)
  • Catch-all detection
  • Batches in JSON or CSV

What one call returns

You send an address with your secret key and get JSON back. The example follows version 1 of the API contract; the API isn’t open yet.

API v1 · in development, response abridged
# request
POST /v1/verify
Authorization: Bearer sk_live_…
{ "email": "ana@example.com", "mode": "mailbox" }

# response
{
  "email": "ana@example.com",
  "mode": "mailbox",
  "verdict": "valid",
  "reason_code": "mailbox_exists",
  "reason": "The mail server accepts this recipient and rejects a random one.",
  "flags": { "disposable": false, "free": false, "catch_all": false },
  "credits_charged": 1,
  "retry_at": null
}
  • mode: basic (the default) or mailbox. See the two kinds of check below.
  • verdict: one of valid, invalid, risky or unknown.
  • reason_code: a stable code your program can branch on, such as mailbox_exists, mailbox_not_found, catch_all, disposable_domain or domain_not_found. New codes may be added, so treat one you don’t know by its verdict.
  • reason: the same reason in plain words, in English or in Spanish if you send Accept-Language: es. You can show it to the person filling in your form.
  • flags: whether the domain is disposable, a free webmail provider or a catch-all server. catch_all is null when it wasn’t tested.
  • credits_charged: 0 or 1, so you know what each result cost.
  • retry_at: when a temporary result can be checked again, or null.

The full response also carries an identifier, the steps that ran, the domain’s mail servers and what the server answered. A bounce probability is in preparation and is not part of version 1 of the contract; we aren’t giving a date. If it is added it will be a new field, so existing integrations keep working.

Two kinds of check

Not every use needs the same depth. A sign-up form needs an answer while the person is still on the page; a list about to receive a campaign needs to know whether each mailbox exists.

CheckWhat it looks atPlanned price
Sign-up check
mode: basic
Format, domain and mail servers, disposable and legacy providers. No contact with the mailbox server, so it normally answers in well under a second and never returns valid: a healthy domain gives unknown with mailbox_not_checked.Free: 1,000 a month. Basic: €9 a month for 20,000. Basic+: €29 a month for 150,000.
Mailbox verification
mode: mailbox
All of the above, plus a conversation with the recipient’s mail server that ends before any message is sent, and a catch-all control. It can take up to 30 seconds.Free: 100 a month, up to 20 a day, no rollover. Packs: 2,500 for €9, 10,000 for €29, 50,000 for €99, 100,000 for €179.

Planned prices in euros, VAT excluded; they may change before launch. A mailbox credit is charged only when the verdict isn’t “unknown”, duplicates in a list are free and pack credits don’t expire while your account is active (see the terms). A sign-up check uses one monthly check each time it completes, except when the domain’s DNS fails temporarily. See pricing.

For lists there are batches: up to 10,000 addresses as JSON or a CSV file of up to 100,000 rows, verified in the background, with results as JSON or CSV. Your plan may set a lower limit. More in email list cleaning.

Using it in a sign-up form

Email validation at sign-up goes wrong in two ways: letting rubbish in, or locking real people out. These rules keep both under control with any verification API, ours included.

  1. Call the API from your server, never from the browser. An API key in front-end code can be copied by anyone who opens the developer tools.
  2. Reject only what is certainly wrong. An invalid verdict means a broken format or a domain that doesn’t exist or doesn’t accept mail. Show the reason, so someone who mistyped can fix it.
  3. Set your own policy for risky. A disposable address may be acceptable for a newsletter and not for a free trial. See the disposable email checker.
  4. Never block on unknown or on a timeout. In a sign-up check, unknown with mailbox_not_checked is the normal answer for a good address. And if the API is slow or unreachable, let the sign-up through and check later. Losing a real customer costs more than one bad address.
  5. Keep the confirmation email where you need proof of ownership. Verification tells you an address can receive mail, not who is typing it.

What the API will not do

  • Send email to the addresses you check. Not a test message, not a “ping”.
  • Build profiles of people or enrich your contacts with data from elsewhere.
  • Hide who is asking. Mailbox checks come from an identified host, with a public page that explains what it does on a mail server and how to reach us.
  • Promise certainty where there is none. Some servers accept every address and others refuse to answer; in those cases you get risky or unknown with the reason, and in mailbox verification unknowns are free.

Use it from your AI agent

An AI agent will be able to use SalchiMail in two ways, both with the same API key and the same credits as the API. Neither is open yet: they arrive with the API.

  • A remote MCP server (Streamable HTTP) for Claude Code, Cursor, VS Code and any other client that takes a remote server with a header. It authenticates with your API key as a Bearer token.
  • A skill in the open Agent Skills format. It works with curl alone, so it needs no MCP server.
MCP server · coming soon

Claude Code

claude mcp add --transport http salchimail https://mcp.salchimail.com/mcp \
  --header "Authorization: Bearer $SALCHIMAIL_API_KEY"

Cursor, VS Code and other clients

{
  "mcpServers": {
    "salchimail": {
      "type": "http",
      "url": "https://mcp.salchimail.com/mcp",
      "headers": { "Authorization": "Bearer ${SALCHIMAIL_API_KEY}" }
    }
  }
}

The key names differ between clients (mcpServers or servers; http, streamable-http or streamableHttp), so check your client’s documentation.

The server has eight tools. Six need your key: verify_email checks one address; create_batch, get_batch, get_batch_results and cancel_batch handle lists of up to 10,000 addresses; and get_usage shows credits and limits. get_plans and get_purchase_link work without a key. A check costs the same as through the API, and the other tools are free.

Asked “does the mailbox ana@example.com exist?”, an agent calls verify_email with mode: "mailbox", gets back the verdict valid with the reason code mailbox_exists, and answers in plain words. Payment always happens in your browser: the agent gives you a link and never handles card details.

Documentation: coming soon

The API reference (docs.salchimail.com) and the MCP server (mcp.salchimail.com) are planned and not published yet. Until they are, this page is the public description of the API. The verification engine will be published as open source under AGPL-3.0 at launch, so anyone can audit what happens to each address.

FAQ

Questions about the API

Can I use the API today?

Not yet. The API is in development and opens with the launch; people on the waitlist get in before the public opening. Today you can use the free web checker on the home page, which covers format, domain and disposable providers.

Will there be a free tier?

Yes. The planned free plan includes 1,000 sign-up checks and 100 mailbox verifications a month (up to 20 a day), with no rollover. Anti-abuse limits apply: one free account per person.

Do you charge for “unknown” results?

Not in mailbox verification: if the mail server gives no usable answer, the result says why and costs nothing. A sign-up check is different. It never contacts the mailbox server, so “unknown, mailbox not checked” is its normal answer for a healthy domain, and it uses one of your monthly checks.

Where will the data be processed?

At launch we’ll act as your data processor, with data hosted in the EU and a data processing agreement (DPA) for every customer.

Be among the first with an API key

Founder spots are open. Reserving one takes 20 seconds and costs nothing.

Reserve a founder spot