Pick your door
API or table? Pick in 30 seconds.
TexAu is a GTM data platform with 81 endpoints across 32 integrations. The same enrichment, scoring, and CRM sync runs behind a table UI and a REST + MCP API. Pick the door that matches who's driving.
The 30-second decision
Will a human be looking at the data in TexAu, or will only your code touch it?
- If a human is using it → Platform.
- If only code touches it → API.
- Both → You'll want both. Talk to us about bundled pricing.
Side-by-side.
| TexAu Platform | TexAu API | |
|---|---|---|
| Who it's for | GTM operators, agencies, founders, sales teams | GTM engineers, SaaS products, AI agents, data warehouses |
| Interface | Table UI, GTM Co-Pilot, visual CRM sync | REST + webhooks + MCP server |
| Setup time | 5 minutes (sign up, paste, enrich) | 5 minutes (key, curl, ship) |
| Best for | "500 enriched leads in HubSpot by Friday" | "Our app needs to enrich users on signup" |
| Team seats | Included on team plans | Not applicable — API keys instead |
| Workflow building | Right-click on a column | Compose endpoints in your code |
| Scheduling | Built into the table | Use cron, EventBridge, your scheduler |
| CRM sync | Bidirectional, visual, real-time | API endpoints — you control the sync logic |
| AI agents (MCP) | Use the MCP catalog from Claude/Cursor | Same MCP catalog, your API key |
| Credit cost | Standard rate | 40% off platform rate |
| Pricing model | Monthly subscription, per workspace | Monthly, volume tiers, no annual lock-in |
| Pay-on-match | Yes | Yes |
| Roll-over credits | Up to 2× monthly balance | Up to 2× monthly balance |
| Sandbox | Free trial | Sandbox key included |
| Best signal you need this | "I want to do outbound today" | "I'm reading this on a phone in a code editor" |
Three picks for three buyers.
"I run an agency"
You have ten clients. Each client has their own list, their own CRM, their own quirks. You want one place to do enrichment across all of them, with a workspace per client and shared credits.
Pick: Platform → Teams tier
See agency plan →"I'm shipping an enrichment feature inside my SaaS"
You don't want users leaving your product. You want enriched company data appearing on user profiles. You need an API call on signup and a webhook when data refreshes.
Pick: API → Growth tier
See API Growth tier →"I'm building a GTM agent in Claude / Cursor / LangGraph"
You want your agent to find leads, score them, draft personalized messages, and push to outbound — without you writing tool wrappers.
Pick: API + MCP → start with Starter
Install MCP →"We do all of the above"
A common scenario for multi-team accounts. Operators run the day-to-day in the platform. Engineers embed the API in your product. The same credit pool can fund both, but you'll want bundled pricing.
Bundle → Talk to salesYou don't lose anything by choosing one.
Same waterfall.
32 integrations cascaded, identical order, identical accuracy.
Same data.
Email, phone, company firmographics, tech stack, funding, LinkedIn — same registry, same providers.
Same MCP catalog.
Both products expose the same 200+ tools to AI agents. The difference is who pays for the calls.
Same compliance.
GDPR, CCPA, SOC 2 (Q3 2026). Same DPA, same security controls.
Same support.
Same engineering team behind both.
The trade-offs.
Choose Platform if you want:
- A UI your non-technical team can use today
- The GTM Co-Pilot ("describe a pipeline, get a table")
- Visual CRM sync with conflict resolution
- Templates that deploy across client workspaces
- Per-seat collaboration, comments, audit trails
- Scheduled enrichment runs without writing cron
| Lead | Company | Score |
|---|---|---|
| Sarah Chen | acme.com | 92 |
| Marco Liu | northwind.io | 88 |
| Priya Rao | globex.dev | — |
Choose API if you want:
- 40% lower per-credit cost
- Programmatic control over every action
- Embedding enrichment inside your own product
- Idempotency keys, webhooks, replay
- AI agent integration (MCP) inside your stack
- Custom UI on top of TexAu's engine
/v1/email_finding_waterfall{ "first_name": "Sarah", "last_name": "Chen", "domain": "acme.com" }
{ "success": true, "result": "[email protected]", "provider": "hunter" }
Most teams end up with both.
The most common journey: a GTM operator signs up for the platform, runs outbound from a table, and proves the wedge. Six months later their GTM engineering team starts embedding enrichment in the product — or shipping an AI sales agent — and they add the API on top of the existing account.
We make this transition explicit. Same login, same billing, separate credit pools (or shared, your call). Operators don't lose their workflows. GTM engineers don't get a separate vendor relationship.
Talk to sales about bundling →FAQ
Can I use both?
Yes. Many teams do. Platform for GTM operators, API for GTM engineers. Talk to us about bundled pricing.
Will my data appear in both?
Workspaces are isolated by default. You can connect API keys to specific workspaces if you want unified analytics. Otherwise they're separate.
Does the MCP server require the API or the platform?
Either works. The MCP server authenticates with a TexAu key — platform or API. The credit cost differs (API rate is 40% lower).
Can I downgrade from one to the other?
Yes. Plans are monthly. Switch when it makes sense.
What if I'm not sure which I need?
Start with the platform. If you find yourself writing scripts to drive it, you want the API too.