Ask Hunter which email addresses it knows at a company, and who is saved.
Connect Hunter with an API key and Memtro reads the team's saved leads by name, company or list, with position, confidence, verification and sending status, plus lead lists, tags, email sequences and the account's credit balance. Domain Search finds the addresses at a company and spends credits. The hourly sync also writes newly saved leads into memory. When asked, and once an administrator has granted the action by name, it can save, update or permanently delete leads, manage tags and lists, build draft email sequences, and start one, which emails every recipient from your sender accounts and cannot be recalled.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Hunter tool, reads what it needs, and answers with the source cited.
These tools change something in Hunter. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Hunter for you. Each event can start a job, with the event as its input. Hunter signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Hunter is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Hunter + MemtroWhich email addresses does Hunter know at northwind.com?
How many Hunter credits are left this month?
Which of our saved leads have unverified emails?
Save Priya Sharma at Acme as a lead in the Q3 outreach list
Pause the Globex follow-up sequence
Before outreach to Northwind, a sales rep asks which addresses Hunter knows there. Memtro checks the balance first, then runs a Domain Search that spends 2 credits and returns 14 people with position, seniority and confidence, plus the company's email pattern.
Dan Fletcher hears that BigCo has signed and asks Memtro to stop the follow-up sequence they are in. Memtro pauses the active sequence in Hunter, so no further scheduled emails go out, and says the emails already sent cannot be recalled.
The teams that lean on Hunter most, a question each of them asks, and what they connect beside it.
A record in Hunter is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Capsule CRM
Copper
Freshsales
Dialpad
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapOpen hunter.io/api-keys and copy an existing key or generate a new one. It works on every Hunter plan, Free included
In Memtro open Connections → Hunter, paste the API key and connect
Domain searches spend Hunter credits, 1 per 10 addresses returned. Checking the account, reading leads and changing leads, tags and lists are free
Ask how many credits are left this month, which is free
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Hunter tools are the same everywhere.
Only when you ask, and only what it has been granted: save a new lead (refused when the email is already a lead); create a lead tag; attach an existing tag to a lead; update or delete a saved lead; remove a tag from a lead, or rename, recolour or delete a tag; create or delete a leads list; create a draft email sequence and add steps to it; add people to a sequence (on an active one Hunter may email them at once), or take them out; start a sequence (emails every recipient), pause, resume or archive it. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Hunter records into memory as entities.
API key. Open hunter.io/api-keys and copy an existing key or generate a new one. It works on every Hunter plan, Free included.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Hunter for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time