INSTALLATION DESK

Review the 6sense runtime before connecting data.

This page is a practical installation reference, not a sales form. Start with the command, inspect what runs, and keep provider access deliberately narrow.

Terminal installation checklist and secret management diagram

CONTACT INFORMATION

Documentation-first support routes.

No inquiry form is required to install. Use the public channels below for documentation, package review, and issue reporting; never include API keys, contact records, or customer data in a public message.

Package and installation

Run the command from a supported agent environment and review the terminal output. For defects, prepare the runtime version, reproducible steps, and sanitized logs.

Open the install checklist

Security questions

Document the package version, requested permissions, connected provider, data path, retention behavior, and revocation procedure before internal approval.

Read the privacy framework

Operating hours

Self-service documentation is available continuously. Public issue response timing is not guaranteed; do not treat an unconfirmed message as an incident-response commitment.

Review research notes

BEFORE YOU RUN

Four checks for a controlled installation.

  1. Environment: confirm the runtime and package policy used by your organization. Record the runtime version so a failed installation can be reproduced.
  2. Package: review the package identity, requested actions, displayed version, and network behavior. Do not assume a copied command or a clean terminal exit proves the first research task is correctly configured.
  3. Credentials: use scoped keys and the runtime's secret store; do not paste secrets into prompts. Document rotation and revocation before a production connection is approved.
  4. Test: use synthetic or approved records until data behavior and deletion are understood. Validate firmographic filtering, technographic data, provider provenance, API rate limits, and export behavior independently.

The first controlled test should include known-fit, known-misfit, and ambiguous accounts. Compare inclusion reasons, missing evidence, role inference, and contact enrichment against a reference decision made before the run. This separates workflow quality from confirmation bias.

Exact commandnpx -y @okki-global/okki-go-taroball

Copying is not installation. Run, configure, and verify a first result as separate steps.