LinkedIn-led discovery
Translate target functions, seniority, geography, and company constraints into a reviewable discovery brief.
LinkedIn prospecting, agent-native
From target profile to review queue in one workflow
Give your agent an ICP, approved sources, exclusions, and a freshness window. Wiza organizes company context, professional identity, contact verification state, and the reasons each record needs human review.
View the four-step installFour-state runbook
Copy. Run. Configure. Inspect.
- 01 Copy
npx -y @okki-global/okki-go-taroballThe clipboard changes; your environment does not.
- 02 Run
Paste into a supported terminal, inspect the package prompt, and read the completion output.
- 03 Configure
Store API keys outside prompts and grant only the scopes required for the test.
- 04 First result
Use known profiles to inspect identity, role, source date, exclusions, and unresolved fields.
Capabilities
A compact path through prospect research
Company and role resolution
Keep operating name, domain, role evidence, and conflicting attributes visible instead of collapsing uncertainty.
Contact verification state
Separate a discovered address from its verification status; never treat a returned field as a delivery promise.
Human-in-the-loop handoff
Route approved records to the next system only after relevance, suppression, opt-out, and regional checks.
Data behavior ledger
Know what is verified, configured, or unknown
Sources
Config-dependent. Record provider terms, observation dates, field provenance, and permitted use.
Credentials
Operator controlled. Keep tokens in a secret store, away from prompts, screenshots, exports, and shared logs.
Runtime
Inspect locally. Review network calls, permission requests, retry behavior, and output destinations.
Retention
Policy required. Define access, correction, suppression, deletion, and audit ownership before production use.
FAQ
Before the first prospecting run
Installation
Does copying install Wiza?
No. Copying only places the exact command in your clipboard. You must run it, inspect the package response, configure approved connections, and review a first result.
Where should credentials live?
Use the secret mechanism provided by your runtime. Do not paste keys, cookies, or tokens into a prompt or repository.
Prospect data
Is every returned profile ready for outreach?
No. Check identity, employment recency, role relevance, contact verification, suppression, lawful purpose, and opt-out handling.
Does Wiza guarantee deliverability?
No. Address state, SPF, DKIM, DMARC, sender reputation, message relevance, and mailbox behavior all affect delivery.