sales
Hunter CLI for CI
Use the Hunter CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
8 functions 7 read 1 write API key auth
Hunter CLI for CI
Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.
Use this shape when a pipeline needs to read or update an external service. The Hunter CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Hunter CLI for CI
kosmokrator integrations:configure hunter --set api_key="$HUNTER_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call hunter.hunter_domain_search '{"domain":"example_domain","limit":1,"offset":1,"type":"example_type"}' --jsonDiscovery Before Execution
Agents and scripts can inspect Hunter docs and schemas before choosing a function.
kosmo integrations:docs hunter --json
kosmo integrations:docs hunter.hunter_domain_search --json
kosmo integrations:schema hunter.hunter_domain_search --json
kosmo integrations:search "Hunter" --json
kosmo integrations:list --jsonUseful Hunter CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
hunter.hunter_domain_search | Read | domain, limit, offset, type | Search for professional email addresses associated with a domain. Returns email addresses found for the company, along with contact names, positions, and social profiles. Supports filtering by email type (personal or generic). |
hunter.hunter_email_finder | Read | domain, first_name, last_name | Find the most likely professional email address for a person based on their name and company domain. Returns the email with a confidence score and sources where the email was found. |
hunter.hunter_email_verifier | Read | Verify the deliverability of an email address. Checks whether the email is valid, the mailbox exists, and accepts mail. Returns a result status (deliverable, undeliverable, risky, or unknown) along with confidence scores and SMTP details. | |
hunter.hunter_email_count | Read | domain | Get the total number of email addresses Hunter.io has found for a domain. Returns counts broken down by email type (personal, generic) and department. This endpoint does not consume API credits. |
hunter.hunter_list_leads | Read | limit, offset | List leads stored in your Hunter.io account. Supports pagination with limit and offset parameters. Returns lead details including email, name, and associated lists. |
hunter.hunter_get_lead | Read | id | Retrieve detailed information about a single lead by its ID. Returns the lead's email address, name, company, and any associated lists or custom fields. |
hunter.hunter_create_lead | Write | email, first_name, last_name, list_id | Create a new lead in Hunter.io. Requires an email address. Optionally include first name, last name, and a list ID to add the lead to a specific lead list. Returns the created lead object with its ID. |
hunter.hunter_get_current_user | Read | none | Get information about the authenticated Hunter.io account, including the user's name, email, plan details, and API usage (requests made and remaining). Useful for verifying the API key works and checking usage limits. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.