HTTP recipe, not a listing
A Clay user can configure this today with an API key. Email Intel is not in the Clay data-provider directory yet, and this page does not claim that listing.
Software early access Clay HTTP action
Verify in the waterfall.
Enrich only what you can defend.
Clay already has the people. Email Intel adds a catch-all-aware verify step before enrich: public signals only, an explicit result and confidence, and no test message to the address. This is an HTTP action recipe, not a Clay data-provider listing.
APIWorkflow access
ContextAlongside each result
0test emails sent
01 / The decision
Enriching an unresolved catch-all wastes the expensive columns.
A Clay waterfall that enriches every Find People row will spend credits on addresses a catch-all mail server would accept for anyone. Verify first. Keep deliverable. Drop undeliverable. Hold risky and unknown for review.
The HTTP action is POST /v1/verify with a Bearer API key and {"email":"{{Email}}"}. Map result, confidence, catchAll.domainIsCatchAll, catchAll.resolved, and creditsUsed. Credits are billed on that verify call — the same SKU as REST, n8n, or Zapier.
01HTTP API column
Add Column → Action → HTTP API. Method POST. URL https://email-intel-api-production.up.railway.app/v1/verify. Headers: Authorization: Bearer YOUR_EDI_API_KEY and Content-Type: application/json. Body: {"email":"{{Email}}"}.
↗02Map the decision fields
result (deliverable / undeliverable / risky / unknown), confidence (0–1), catchAll.domainIsCatchAll, catchAll.resolved, and creditsUsed. Treat unknown as unknown.
↗03Filter before enrich
Keep deliverable rows. Remove undeliverable and critical domain risk. Do not enrich a catch-all that did not resolve.
↗04Batch large tables
For 1,000+ rows, use POST /v1/verify/batch instead of one HTTP action per row, then join results back on email.
↗02 / Operating boundaries
Useful because the limits
are visible.
No test emails
The action never sends a message to the target mailbox. Verification uses public signals only.
No accuracy number here
We do not publish a head-to-head accuracy claim until a replacement benchmark uses observed customer delivery outcomes.
03 / Questions buyers ask
Clear answers before
you commit.
Is Email Intel listed as a Clay data provider?
No. This page is an HTTP action recipe. A Clay directory listing is a later operator step and is not claimed here.
Does the Clay action send test emails?
No. Email Intel resolves catch-alls from public signals. The target mailbox does not receive a verification message.
Do Clay HTTP rows use Email Intel credits?
Yes. Each /v1/verify call uses the same credit ledger as the REST API. Clay enrichment credits are separate and should only be spent on rows you kept.
04 / Continue the evaluation
Verification API
The evidence model the HTTP action calls.
Smartlead and Instantly
The same verify-then-import idea for sending platforms.
MCP, n8n, Zapier, Make
Private automation connectors over the same API.
Start with evidence
Build your verification workflow.
Start with Email Intel.
Tell us your verification volume and integration needs. We will confirm the available software workflow during early-access onboarding.