Email finding and verification for AI agents

Verify business emails before they enter your outbound queue

Give your agent a domain, person, or candidate address and receive a reviewable result with verification state, evidence notes, and handling guidance. NeverBounce keeps valid, invalid, catch-all, and unknown outcomes distinct so RevOps can decide what moves forward.

See the first result
Agent terminal showing an email verification resultnpx -y @okki-global/okki-go-taroball

Evidence grid

Four tasks, each with an explicit boundary

Find a business email

Input
Name and company domain.
Output
Candidate address plus confidence state.

Limit: a pattern match is not a verified mailbox.

Verify a candidate

Input
A business email selected for outreach.
Output
Valid, invalid, catch-all, or unknown.

Limit: a valid result cannot guarantee delivery or consent.

Prepare review context

Input
Verification state and campaign policy.
Output
Risk notes, checked time, suppression status, and source context.

Limit: catch-all and unknown require a policy decision.

Protect the send queue

Input
Human-approved candidates only.
Output
A reviewed handoff, not an automated blast.

Limit: authentication, opt-out, and regional rules remain operator duties.

4 statesValid · Invalid · Catch-all · Unknown
3 gatesVerify · Suppress · Review
1 timestampKeep the checked time
0 guaranteesDelivery and replies vary

Runtime matrix

Know what enters, runs, and leaves the agent

Input sources

Company domain
Public business identity · operator supplied

Candidate email
Professional contact · review required

Verification runtime

Syntax and domain checks
Network lookup · inspect locally

Provider connection
Scoped API secret · config-dependent

Output destinations

Agent result
State and evidence · local review

CRM or send queue
Only after approval · operator controlled

Four-state runbook

Copy is not the same as installed

  1. 1. Copynpx -y @okki-global/okki-go-taroball

    Success means the exact command is on your clipboard.

  2. 2. Run

    Execute it in your agent terminal. Inspect package identity, prompts, permissions, and completion output.

  3. 3. Configure

    Store provider credentials in environment secrets with minimum scope. Never paste API keys into a prompt.

  4. 4. First result

    Use known valid, invalid, catch-all, and ambiguous examples. Confirm state, timestamp, and review notes.

FAQ

Verification questions worth settling before scale

No. Verification reduces address risk; delivery also depends on reputation, content, authentication, provider filtering, and recipient behavior.

Treat catch-all as unresolved. Apply your risk policy, confirm relevance, use conservative sending, and monitor bounce signals.

No. Establish lawful purpose, relevance, suppression and opt-out handling, and applicable regional requirements first.