Reaching the buyer
An account executive asks for the work email of Priya Nair at Northwind. Memtro finds her in Lusha, reports the credits that search charged, reveals her work email when asked, and says how many credits the reveal cost.
Ask Lusha for the work email of a named contact at a company.
Connect Lusha with an API key and Memtro looks up people and companies in Lusha's database, with title, seniority, company, industry, country and size, reveals a person's work email or, when asked, phone, and reads full company profiles. Every search and reveal spends Lusha credits, and every answer says how many. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can create, share, archive or permanently delete Lusha tables, add or remove rows and columns, and run a column's enrichment, which spends credits per row.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Lusha tool, reads what it needs, and answers with the source cited.
These tools change something in Lusha. 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.
Once Lusha 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.
What is the work email for Priya Nair at Northwind?
How many Lusha credits do we have left this cycle?
How big is Brightwave Ltd, and what industry is it in?
Who is head of finance at BigCo?
Make a shared Lusha table of the five finance leads we found today
An account executive asks for the work email of Priya Nair at Northwind. Memtro finds her in Lusha, reports the credits that search charged, reveals her work email when asked, and says how many credits the reveal cost.
Laura Bennett asks Memtro to put the finance leads found at Globex, Acme and BigCo into a table the sales team can see. Memtro creates a shared contacts table owned by Laura in Lusha and adds the five contacts, which costs no credits, and reports which were added.
The teams that lean on Lusha most, a question each of them asks, and what they connect beside it.
A record in Lusha 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.
Lusha does not say which plans include API access. The key is made by an admin, or a manager with API access
In dashboard.lusha.com open API → Manage API keys and copy a key
In Memtro open Connections → Lusha, paste the API key and connect. Searches, reveals and some table actions spend Lusha credits, and checking usage is free
Ask how many Lusha credits are left this cycle
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Lusha tools are the same everywhere.
Only when you ask, and only what it has been granted: create a Lusha contacts or companies table, owned by a named Lusha user; rename, share, archive or restore a table; delete a table and all its data (permanent); add contacts to a table, or companies (spends credits per new company), or remove rows; add enrichment columns to a table (enrichment starts on every row) or remove one; run a table column's enrichment on all, missing or named rows (spends credits per row). 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.
API key. Lusha does not say which plans include API access. The key is made by an admin, or a manager with API access.
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