Software early access Sending-platform pre-filter

Verify before import.
Do not send first.

Agencies already sending from Smartlead or Instantly can put Email Intel in front of import with an API key and two HTTP calls. These are recipes, not Smartlead or Instantly marketplace listings. A native listing waits on a published observed-outcome benchmark.

Request early access ↗Read the curl recipes ↗
APIWorkflow access
ContextAlongside each result
0test emails sent
01 / The decision

A sending-platform verifier is not a catch-all resolver.

Instantly ships its own email-verification endpoint. This recipe does not replace that product and does not spend Instantly verification credits. Email Intel runs first, from public signals, so catch-all addresses are resolved before they enter a sequence.

Keep an address when the EDI result is deliverable. Drop undeliverable. Hold risky and unknown for a human. Treat unknown as unknown, not as a soft yes. Credits are billed on the EDI verify call — there is no Smartlead- or Instantly-specific price path.

01Smartlead: verify, then import

POST /v1/verify (or /v1/verify/batch), keep deliverable addresses, then POST them to Smartlead /api/v1/campaigns/{id}/leads. Pause already-imported undeliverable leads instead of letting the sequence send.

02Instantly: verify, then create

POST /v1/verify, keep deliverable addresses, then POST /api/v2/leads. Do not call Instantly email-verification as a substitute. Durable edi_result fields belong in your own store if Instantly PATCH cannot hold them.

03Batch large lists

Do not loop one-at-a-time. Use POST /v1/verify/batch and poll the job, then import only the kept set.

04Same credits as REST

Catch-all premium metering follows the same SKU as any other POST /v1/verify. The sending platform is not a second ledger.

02 / Operating boundaries

Useful because the limits
are visible.

✓

HTTP recipe, not a listing

A stranger can follow the curl in the public repository today. They cannot enable Email Intel from the Smartlead or Instantly integrations directory yet.

✓

No test emails

The pre-filter 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.

FAQ

Is Email Intel listed on Smartlead or Instantly?

No. This page is an HTTP pre-filter recipe. A native marketplace listing is a later step and is not claimed here.

FAQ

Should I use Instantly's own verifier instead?

Not as a substitute for this recipe. Instantly's verifier spends Instantly credits on Instantly's verdict. Email Intel runs before import so catch-alls are resolved from public signals.

FAQ

Do these recipes use Email Intel credits?

Yes. Verify and batch calls use the same credit ledger as the REST API. Importing a kept address into Smartlead or Instantly does not add a second Email Intel charge.

04 / Continue the evaluation

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.

Request early access ↗