BusinessMCP

People data API

Named business contacts with their work email and LinkedIn, from a store we build ourselves, with every opt-out honoured before a record leaves.

Get an API key — freeAPI reference
1,000 free credits every month · REST and MCP

What it’s for

Reach the right person

List the decision-makers at an account by seniority or department before you write to it.

Complete a lead

Turn a work email from a form into a name, title and LinkedIn profile.

Address a named contact

Get the work email for a person you already know by name, with how sure we are about it.

Endpoints

Each is a REST route and an MCP tool with the same name, input and price. Examples use the key from the BUSINESSMCP_API_KEY environment variable.

People search

Named decision-makers at a company, with work email and LinkedIn where known.

10 credits per item, only when a result is found

POST/api/hub/v1/people/search

  • domainstringRequired · max 253 chars
  • senioritystring[]Optional · 0–6 items
  • departmentstringOptional · max 40 chars
  • title_containsstringOptional · max 60 chars
  • limitintegerOptional

Example request

curl -X POST https://businessmcp.com/api/hub/v1/people/search \
  -H "Authorization: Bearer $BUSINESSMCP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"acme-logistics.com","seniority":["vp","director"],"limit":5}'

MCP name people_searchFull reference and response

Email finder

A named person's work email at a company, with how sure we are.

15 credits per call, only when a result is found

POST/api/hub/v1/people/email-finder

  • domainstringRequired · max 253 chars
  • first_namestringRequired · max 60 chars
  • last_namestringRequired · max 60 chars

Example request

curl -X POST https://businessmcp.com/api/hub/v1/people/email-finder \
  -H "Authorization: Bearer $BUSINESSMCP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"acme-logistics.com","first_name":"Jordan","last_name":"Rivera"}'

MCP name email_finderFull reference and response

Person enrichment

Name, title, employer and LinkedIn for a work email, or the reverse.

10 credits per call, only when a result is found

POST/api/hub/v1/people/enrich

  • emailstringOptional · email · max 320 chars
  • linkedin_urlstringOptional · max 300 chars

Example request

curl -X POST https://businessmcp.com/api/hub/v1/people/enrich \
  -H "Authorization: Bearer $BUSINESSMCP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"jordan.rivera@acme-logistics.com"}'

MCP name person_enrichFull reference and response

What it does not do

  • We never return people located in the EU, the EEA, the UK or Switzerland, people we place in California, Texas, Vermont and Oregon, or people we cannot place (in the United States, in a state). We place a US person by their employer's state when we do not know their own.
  • Anyone who opts out through our opt-out form is removed from our store within about a day and never returned again.
  • An address marked pattern was built from the company email format and has not been checked. Verify it before sending.
  • Every people call is logged against your account with the purpose you declared. Use for credit, employment, insurance or housing decisions is prohibited.

Frequently asked questions

Is this people data GDPR compliant?

We sidestep the question for the people it would apply to: the API never returns anyone we place in the EU, the EEA, the UK or Switzerland, and never returns someone we cannot place in a country at all.

Why are California, Texas, Vermont and Oregon excluded?

Those four states require data brokers to register. We do not sell records about people we place there, and we say so on our data-broker disclosure. For a US person we place them by their own stated location, or otherwise by their employer’s state; a US person we cannot place in any state is not returned.

What do I need before the first people call?

A card on file for your Data API account and acceptance of the people-data terms, where you declare what you will use the records for. Both are on the Billing page of the developer portal. Free credits never cover people calls.

How do opt-outs work?

Anyone can remove themselves through our opt-out form without an account. We delete them from our store within about a day and check every result against the opt-out list before it leaves, so an opted-out person is never returned again.

Is an email from email_finder verified?

Not always. An address from our store carries the status it was last checked at (valid, catch_all or unknown); an address built from the company’s email format is labelled pattern and has not been checked. Run a pattern address through email_verify, or your own verifier, before you send to it.

Related reading

Data-broker disclosureOpt out of our recordsHunter.io alternativeEmail finder vs email verification

Try it on your own data

The same key reaches every Data API tool. See the full price list before you spend a credit.

Get an API key — free
No card until you go past the free credits

More of the Data API

Company data API5 toolsViewIP to company API2 toolsViewWebsite checks API4 toolsViewEmail verification, MCP monitoring and lead check API8 toolsView

Back to the Data API overview.