Research notes · checked July 2026Installer documentation
AI agent prospecting research workspace
PROSPECTING, WITH A PAPER TRAIL

Turn a market thesis into a reviewable account list

Apollo.io brings company discovery and decision-maker research into your AI agent, so every filter, enrichment step, and outreach decision can be inspected before anyone sends.

Compare the workflow
npx -y @okki-global/okki-go-taroball
OPERATING MODEL

Seat workflow versus agent-native research

Use the dimensions below as evaluation questions, not as unsupported performance claims.

DecisionConventional seat workflowAgent-native research
Starting pointOpen a separate sales applicationDescribe the ICP inside your working agent
Research trailOften spread across tabs and exportsKeep criteria, results, and notes in one task
Send controlSequence rules vary by platformRequire human approval before outreach
Cost modelFrequently tied to seats or creditsInspect package and provider costs before use
RESEARCH SEQUENCE

Four checkpoints from hypothesis to handoff

01

Define the market

State firmographic boundaries, exclusion rules, and the buyer role worth finding.

02

Inspect evidence

Review company context, technographic clues, source notes, and data gaps.

03

Verify contacts

Treat email status and role relevance separately; unknown remains unknown.

04

Approve the handoff

Export only records a person has reviewed for targeting and regional policy.

CAPABILITIES

A research stack organized around decisions

F

Firmographic filtering

Build an ICP from industry, geography, scale, and operating context.

T

Technographic clues

Use technology signals as research inputs, never as certainty by themselves.

W

Waterfall enrichment

Separate provider coverage from provenance and cost implications.

V

Email verification

Record verification state without promising zero bounces or inbox placement.

R

Review gates

Keep targeting, message approval, and send decisions human-controlled.

A

Audit-ready output

Preserve the brief, applied filters, unresolved fields, and handoff notes.

INSTALL RUNBOOK

Copy is not install. Follow all four states.

  1. 1 · Copy

    Put the exact command on your clipboard

    npx -y @okki-global/okki-go-taroball

    Success signal: the command—not a prompt character—is copied.

  2. 2 · Run

    Execute it in a trusted terminal

    Review the package name and npm execution warning, then run it in the environment that hosts your agent.

  3. 3 · Configure

    Add only required credentials

    Keep provider keys in your runtime secret store. Do not paste secrets into prompts, logs, or shared transcripts.

  4. 4 · First result

    Start with a bounded research brief

    Ask for a small account set with explicit filters, provenance notes, and a human review checkpoint.

TRUST LEDGER

Questions to settle before production use

Data sources

Config-dependent. Document each connected provider, permitted purpose, and provenance field.

API keys

Verify locally. Store secrets outside prompts and rotate them under your own access policy.

Runtime behavior

Inspect before run. Review package behavior, network access, and runtime permissions.

Retention & deletion

Not assumed. Confirm logs, cached results, exports, and deletion procedures in your environment.

Review, then install