Install

One command between your sales task and a testable first result

Copy the exact package command, inspect what it will run, then configure a narrow business-email research task inside your existing AI agent. Copying does not install anything; execution begins only when you paste and run the command in a compatible terminal.

npx -y @okki-global/okki-go-taroball
GetProspect installer shown beside an AI agent task

Readiness dashboard

Check the environment before the first run

01

Runtime

Use an environment that can invoke npx and review the package identity presented by the registry. Runtime version support is not asserted on this page; confirm it against the current package metadata before production use.

02

Permissions

Start in an isolated workspace with the least filesystem and network access needed for the test. Inspect requested actions rather than assuming that a copied command is harmless or that installation is already complete.

03

Credentials

Store any provider keys in your agent runtime's secret facility. Never paste credentials into prompts, templates, screenshots, shell history, or exported prospect records, and use narrow scopes where the provider supports them.

04

Test scope

Begin with one company, one role, and a small labeled sample. Keep external sending disabled while you evaluate provenance, checked time, syntax, domain, mailbox uncertainty, suppression, and reviewer effort.

Run references

Four notes worth opening before production

The fastest setup is still an auditable setup. Treat these references as verification prompts for your own environment, not as claims that every runtime or data provider behaves identically.

Package identity

Confirm the package name, displayed version, maintainer information, registry source, update path, and uninstall instructions at the time you run it.

Open run sequence

Data connectors

Document which source supplies a candidate address, which source verifies it, the retrieval time, rate limits, and how unknown or catch-all states are preserved.

Review capabilities

Outbound controls

Keep human approval between research and action. Technical verification does not establish relevance, lawful basis, consent, deliverability, or inbox placement.

See operating examples

Removal and retention

Uninstalling a package does not remove records copied to logs, local files, CRM, engagement tools, or provider systems. Map and test each deletion path.

Read privacy notes

Runbook

Move through four observable states

  1. Copy.

    The button copies only npx -y @okki-global/okki-go-taroball, without a prompt character or hidden argument. Nothing executes at this state.

  2. Run.

    Paste the command into the reviewed terminal. Observe package resolution, requested access, network activity, console messages, and any files created in the test workspace.

  3. Configure.

    Add approved credentials through the runtime's secret store, select permitted sources and destinations, and define a human review gate before export or outreach.

  4. Verify the first result.

    Ask for a single role at a known B2B company. Check source provenance, timestamp, inferred-versus-observed status, uncertainty, and whether the record can be corrected, suppressed, and deleted.

Copy the installer when your test workspace is ready

The button copies the command. You decide where and when it runs.

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