Identify Email Type (Utility)
Texau → Identify Email Type (Utility)
/v1/texau-identify-email-type{ "email": "[email protected]" }
{ "ok": true, "data": { "email_address": "[email protected]", "username": "sample", "domain": "https://acme.com", "email_provider": "[email protected]", "guessed_name": "sample", "is_gmail": true, "is_hotmail": true, "is_i_cloud": true, "is_likely_company_email": "[email protected]", "is_likely_education_email": "[email protected]", "is_likely_personal_email": "[email protected]", "is_proton_mail": true, "is_yahoo": true, "is_yandex": true } }
Classifies an email address as personal, business, educational, or freemail and extracts the provider domain.
Install
Add identify email type (utility) to your MCP client.
Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__texau-identify-email-type
When to use this.
The "Identify Email Type" action is a powerful utility designed to classify email addresses into categories such as personal, business, educational, or freemail, while also extracting the provider domain. It takes a single input parameter, the email address (text), which is analyzed to determine its type. The action outputs a range of data fields, including the email address (email), username (id), domain (companyDomain), email provider (companyName), and various boolean indicators that specify if the email belongs to popular providers like Gmail, Hotmail, iCloud, ProtonMail, Yahoo, or Yandex. Additionally, it assesses whether the email is likely a company or education email. This action is particularly useful for data enrichment in customer relationship management (CRM) systems, marketing automation, and user verification processes, enabling businesses to enhance their user profiles and tailor communications effectively.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Identify Email Type (Utility)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
email_addressEmail AddressnullabletextusernameUsernamenullabletextdomainDomaintextemail_providerEmail Providernullabletextguessed_nameGuessed Namenullabletextis_gmailIs Gmailnullablebooleanis_hotmailIs Hotmailnullablebooleanis_i_cloudIs I Cloudnullablebooleanis_likely_company_emailIs Likely Company Emailnullablebooleanis_likely_education_emailIs Likely Education Emailnullablebooleanis_likely_personal_emailIs Likely Personal Emailnullablebooleanis_proton_mailIs Proton Mailnullablebooleanis_yahooIs Yahoonullablebooleanis_yandexIs Yandexnullableboolean
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/texau-identify-email-type. Auth: x-api-key.
/v1/texau-identify-email-typecurl -X POST 'https://v3-api.texau.com/api/v1/texau-identify-email-type' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"email":"[email protected]"}'
{ "ok": true, "data": { "email_address": "[email protected]", "username": "sample", "domain": "https://acme.com", "email_provider": "[email protected]", "guessed_name": "sample", "is_gmail": true, "is_hotmail": true, "is_i_cloud": true, "is_likely_company_email": "[email protected]", "is_likely_education_email": "[email protected]", "is_likely_personal_email": "[email protected]", "is_proton_mail": true, "is_yahoo": true, "is_yandex": true } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
enrichment
Remove Extra Whitespace (Utility)
Cleans up text by removing extra spaces, tabs, and newlines while preserving single spaces.
enrichment
Find URL Redirect Destination (Utility)
Resolves a URL to its final destination and returns the full redirect chain with HTTP status codes.
enrichment
Format Date and Time (Utility)
Converts a date-time string to UTC timezone and extracts individual date and time components.
Output
Results land in a TexAu table.
Sample rows below.
Real result preview coming soon.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
Workflow
A real example.
Trigger → identify email type (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
Reliability
Rate limits & reliability.
- Per-minute limit1000 / min
- Per-day limit1,000,000 / day
- RetriesAutomatic w/ backoff
- ModeSync
Errors
HTTP status codes.
What each response means and what to do about it.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
Related
More Texau actions.
enrichment
Remove Extra Whitespace (Utility)
Cleans up text by removing extra spaces, tabs, and newlines while preserving single spaces.
enrichment
Find URL Redirect Destination (Utility)
Resolves a URL to its final destination and returns the full redirect chain with HTTP status codes.
enrichment
Format Date and Time (Utility)
Converts a date-time string to UTC timezone and extracts individual date and time components.
enrichment
Normalize Phone Number (Utility)
Normalizes and validates a phone number to E.164, national, and RFC3966 formats with country metadata.
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__texau-...` 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 Identify Email Type (Utility) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.