Source & Enrich public data
for {{in house automation}}
Heads of Talent at 200–1,000 person US companies hiring recruiters
| Person | Title | Company | Location | Tenure | |
|---|---|---|---|---|---|
| Amara Okafor | Head of Talent Acquisition | Patagonia | Ventura, US | a.okafor@patagonia.com | 3 yr 2 mo |
| João Almeida | Head of People | Grupo Piracanjuba | Bela Vista, BR | j.almeida@piracanjuba.com.br | 5 yr 3 mo |
| Elena Vasquez | Senior Recruiting Manager | AI at Meta | Menlo Park, US | e.vasquez@ai.meta.com | 2 yr 0 mo |
One Engine → Full Coverage
Search, filter, resolve, enrich, push to a campaign, and watch replies land — without exporting a CSV or opening a second tab.
Straight into a campaign
Selected rows become a list, a sequence, or a CRM pipeline in one action. No export, no re-upload, no mapping step.
Filters that tell the truth
Every filter shows how much of the corpus actually has that field on file, so a sparse field never silently deletes your list.
Cost on the control that spends it
Reveal reads 1 cr before you click it. Batches quote a ceiling, never a flat total — nothing that fails is billed.
Why teams are integrating our API & MCP
Describe the list.
Get the list.
Natural language resolves to a real query against the index — not a keyword match. The count moves as you refine, and every filter shows its coverage before it silently removes anyone.
Benchmarks
Highest quality data
at every latency
Best-in-class accuracy for every search vertical, and across the benchmarks that actually stress a retrieval engine.
Accuracy (%)
Reverse lookup
Partial match
Live profile
Data nobody else has
The index is queryable as an API and as an MCP server, with endpoints the general-purpose data vendors don't expose — reverse lookup, partial-match resolution, and live profile fetches.
Exclusive Reverse-lookup a work or personal email to a person
Enriching accounts that sign up with a personal address, and filling in work history behind old CRM records.
Exclusive Resolve a person or company from partial information
A name and a company, a domain and a title — enough fragments to identify a record without an exact key.
Filter companies on attributes the big sales tools don't expose
Specialties, technology, headcount bands and hiring posture, combined in one query.
Search people more granularly than a recruiter seat allows
Title, seniority, tenure and skills together, with coverage shown per field.
Exclusive Let agents build prospect lists across every source at once
One MCP call fans out across the index, the waterfall and the signal scrapers, and returns rows.
Verify any email through the waterfall before you send
Validation runs the same providers as enrichment, so a verified address is verified the same way twice.
REQUEST curl https://api.datasource.io/v1/email-to-person \ --request POST \ --header 'Content-Type: application/json' \ --data '{ "apiKey": "YOUR_API_KEY", "email": "john@company.com" }' RESPONSE { "data": [ { "name": "John Smith", "headline": "Software Engineer at Tech Corp", "locality": "San Francisco, CA", "current_job": { "company_name": "Tech Corp", "title": "Software Engineer", "is_current": true, "start_date": "2022-01", "seniority": "Mid-Senior level" }, "provider": "waterfall:step-2", "credits_charged": 1 } ] }
The questions we'd ask
Where does the data come from?
Two places, and the difference matters. There is a licensed core index of people and company records that we hold and refresh on a schedule — that's what search runs against, and querying it costs nothing. On top sits a live waterfall across twelve providers, used only when you ask for something the index doesn't hold. Every enriched value keeps the provider that produced it.
How is this different from an enrichment tool like Clay?
Enrichment tools own no data of their own — they orchestrate providers you bring, and you build the table before you get an answer. We kept the good part: the waterfall, the provenance, the per-row control. What we add underneath is an index, so you can find the people in the first place, and a sequencer on top, so you don't hand off to a fourth tool to send.
How is this different from a database like Apollo?
A database gives you coverage and one fixed opinion about how each field gets resolved. When its answer is missing or wrong you have no second option and usually no way to see where the value came from. We run a multi-provider waterfall over our own index instead, bill per resolved row, and publish the coverage of every field before you filter on it.
Can I use my own sending domains?
Yes — connect existing mailboxes, or buy domains and mailboxes inside the app and have them warming the same day. Sending windows, throttles and warmup are configured per mailbox, because that's the level deliverability actually operates at.
Is the data compliant?
Records are business-contact data, sourced under licence, with suppression and deletion handled at the org level. Opt-outs propagate across lists, sequences and the CRM at once rather than per-tool.
Point it at your market and
see what comes back
Start free with 200 credits. Build an audience, resolve a few contacts, and watch the whole path work before you pay for anything.