Developer docs
MyDataHub developer docs
Count, preview and quote UK B2B contacts for free, then order by REST, MCP or the app. One credit buys one complete UK record.
MyDataHub by Emailmovers is the UK B2B count engine. Counts, breakdowns, masked samples and quotes cost 0 credits and need no account. You pay only when you order records, at 1 credit per complete UK record, at the same price in the app, the REST API and the MCP server.
Choose your starting point
| You are | Start with | What you do |
|---|---|---|
| Using the app | Quickstart for people | Describe an audience, read the count and a masked sample, order |
| Writing code | Quickstart for developers | Count, quote and order with curl and TypeScript |
| Building or running an agent | Quickstart for agents | Connect Claude, ChatGPT or Cursor to the MCP server |
Using today's 13 MCP tools or RunExtract | Migration guide | Map every old call to its replacement |
The rules that never change
- Looking is free. The filter catalogue, title expansion, location resolution, counts, breakdowns, masked samples, machine quotes and plans cost 0 credits and need no account.
- One credit, one record. A credit buys one complete UK record. Duplicates, suppressed records, records you already hold and failed lookups cost 0.
- Quote, then confirm. A spend needs a machine
quote_idplus a person's confirmation or an agent key within its limits. A flag set by a model is never consent. See Spending safely. - One audience definition. Chips in the app, a brief compiled by an agent and a JSON document sent over REST all produce the same count, the same breakdown and the same id. See The audience definition.
- Counts replay. A count id is content addressed and re-runs exactly for 12 months on its pinned dataset version. See Versions and reproducibility.
What is behind the counts
On 26 September 2026 the database held 9,028,587 records at active companies. Of those, 1,660,190 had an email address, 1,605,275 had a named-person email and 1,277,443 of those were at Manager level or above. Counts for the same audience are identical in the app, the API and the MCP server.
Where things live
| Surface | Address | Status |
|---|---|---|
| App | https://mydatahub.emailmovers.com | Not yet live. Today's product is at https://app.mydatahub.uk |
| REST API | https://mydatahub.emailmovers.com/v1 | Not yet live |
| MCP server | https://mydatahub.emailmovers.com/mcp | Not yet live. Today https://mcp.mydatahub.uk serves 13 tools. It keeps serving today's product after launch, until the new server supports OAuth sign-in from the client, and then passes MCP through to it |
| OAuth 2.1 issuer | https://mydatahub.emailmovers.com/id | Not yet live. At launch it signs you in to the app; REST and MCP clients use an API key, and OAuth sign-in for them is planned for after launch |
| These docs | https://emailmovers.com/mydatahub/docs/ | Built, not yet published |
For agents reading this site
Every page has a Markdown twin at the same path with .md, such as /quickstart/developers.md. The index is llms.txt, and the guides, problem types and reference indexes are in one file at llms-full.txt. The OpenAPI 3.1 document is at /reference/openapi.json.
All guides
- Audience definition: the JSON document every count starts from.
- Counts and breakdowns: Total, New to you, Emailable, and what disclosure control does to small numbers.
- Samples: masked previews with why each record matches.
- Quotes and orders: machine quotes, orders, records and credits.
- Spending safely: the three layers that guard every spend.
- Authentication: API keys, agent keys and scopes, and OAuth 2.1, which signs you in to the app.
- Errors: every problem type and what to do next.
- Rate limits: limits by tier and the headers that report them.
- Webhooks: Standard Webhooks signing, retries and event types.
- Suppressions and objections: lists, checks before a send and database-wide objections.
- Compliance receipts: the signed receipt for every order and how to verify it.
- Versions and reproducibility: dated API versions, dataset versions and count ids.
- Changelog and deprecation policy: what changed and how long old things last.
- Reference: every REST operation and MCP tool, generated from the contracts.