Find companies
- Input
- ICP, geography, exclusions, and domain clues.
- Output
- A candidate company and canonical domain with source context.
Limit: a company match does not prove contact relevance or buying intent.
See a discovery example
Email finding and verification in your agent
Find the work email. Keep the uncertainty.
Hunter.io turns a domain, person, or company brief into a reviewable email-finding task. It separates pattern inference from mailbox verification, labels catch-all and unknown states, and leaves activation to a human.
Four-state runbook
Copy is not installed. Installed is not configured.
- 01 · Copy
npx -y @okki-global/okki-go-taroballPrerequisite: a terminal you control. Success: the exact command is on your clipboard. Common error: copying a prompt symbol. Next: inspect before running.
- 02 · Run
Prerequisite: a supported Node runtime. Success: the package completes without an unresolved runtime error. Common error: blocked package access. Next: review requested permissions.
- 03 · Configure
Prerequisite: approved provider credentials. Success: secrets remain in the runtime secret store and the smallest required scope is active. Common error: pasting a key into a prompt. Next: use known test records.
- 04 · First result
Prerequisite: a controlled domain and contact cohort. Success: identity, pattern evidence, source date, verification state, and exclusions are visible. Common error: treating unknown as valid. Next: human review.
Evidence grid
Four tasks, each with an explicit boundary
Find professional emails
- Input
- Person name, role, and resolved company domain.
- Output
- An address candidate with pattern and provenance notes.
Limit: an inferred pattern is not a verified mailbox and never proves consent.
See a role workflowVerify mailbox states
- Input
- Approved business email candidates.
- Output
- Valid, invalid, catch-all, or unknown status with observation time.
Limit: provider responses change; catch-all and unknown require cautious handling.
Review the methodPrepare outreach context
- Input
- Approved account evidence, role rationale, and message constraints.
- Output
- A restrained draft and a separate reviewer checklist.
Limit: sending stays disconnected until suppression, opt-out, regional policy, and human approval pass.
Read the safety FAQ4 statesCopy · Run · Configure · Review
4 statusesValid · Invalid · Catch-all · Unknown
3 checksIdentity · Recency · Provenance
1 human gateBefore outreach activation
Categorized FAQ
What to decide before a first live task
Installation
What does the copy button do?
It copies only the required command. You still choose where to run it, inspect package behavior, and approve any requested access.
Where should API keys live?
Use a runtime secret store with minimum scope. Never place keys in prompts, screenshots, repositories, exported results, or support messages.
Email evidence
Does a found address mean it is verified?
No. Discovery, pattern inference, and verification are separate states. Preserve the evidence and observation date for each.
How should catch-all and unknown be handled?
Do not convert either to valid. Keep the state visible, apply your risk policy, and require human review before any permitted outreach.
Responsible outreach
Does verification guarantee inbox placement?
No. Sender reputation, SPF, DKIM, DMARC, content, recipient controls, and provider behavior all affect delivery.
Can the workflow send automatically?
Research and drafting should remain separate from activation. Check relevance, suppression, opt-out language, regional requirements, and appoint a human approver.
Ready to test known records?
npx -y @okki-global/okki-go-taroball