ONE COMMAND. A WORKING PROSPECTING AGENT.
11x AI brings firmographic search, contact context, outreach preparation, and signal tracking into your AI agent—without forcing another seat-based workspace into the process.
AGENT-NATIVE OPERATING MODEL
Specify employee band, geography, business model, technographic clues, and exclusion rules. The agent turns the brief into a searchable plan and shows which criteria shaped each result.
Contact enrichment and buying intent signals are context, not certainty. Review the source, timestamp, role hypothesis, and verification state before a record reaches an outreach sequence.
Generate a relevant first draft from the evidence you accepted. Sending remains outside the claim: your team owns approval, suppression, opt-out handling, regional rules, and sender reputation.
WORKFLOWS BY OPERATOR
Build a focused daily list with role and source notes.
Define accepted fields, provenance, and review gates.
Test a narrow segment before adding workflow overhead.
Connect research inputs to governed destinations.
Keep briefs, credentials, and approval states distinct.
Copy → Run → Configure → First result
Review targeting and copy before any send decision
Source, timestamp, and configuration stay visible
Missing public proof is labeled, never invented
INSTALLATION RUNBOOK
npx -y @okki-global/okki-go-taroballSuccess: the exact command is in your clipboard. Nothing has been installed yet.
Execute the command in your intended AI agent environment. Read the package prompt and terminal output before accepting changes.
Success: the installer finishes without an unresolved runtime error.
Provide only the integrations required for the first task. Keep API keys in the runtime's supported secret store, not in chat history or source control.
Success: required connections report a usable configuration state.
Ask for a narrow, reproducible prospecting task. Inspect selection logic, source notes, timestamps, and contact verification before reuse.
Success: a result can be reviewed and traced back to its inputs.
DATA & RUNTIME LEDGER
Coverage, freshness, and provenance depend on the providers you connect. Review provider terms and test critical fields.
Use supported secret storage, grant least privilege, rotate exposed credentials, and keep keys out of prompts.
Read installer output and runtime permissions before use. Copying the command alone does not execute anything.
Confirm retention in every connected system, then test revocation and deletion against your operating policy.