Hunter (BYOK) — connector documentation
- MCP endpoint:
https://byok-hunter.connectorbay.com/mcp - REST API:
POST https://byok-hunter.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-hunter.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Hunter Hunter API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-hunter.connectorbay.com/health· Tool schemas:https://byok-hunter.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-hunter · agent@connectorbay.com
What Hunter (BYOK) is for
Hunter (BYOK) lets an AI assistant read your own Hunter data through the Hunter API with a key you supply (Hunter API key). Read-only: 8 tools (get_account, list_team_members, list_leads, get_lead, list_leads_lists, list_sequences, get_sequence_stats, list_sequence_recipients). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.hunter.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hunter. Hunter and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "How many Hunter credits do I have left?"
- "Who is on my Hunter team?"
- "Which leads at Stripe have I saved in Hunter?"
- "Show me Hunter lead 1"
- "What lead lists do I have in Hunter?"
- "Which of my Hunter email sequences are running?"
What it does
get_account: Show the Hunter account behind the key: owner name and email, plan, reset date and how many searches, verifications and credits are used and left. This call is free and does not use search or verification credits.list_team_members: List the members of your Hunter team with id, name and email. This call is free and does not use search or verification credits.list_leads: List leads saved in your Hunter account (newest first) with name, email, company, position, verification status and list. Only returns leads you already saved; it does not search for new ones. This call is free and does not use search or verification credits.get_lead: Get one saved lead by id with all its stored fields. This call is free and does not use search or verification credits.list_leads_lists: List your Hunter lead lists with id, name, lead count and type (static or dynamic). This call is free and does not use search or verification credits.list_sequences: List your Hunter email sequences with recipient count and whether each is started, paused or archived. This call is free and does not use search or verification credits.get_sequence_stats: Get delivery and engagement statistics of one email sequence: recipients, sent, delivered, opened, clicked, replied, bounced and the rates. This call is free and does not use search or verification credits.list_sequence_recipients: List the recipients of one email sequence with name, company and sending status (pending, sent, opened, replied, bounced ...). This call is free and does not use search or verification credits.
BYOK key
You bring your own Hunter Hunter API key (https://hunter.io/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.hunter.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://hunter.io/api-documentation/v2 (the API this connector calls, with a BYOK key)
Live from the Hunter API (api.hunter.io) with a BYOK key; documentation: https://hunter.io/api-documentation/v2. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hunter. Hunter and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Hunter account.
Built for: Worldwide. Languages: English.