Every API here is available over the APIs.io API and to AI agents over MCP.
openapi: 3.2.0
info:
title: BusinessMCP Hub Email API
version: 1.0.0
description: One BusinessMCP API key for company data, IP intelligence, website checks and MCP trust tools. Every call is prepaid and priced in US dollars, paid from the account balance, which is added in any whole-dollar amount from $10 to $5,000; a dollar paid is a dollar of balance and nothing is invoiced afterwards. Send an Idempotency-Key header to make a retry free. The same tools are available over MCP at https://businessmcp.com/api/hub/mcp.
servers:
- url: https://businessmcp.com/api/hub/v1
security:
- bearer: []
tags:
- name: Email
paths:
/tools/fp.company.email_pattern/call:
post:
operationId: call_fp_company_email_pattern
summary: Email pattern
description: 'Return the email address format a company uses (for example {first}.{last}), how confident we are in it, whether it was validated by a live mailbox check, whether the domain accepts mail (MX) and whether it is a catch-all domain that accepts any address. Company-level data only: no person is returned. Charged only when a pattern is known.
Pricing: $0.02 per call, charged only for results found.'
tags:
- Email
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/fp_company_email_pattern'
example:
domain: acme.com
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
domain: acme.com
found: true
pattern: '{first}.{last}'
confidence: 0.8
validated: true
example: jane.doe@acme.com
accepts_mail: true
catch_all: false
mail_checked_at: '2026-09-01T00:00:00Z'
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/companies/{domain}/email-pattern:
get:
operationId: fp_company_email_pattern
summary: Email pattern
description: 'Return the email address format a company uses (for example {first}.{last}), how confident we are in it, whether it was validated by a live mailbox check, whether the domain accepts mail (MX) and whether it is a catch-all domain that accepts any address. Company-level data only: no person is returned. Charged only when a pattern is known.
Pricing: $0.02 per call, charged only for results found.'
tags:
- Email
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
domain: acme.com
found: true
pattern: '{first}.{last}'
confidence: 0.8
validated: true
example: jane.doe@acme.com
accepts_mail: true
catch_all: false
mail_checked_at: '2026-09-01T00:00:00Z'
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
parameters:
- name: domain
in: path
required: true
schema:
type: string
/tools/fp.site.email_auth/call:
post:
operationId: call_fp_site_email_auth
summary: Email authentication check
description: 'Check a domain’s email authentication: MX, SPF, DMARC policy and DKIM on common selectors, each graded pass, warn, fail or unknown with the fix. A DNS lookup we could not complete is reported as unknown, never as fail.
Pricing: $0.02 per call.'
tags:
- Email
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/fp_site_email_auth'
example:
domain: acme.com
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
domain: acme.com
score: 3
checks:
- id: mx
label: MX records
status: pass
detail: Mail is routed via aspmx.l.google.com (5 records).
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/sites/{domain}/email-auth:
get:
operationId: fp_site_email_auth
summary: Email authentication check
description: 'Check a domain’s email authentication: MX, SPF, DMARC policy and DKIM on common selectors, each graded pass, warn, fail or unknown with the fix. A DNS lookup we could not complete is reported as unknown, never as fail.
Pricing: $0.02 per call.'
tags:
- Email
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
domain: acme.com
score: 3
checks:
- id: mx
label: MX records
status: pass
detail: Mail is routed via aspmx.l.google.com (5 records).
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
parameters:
- name: domain
in: path
required: true
schema:
type: string
/tools/fp.email.verify/call:
post:
operationId: call_fp_email_verify
summary: Email verify
description: 'Check whether an email address can receive mail before you send to it. First, what we already know about this exact address: whether real mail to it was delivered, replied to or hard-bounced on our platform recently, and whether our own data pipeline checked the mailbox in the last 180 days and the mail server accepted or rejected it. Then the domain: well-formed syntax, a live mail server (MX), whether the domain is catch-all, disposable or a free-mail provider, whether it is a shared role inbox (info@, sales@), and whether the local part fits the company address format we know, plus how mail in that format has fared. Returns a verdict of deliverable (a delivery or reply in the last 90 days, or a passed pipeline mailbox check in the last 180), undeliverable, risky, domain_ok or unknown with the reasons. When our records settle nothing, we then ask the domain’s mail server live, from our own verifier, whether it would accept this mailbox and whether it accepts a random one (no message is ever sent): accepted with the random one refused is deliverable, a permanent mailbox rejection is undeliverable, and a server that accepts every address is risky. Servers that greylist, block probes or answer slowly (Yahoo, AOL and iCloud never give a mailbox answer) leave the verdict at domain_ok, which then means the domain accepts mail but the mailbox could not be confirmed. The address is not stored.
Pricing: $0.005 per call.'
tags:
- Email
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/fp_email_verify'
example:
email: jane.doe@acme.com
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
email: jane.doe@acme.com
verdict: domain_ok
reasons:
- The domain accepts mail. The mailbox itself was not contacted.
checks:
syntax: true
mx:
- aspmx.l.google.com
catch_all: false
disposable: false
free_mail: false
role: false
fits_company_pattern: true
company_pattern: '{first}.{last}'
network:
evidence: null
window_days: 90
pattern:
delivered: 10-99
bounced: 1-9
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/emails/verify:
post:
operationId: fp_email_verify
summary: Email verify
description: 'Check whether an email address can receive mail before you send to it. First, what we already know about this exact address: whether real mail to it was delivered, replied to or hard-bounced on our platform recently, and whether our own data pipeline checked the mailbox in the last 180 days and the mail server accepted or rejected it. Then the domain: well-formed syntax, a live mail server (MX), whether the domain is catch-all, disposable or a free-mail provider, whether it is a shared role inbox (info@, sales@), and whether the local part fits the company address format we know, plus how mail in that format has fared. Returns a verdict of deliverable (a delivery or reply in the last 90 days, or a passed pipeline mailbox check in the last 180), undeliverable, risky, domain_ok or unknown with the reasons. When our records settle nothing, we then ask the domain’s mail server live, from our own verifier, whether it would accept this mailbox and whether it accepts a random one (no message is ever sent): accepted with the random one refused is deliverable, a permanent mailbox rejection is undeliverable, and a server that accepts every address is risky. Servers that greylist, block probes or answer slowly (Yahoo, AOL and iCloud never give a mailbox answer) leave the verdict at domain_ok, which then means the domain accepts mail but the mailbox could not be confirmed. The address is not stored.
Pricing: $0.005 per call.'
tags:
- Email
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
email: jane.doe@acme.com
verdict: domain_ok
reasons:
- The domain accepts mail. The mailbox itself was not contacted.
checks:
syntax: true
mx:
- aspmx.l.google.com
catch_all: false
disposable: false
free_mail: false
role: false
fits_company_pattern: true
company_pattern: '{first}.{last}'
network:
evidence: null
window_days: 90
pattern:
delivered: 10-99
bounced: 1-9
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/fp_email_verify'
example:
email: jane.doe@acme.com
/tools/fp.email.verify_bulk/call:
post:
operationId: call_fp_email_verify_bulk
summary: Bulk email verify
description: 'Check up to 50 email addresses in one call, with the same checks and verdicts as email_verify: our delivery records, MX, catch-all, disposable, free-mail and role checks, then a live mailbox check from our own verifier (no message is ever sent) for the addresses those records cannot settle. Returns one result per input address, in order, and a count per verdict. Mail servers are asked at most two connections at a time, so a list that is all one provider takes longer than a mixed one; an address the server did not answer in time keeps its records verdict. Charged per unique address. The addresses are not stored.
Pricing: $0.005 per item.'
tags:
- Email
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/fp_email_verify_bulk'
example:
emails:
- jane.doe@acme.com
- nobody@example.invalid
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
results:
- email: jane.doe@acme.com
verdict: deliverable
reasons:
- The mail server accepted this mailbox and refused a random one (live check, no message sent).
- email: nobody@example.invalid
verdict: undeliverable
reasons:
- The domain publishes no mail server.
counts:
deliverable: 1
undeliverable: 1
risky: 0
domain_ok: 0
unknown: 0
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/emails/verify/bulk:
post:
operationId: fp_email_verify_bulk
summary: Bulk email verify
description: 'Check up to 50 email addresses in one call, with the same checks and verdicts as email_verify: our delivery records, MX, catch-all, disposable, free-mail and role checks, then a live mailbox check from our own verifier (no message is ever sent) for the addresses those records cannot settle. Returns one result per input address, in order, and a count per verdict. Mail servers are asked at most two connections at a time, so a list that is all one provider takes longer than a mixed one; an address the server did not answer in time keeps its records verdict. Charged per unique address. The addresses are not stored.
Pricing: $0.005 per item.'
tags:
- Email
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
ok:
const: true
data: {}
meta:
$ref: '#/components/schemas/Meta'
required:
- ok
- data
- meta
example:
ok: true
data:
results:
- email: jane.doe@acme.com
verdict: deliverable
reasons:
- The mail server accepted this mailbox and refused a random one (live check, no message sent).
- email: nobody@example.invalid
verdict: undeliverable
reasons:
- The domain publishes no mail server.
counts:
deliverable: 1
undeliverable: 1
risky: 0
domain_ok: 0
unknown: 0
meta:
request_id: b1f0…
tool: example
cost_usd: $0.02
replayed: false
'400':
description: Invalid input (not charged)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Missing or invalid API key
'402':
description: Balance too low, or a key spend limit reached
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited
'503':
description: Upstream or billing unavailable (refunded)
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/fp_email_verify_bulk'
example:
emails:
- jane.doe@acme.com
- nobody@example.invalid
components:
schemas:
fp_email_verify:
type: object
properties:
email:
type: string
minLength: 3
maxLength: 320
required:
- email
additionalProperties: false
fp_email_verify_bulk:
type: object
properties:
emails:
minItems: 1
maxItems: 50
type: array
items:
type: string
minLength: 3
maxLength: 320
required:
- emails
additionalProperties: false
Error:
type: object
properties:
ok:
const: false
error:
type: object
properties:
code:
type: string
enum:
- not_permitted
- quota_exceeded
- plan_required
- not_found
- invalid_input
- upstream_failed
- backend_unavailable
- unavailable
- internal
message:
type: string
hint:
type: string
retryable:
type: boolean
upgrade_url:
type: string
details:
type: object
required:
- code
- message
- retryable
required:
- ok
- error
fp_site_email_auth:
type: object
properties:
domain:
type: string
minLength: 3
maxLength: 253
required:
- domain
additionalProperties: false
Meta:
type: object
properties:
request_id:
type: string
tool:
type: string
provider:
type: string
enum:
- first_party
- vendor
- publisher
trust_tier:
type: string
cost_usd:
type: string
description: What this call cost, e.g. "$0.02".
trial_usd:
type: string
description: The part of the cost paid from promotional balance (always $0 for accounts opened after 2026-10-21).
paid_usd:
type: string
description: The part of the cost the purchased balance paid.
replayed:
type: boolean
balance_usd:
type: string
description: Purchased balance left after the call.
trial_left_usd:
type: string
description: Promotional balance left after the call, when any.
required:
- request_id
- tool
- cost_usd
- replayed
fp_company_email_pattern:
type: object
properties:
domain:
type: string
minLength: 3
maxLength: 253
required:
- domain
additionalProperties: false
securitySchemes:
bearer:
type: http
scheme: bearer
description: A BusinessMCP API key (mcph_…).