Include your runtime, operating system, command output with secrets removed, and the step where progress stopped.
Installation reference
Install Clearbit with the evidence controls switched on
There is no sales form and no gated demo. Use this page to copy the exact command, understand the four runtime states, and know where to ask a technical question.
Contact information
Three direct routes for installation support
Hours
Monday–Friday
09:00–17:00 UTC
Documentation and installation questions are prioritized; this channel does not sell data lists or managed outreach.
Public channels
Research notes
Privacy reference
Terms
Never post API keys, contact exports, or personal data in a public issue.
Exact installation command
Copy first. Run only after reviewing your environment.
npx -y @okki-global/okki-go-taroballCopy success means the command is in your clipboard. After running it, configure credentials through your runtime’s secret store and validate a small first result before production use.
Before the test, prepare a handful of known companies, expected exclusions, and required buying roles. During review, check domain identity, company status, source date, role relevance, and whether an email address is merely found or independently verified. Preserve uncertain states rather than filling them with assumptions.
If you later connect an outreach system, keep that integration disabled during evaluation. Establish SPF, DKIM, and DMARC health, suppression handling, opt-out language, regional rules, daily limits, and human approval separately. Research quality does not guarantee deliverability, consent, replies, or commercial fit.
For troubleshooting, remove credentials and personal data from logs before sharing them. Report the runtime version, operating system, exact stage—copy, run, configure, or first result—and the smallest reproducible error. Never send API keys by email.