Betterenrich logo

Check Email Service Provider

Better Enrich → Check Email Service Provider

POST/v1/betterenrich-check-esp
texau__betterenrich-check-espenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/betterenrich-check-esp
{
  "website_or_email": "[email protected]"
}
200 Accepted
{
  "ok": true,
  "data": {
    "esp": "sample",
    "message": "sample"
  }
}

Identifies the email service provider for a given email address.

Install

Add check email service provider to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__betterenrich-check-esp

When to use this.

The "Check Email Service Provider" action, also known as betterenrich-check-esp, is designed to identify the Email Service Provider (ESP) associated with a given email address, such as Gmail, Outlook, or Yahoo. This action requires a single input parameter, websiteOrEmail, which is a text field representing the email address to be analyzed. Upon execution, the action returns two output fields: esp, which indicates the identified Email Service Provider, and message, providing additional context or information regarding the result. This action falls under the enrichment category and is particularly useful for businesses and developers looking to enhance their data quality, improve email marketing strategies, or validate user registrations by accurately determining the ESP for email addresses. By leveraging this functionality, organizations can tailor their communications and ensure better deliverability rates.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Check Email Service Provider

Try it

Email address to check ESP for

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • esp
    Esp
    text
  • message
    Message
    text

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/betterenrich-check-esp. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/betterenrich-check-esp
curl -X POST 'https://v3-api.texau.com/api/v1/betterenrich-check-esp' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"website_or_email":"[email protected]"}'
200 Accepted
{
  "ok": true,
  "data": {
    "esp": "sample",
    "message": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Check Email Service Provider→Verify Catch-All Email→Find LinkedIn URL by Name

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → check email service provider → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Check Email Service ProviderBetter Enrich action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit500 / min
  • Per-day limit12,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Standard tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Better Enrich actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__better enrich-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Check Email Service Provider in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs