Verify Catch-All Email
Better Enrich → Verify Catch-All Email
/v1/betterenrich-verify-catch-all-email{ "email": "[email protected]" }
{ "ok": true, "data": { "status": "valid" } }
Determines if a domain email address uses catch-all routing that accepts all emails.
Install
Add verify catch-all email 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__betterenrich-verify-catch-all-email
When to use this.
The "Verify Catch-All Email" action is designed to determine whether a specified domain email address employs catch-all routing, which allows it to accept emails sent to any address at that domain. This action requires a single input parameter: the email address (text) that needs verification. Upon execution, it returns a status (text) indicating whether the email address is configured as a catch-all. This functionality is particularly useful for businesses and marketers seeking to validate email addresses for lead generation, ensuring effective communication by identifying domains that accept all emails. Categorized under enrichment, this action enhances data quality and integrity, making it an essential tool for email verification processes.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Verify Catch-All Email
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
statusStatustext
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/betterenrich-verify-catch-all-email. Auth: x-api-key.
/v1/betterenrich-verify-catch-all-emailcurl -X POST 'https://v3-api.texau.com/api/v1/betterenrich-verify-catch-all-email' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"email":"[email protected]"}'
{ "ok": true, "data": { "status": "valid" } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
enrichment
Find LinkedIn URL by Name
Finds a LinkedIn profile URL using a person's full name and company name.
enrichment
Find Mobile Number by LinkedIn URL
Finds mobile phone numbers from a LinkedIn profile URL using multi-source verification.
enrichment
Check Email Service Provider
Identifies the email service provider for a given email address.
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 → verify catch-all email → 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 limit500 / min
- Per-day limit12,000 / day
- RetriesAutomatic w/ backoff
- ModeAsync
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 Better Enrich actions.
enrichment
Find LinkedIn URL by Name
Finds a LinkedIn profile URL using a person's full name and company name.
enrichment
Find Mobile Number by LinkedIn URL
Finds mobile phone numbers from a LinkedIn profile URL using multi-source verification.
enrichment
Check Email Service Provider
Identifies the email service provider for a given email address.
enrichment
Find Work Email by Name and Domain
Finds business email addresses using a person's full name and company domain.
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 Verify Catch-All Email in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.