REST65+ enrichment endpointsMCP-native

The enrichment API behind Claude + TexAu MCP.

65+ enrichment endpoints — waterfall email and phone, profile and company enrichment, web scraping, AI Enrich. The same key powers the MCP server most teams install in Claude or Cursor first. Bring your own UI; we handle the data.

Install MCP in Claude →Get an API key Read the docs →

Base URL https://v3-api.texau.com/api/v1. REST auth via x-api-key. The Claude desktop connector authenticates via OAuth — no API key required on that path. MCP server at https://mcp.texau.com/mcp. Signup at enrich.texau.com — separate account from the Platform.

requestPOST

POST /v1/email_finding_waterfall
x-api-key: $TEXAU_KEY
 
{
  "first_name": "Sarah",
  "last_name": "Chen",
  "domain": "acme.com"
}

response200 OK

{
  "success": true,
  "email": "[email protected]",
  "provider": "hunter",
  "credits_charged": 1
}

65+ enrichment endpoints5 waterfalls · 13 async actions100,000 calls / month / endpointAuth: x-api-key · Claude via OAuth

Stop maintaining five integrations to do one job.

Every team that builds enrichment into their product hits the same architecture problem. You wire Hunter for emails, Apollo for company data, Clearbit for tech stack, NeverBounce for verification, then HubSpot or Salesforce for the write-back. Five auth schemes. Five rate limits. Five error contracts. Five invoices.

Before

Five integrations

5 vendor relationships
5 invoices
Custom fallback code per pair
No MCP layer
Annual contract negotiations

After

One API

1 vendor, 1 invoice, monthly
One auth header for REST and MCP
Internal waterfall handles fallbacks
200+ actions, ready-to-run
Monthly billing, no annual commit

Browse 200+ actions, six categories.

Profile + company

Enrichment

POST /enrich_profile and /enrich_company return LinkedIn profile and company data — headline, summary, industry, location, headcount, follower count. Bulk variants for batches up to 100.

5 endpoints

Waterfall enrichment

One call hits 10+ providers under the hood. Returns a double-verified email, phone, person, or company record plus the provider that won. Stop-on-first-success. Free retries on hard fails.

Find + verify + bulk

Email finding & verification

Standalone email-finder, deliverability verification, and inquiry endpoints for async batch jobs. SMTP-grade verification with risk and catch-all flags.

People · posts · profiles

Search

Search LinkedIn people, posts, and lead lists by title, company, location, keywords. Same engine that powers TexAu Tables prospecting.

Page · meta · pixels · stack

Web scraping

Extract page content, JSON-LD, meta tags, tracking pixels, social links, tech stack, emails on page, and full sitemaps. Useful for intent signals and account research.

Prompt-driven

AI Enrich

Pass a prompt + the row data; get back personalized output per record. The same AI Column that powers TexAu Tables, exposed as an API for any pipeline that needs row-level reasoning.

Browse the full action catalog →

Make your first call in two minutes.

Drop your API key into the x-api-key header. POST a name + domain to the email-finding waterfall. Get a double-verified email back, plus the provider that won. The shape below matches the OpenAPI spec — no editing required.

curl -X POST https://v3-api.texau.com/api/v1/email_finding_waterfall \
  -H "x-api-key: $TEXAU_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "first_name": "Sarah",
    "last_name": "Chen",
    "domain": "acme.com"
  }'

Successful calls (2xx) are billed. Failed calls — 4xx and 5xx — are not. Hard fails on waterfall endpoints return billed: false with the quota refunded automatically.

How does one API call hit ten enrichment providers?

Five waterfall endpoints — email finding, email verification, phone finding, person enrichment, company enrichment. Behind each one, ten-plus providers are called in priority order, stop-on-first-success. The response tells you which provider returned the value and how long every attempt took. There is no provider list to configure and no order to manage.

POST /email_finding_waterfall

Find email by name + domain. Stops on first verified hit.

POST /email_verify_waterfall

Confirm deliverability across providers; returns confidence and status.

POST /phone_finding_waterfall

Find direct dial by LinkedIn URL. Cascades through phone-data providers.

POST /person_enrich_waterfall

Merge person profile data from multiple enrichment providers.

POST /company_enrich_waterfall

Merge company data — firmographics, headcount, tech signals — across providers.

Inside the response: success, result, provider (the one that won), providers_tried, and an execution_log with per-provider status and latency. Audit-friendly out of the box.

POST /email_finding_waterfallfirst_name=John · last_name=Doe · domain=acme.com

PR
Provider Ano result
no record
180ms
PR
Provider Bthrottled
rate-limited; auto-skipped
40ms
PR
Provider Cfound
verified · returned to caller
342ms

Predictable status codes. Predictable error bodies.

Every endpoint speaks the same nine status codes and returns JSON on every error. Quota errors include the limit and your current count so retry logic stays trivial.

