Get started

Hunter for AI agents

Hunter finds and verifies professional email addresses tied to a domain, helping sales and recruiting teams build accurate contact lists. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect HunterSee the 37 actions ↓
EmailAPI keyMCP + RESThunter.io
AUDIT LOG · HUNTERPOLICY: acme-support
09:41:07 · claude · u_8f2read
hunter.list_leads
List Leads✓ allowed · 212ms
09:41:08 · claude · u_8f2read
hunter.get_lead
Get Lead✓ allowed · 164ms
09:41:09 · claude · u_8f2write
hunter.create_lead
Create Lead✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
hunter.delete_lead
Delete Lead✕ blocked · policy: deny
EVERY HUNTER CALL, ON THE RECORD
01 · USE CASES

What agents do in Hunter.

01

Find an email by name and domain

Find a person's likely work email using their name and company domain before outreach.

02

Verify an email address

Verify a collected email address's deliverability before adding it to a campaign.

03

Search a domain for contacts

Search a company domain for known email patterns to build a list of contacts.

02 · ACTIONS

37 Hunter actions, graded by risk.

Every Hunter action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

18

Look things up. Allowed by default.

  • hunter.get_lead
    Get Lead
  • hunter.get_usage
    Get Usage
  • hunter.list_leads
    List Leads
  • hunter.get_webhook
    Get Webhook
  • hunter.get_sequence
    Get Sequence
  • hunter.list_webhooks
    List Webhooks
  • hunter.get_leads_list
    Get Leads List
  • hunter.list_campaigns
    List Campaigns
  • hunter.list_sequences
    List Sequences
  • hunter.list_leads_lists
    List Leads Lists
  • hunter.list_team_members
    List Team Members
  • hunter.list_usage_history
    List Usage History
  • hunter.list_email_accounts
    List Email Accounts
  • hunter.get_custom_attribute
    Get Custom Attribute
  • hunter.list_custom_attributes
    List Custom Attributes
  • hunter.get_email_account_usage
    Get Email Account Usage
+ 2 MORE

write

16

Create and change things. Allow, or ask the user first.

  • hunter.create_lead
    Create Lead
  • hunter.update_lead
    Update Lead
  • hunter.create_leads_list
    Create Leads List
  • hunter.update_leads_list
    Update Leads List
  • hunter.create_custom_attribute
    Create custom lead attribute
  • hunter.update_custom_attribute
    Update Custom Attribute
  • hunter.email_count
    Email Count
  • hunter.upsert_lead
    Upsert Lead
  • hunter.email_finder
    Email Finder
  • hunter.domain_search
    Domain Search
  • hunter.email_verifier
    Email Verifier
  • hunter.people_enrichment
    People Enrichment
  • hunter.company_enrichment
    Company Enrichment
  • hunter.discover_companies
    Discover Companies
  • hunter.account_information
    Account Information
  • hunter.combined_enrichment
    Combined Enrichment

destructive

3

Delete, cancel or archive. Ask first, or deny outright.

  • hunter.delete_lead
    Delete Lead
  • hunter.delete_leads_list
    Delete Leads List
  • hunter.delete_custom_attribute
    Delete Custom Attribute
03 · HOW IT WORKS

Hunter in three steps.

  1. 01Your users connect HunterThey add their Hunter api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Lead” can wait for the user, and “delete Lead” can be denied outright.
  3. 03Any agent can actYour agent calls Hunter through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('hunter', {
  read: 'allow',
  write: 'ask',        // create_lead
  destructive: 'deny',  // delete_lead
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Hunter connects.

Users add their Hunter api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Hunter connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Hunter from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More email apps.

Gmail62 actionsOutlook306 actionsSendGrid364 actionsMixmax94 actionsElastic Email91 actionsResend66 actionsLettr60 actionsPostmark46 actions
ALL EMAIL APPS →
07 · FAQ

Hunter and Arc0, answered.

Q01

Can I use Hunter with Claude, ChatGPT or Cursor?

Yes. Connect Hunter to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Hunter actions you allow.

Q02

How do users connect Hunter?

Users add their Hunter api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Hunter actions can my agent take?

37 in total: 18 read, 16 write and 3 destructive, such as “create Lead”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Hunter?

Yes. Actions like “delete Lead” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Hunter too?

Yes. The same Hunter connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Hunter into your agent.

Your users connect Hunter once, under your brand. Your agent gets 37 actions behind your policies, with every call on the record.

Connect HunterBrowse all apps →

Free to build · MCP + REST · Audit log on every plan