Builder infrastructure
TexAu
GTM platform · API · MCP
TexAu markets a GTM platform for finding, enriching, scoring and routing leads from a table, REST API or hosted MCP server. It describes pay-on-match credits and integrations across CRM, enrichment and outbound tools.
Vendor's own claim
What TexAu is
Vendor's own claimTexAu combines a table-based GTM platform with a separate API and MCP product. The retrieved API page documents REST access through an x-api-key, while the MCP page describes hosted HTTP access for agent clients.
What it can do
Vendor's own claim- Lead search and enrichment
- Email and phone waterfalls
- Lead scoring
- CRM and outbound-tool sync
- REST API and webhooks
- Hosted MCP server
Who it is for
Vendor's own claimFounders, agencies, GTM teams and GTM engineers that need enrichment, verification, CRM routing or agent-driven data workflows.
When to choose something else
Our readTeams with only occasional enrichment needs may find the $79/month Solo starting point and credit model excessive. Buyers must also check which product they need: the pricing page says the Platform and standalone API/MCP are separate subscriptions and dashboards, even though Starter and above include Platform-scoped API and webhook access.
Developer and agent access
From official docs- Authentication
- x-api-key for REST and most MCP clients; Claude Desktop uses OAuth
- Base URL
- https://v3-api.texau.com/api/v1
- Rate limits
- 100,000 calls/month per endpoint is stated on the API page; MCP FAQ states a default 100 requests/sec per key.
- Machine-readable API
- No OpenAPI link in the reviewed source set
- POST /v1/email_finding_waterfall
- /enrich_profile
- /enrich_company
Published pricing
From official docs| Plan | Price | Included |
|---|---|---|
| Solo | $79/mo | 2,500 credits/month (~500 enriched leads) |
| Starter | $199/mo | 8,000 credits/month (~1,600 enriched leads) |
| Teams | $549/mo | 25,000 credits/month |
| Enterprise | Custom | Unlimited team members |
Verify before you adopt it
- A machine-readable OpenAPI specification was not included in the reviewed source set.