Code	Meaning	What it tells you
200	OK	Successful response. Body shape varies by endpoint.
400	Bad Request	Missing or invalid input — check the field listed in the body.
401	Unauthorized	Missing `x-api-key` header.
403	Forbidden	Invalid API key, or key lacks permission for this endpoint.
404	Not Found	Resource not found (e.g. profile URL did not resolve).
429	Too Many Requests	Per-minute, per-day, or monthly quota exceeded. Body contains `limit` and `current`.
500	Internal Server Error	We logged it; safe to retry after a short backoff.
502	Bad Gateway	Upstream provider error (waterfall endpoints absorb most of these).
504	Gateway Timeout	Upstream provider exceeded our timeout. Retry idempotent.

429 response · real shape

{
  "error": "Monthly quota exceeded",
  "api": "email_finding_waterfall",
  "limit": 100000,
  "current": 100000
}

5xx responses are rare and logged on our side. Waterfall endpoints absorb most upstream 5xx errors before they reach you and refund the credit on hard fails.

Run it in production.

Rate limits

100,000 calls per endpoint per month. Per-minute limits run 30–3,000 depending on the action; per-day limits 800–1,000,000. Hit the ceiling, get a 429 with `limit` and `current` in the body.

Async jobs

13 endpoints run async. POST returns an `executionId`; poll the matching `_inquiry` endpoint or subscribe to a webhook. Useful for bulk enrichment and large LinkedIn searches.

Webhooks

Subscribe to job-complete events and credit thresholds. Signed payloads. Retry-with-backoff. Replay any delivery from the dashboard.

Sandbox

Every account ships with a sandbox key against test data. Build and test without consuming production credits.

Per-client API keys

Issue scoped sub-keys per client workspace. Bill clients separately, revoke independently, audit per-key usage. Built for agencies running 10+ workspaces on one TexAu account.

Every API key is also an MCP server.

The MCP server is a thin protocol adapter over the same actions your code already calls. Same auth, same credits, same rate limits. If you have an API key, you have an MCP server.

claude mcp add --transport http texau \
  https://mcp.texau.com/mcp \
  --header "x-api-key: $TEXAU_KEY"

Your platform's enrichment becomes your agent's first-class tool — including the AI Enrich action, which gives an agent prompt-driven, row-aware reasoning over whatever data the agent already has.

See the MCP catalog →

API pricing

Pick a tier. Ship today. Switch any time.

Start with 50 free credits on signup. Then buy prepaid bundles based on your volume. Every bundle ships with all 200+ actions, the MCP server, and the same waterfall engine.

5,000 Credits

Best for teams moving from trial traffic to regular API use.

$100$0.020 / credit

Buy 5,000 credits →

Same base per-credit rate
All 200+ actions · MCP included
REST API + webhooks
Standard rate limits
No monthly commitment

Recommended

25,000 Credits

Save 10% at volume.

$450$0.018 / credit

Buy 25,000 credits →

10% discount vs base rate
All 200+ actions · MCP included
REST API + webhooks
Higher throughput headroom
No monthly commitment

50,000 Credits

Save 20% at volume.

$800$0.016 / credit

Buy 50,000 credits →

20% discount vs base rate
All 200+ actions · MCP included
REST API + webhooks
Priority support routing
No monthly commitment

Need 500,000+ credits? Contact sales for custom pricing, dedicated support, and volume discounts.

Contact Sales

Prices shown are the public pay-as-you-go and bundle ladder. Final dollar amounts are confirmed at checkout. Failed lookups on waterfall endpoints return billed: false — your credit is refunded automatically. See full plan comparison →

Built to ship through procurement.

Infrastructure

TLS 1.2+ in transit, AES-256 at rest
99.9% uptime target (status.texau.com)
API key rotation, action-level scopes, IP allowlisting (Enterprise)
Audit logs on every API call
Configurable data retention

Compliance

GDPR compliant; EU-region processing available
CCPA compliant
SOC 2 Type II in progress. Request latest status in Trust Center.
DPA on request
Sub-processor list at /trust-center

Questions GTM engineers actually ask.

How is the API different from the platform?

Same data engine, same waterfall, same accuracy. The platform layers Tables, GTM Co-Pilot, prospecting modals, and visual CRM sync on top. The API gives you the actions raw — bring your own UI.

Can I use the API and the platform together?

Yes. Same account, same credit balance, same audit log. Most teams that ship a feature on the API also keep a platform seat for ad-hoc list building.

Annual contract required?

No. API pricing is prepaid credit bundles. Buy only what you need; volume bundles include automatic per-credit discounts.

Sandbox?

Yes — every account ships with a sandbox key against test data. Develop without consuming production credits.

Can I resell the API?

Yes, with an approved reseller agreement. Several SaaS products power their enrichment under the hood with TexAu.

What happens when a provider in the waterfall is down?

The waterfall handles it internally. The next provider picks up. If every provider in the chain is unreachable, you get a hard-fail response with `billed: false` — your quota is refunded automatically.

Can I scope an API key to specific actions?

Yes. Action-level allowlists per key. Standard practice for agent safety and team isolation.

Where can I see every action?

The action catalog at /apps lists every integration and the actions on each. Each action page shows the parameters, sample response, and the equivalent MCP tool name.

Replace five integrations with one API.

Get a key, hit /email_finding_waterfall, see what comes back. Sandbox is free. 50 credits on signup, no card.

Get an API key →See API pricing Talk to sales