Tool
ContactCTL for Gemini CLI
Gemini CLI runs shell commands through its tooling; ContactCTL is a single binary that answers contact questions in one command each. Add a section to GEMINI.md and the pairing is done.
01 — The problem
Terminal agents deserve terminal tools
Gemini CLI lives in the terminal, but most contact-data products do not — they assume a human with a mouse. Every dashboard hop is a place where an autonomous run stops and waits for you.
ContactCTL keeps the loop closed. The agent shells out to ctc, gets deterministic JSON back, and branches on exit codes. Verification, enrichment, reverse lookup, scoped search, and lookalikes are all one-line commands with credits reported on every output.
There is nothing to configure beyond auth: no server to run, no schema to register, no tokens consumed until the tool is actually used.
02 — The workflow
How it runs
Teach it in GEMINI.md
The context file is the integration point. Keep it short; the CLI documents itself.
## Contact data (contactctl) The `ctc` CLI handles B2B contact work — run it via the shell tool. Verbs: find, verify, whois, phone, search, lookalike. All support --json; none prompt interactively. Before first use in a session, run `ctc instructions`. Preview any spend with --estimate. Cap batches with --max-cost. A failed lookup (exit 2) costs nothing.
A one-question task
“Who runs marketing at acme.com, and can I email them?” — three commands, all shell-native.
03 — Commands and credits
What this workflow uses
Every command reports its credit cost in the output. Preview any spend with --estimate at zero cost.
| Command | Purpose | Credits |
|---|---|---|
| ctc search people --domain D --titles T | Find the right person first | 0.25 credits per search |
| ctc find <name> <domain> --json | Resolve the work email | 1 credit per result found |
| ctc verify <email> | Confirm deliverability | 0.02 credits per verification |
Full datasheet: credit costs in the docs · plan pricing on /pricing