Before a first call
Dan Fletcher, account executive at Acme Ltd, asked who the person behind a new inbound email was. Memtro looked her up in People Data Labs and returned her title, level and employer, spending one credit for the match.
Who is this person, where do they work, and what does their company look like?
People Data Labs connects Memtro to PDL's person and company datasets. It looks up one person by email, social profile or name and employer, or one company by name, website or ticker, and searches both datasets with SQL. People come back as work identity only: name, title, level, employer, industry and country, never contact details, addresses, birth dates, social profiles or history. It reads and nothing else. Every lookup except autocomplete spends your PDL credits, so Memtro makes one only when asked, one person or company at a time.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right People Data Labs tool, reads what it needs, and answers with the source cited.
Once People Data Labs 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 does People Data Labs have on the company at northwind.com?
Who is priya@bigco.com and what is her role?
Which UK software companies with more than 50 employees are in PDL?
How much funding has BigCo raised, and at what stage?
What job titles does PDL use that start with head of?
Dan Fletcher, account executive at Acme Ltd, asked who the person behind a new inbound email was. Memtro looked her up in People Data Labs and returned her title, level and employer, spending one credit for the match.
Sarah Chen, head of sales at Northwind, asked how big BigCo was and how much it had raised. Memtro looked up the company and gave its employee count, founded year, headquarters, funding raised and latest stage.
The teams that lean on People Data Labs most, a question each of them asks, and what they connect beside it.
A record in People Data Labs 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.
In People Data Labs, open dashboard.peopledatalabs.com → Account → API Keys.
Choose Create New Key, name it Memtro and copy the key. Every enrichment, search and identify call spends your PDL credits.
In Memtro, open Connections → People Data Labs and paste it into API key.
Ask your first question: what does People Data Labs have on the company at northwind.com?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The People Data Labs tools are the same everywhere.
Not yet. Today every People Data Labs tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
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. In People Data Labs, open dashboard.peopledatalabs.com → Account → API Keys.
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