About RichAPI
RichAPI is the API + MCP surface of the GTM engine that has run TexAu since 2018 — spun out as its own brand in 2026, because the operator who wants a UI and the engineer who wants an endpoint are two different customers.
Lineage
TexAu shipped in 2018 as a B2B prospecting automation tool. Over eight years the engine underneath grew into what GTM data infrastructure actually requires: multi-provider enrichment waterfalls with circuit breakers, per-customer rate limiting with refund-on-failure, success-weighted billing, signed webhooks, structured observability, and a test suite that gates every deploy. 26,000+ workspaces have run on it.
When Anthropic published the Model Context Protocol, we put the engine behind an MCP server. Watching what agent-builders did with it made the conclusion unavoidable: the API wasthe product for a customer we'd been under-serving — the GTM engineer who wants control, not a canvas.
The 2026 split
Remains the operator product: UI, monthly plans, no code required. If you'd open a table, you want TexAu.
The same engine for people who build: REST + MCP, one key, pay-as-you-go credits. If you'd curl it, you're home.
Principles
Success-weighted billing exists because charging full price for a miss is a vendor-side bug the industry normalized.
provider, providers_tried, execution_log with latencies — on every waterfall call. Infrastructure you can't audit is infrastructure you can't trust.
No single data source wins everywhere. The waterfall is the product.
We return clean JSON; your code writes it where it belongs. Data infrastructure that quietly holds write access to your CRM is a liability, not a feature.
Circuit breakers, idempotent retries, zero-PII logs, 517 tests in CI. Eight years of pager duty went into this engine.
Company
Built and headquartered in Tallinn, Estonia — EU jurisdiction, GDPR-first by default, e-resident-friendly invoicing, and the engineering culture of a country that runs its government on APIs. The team is small on purpose; the test suite is large on purpose.
Numbers
Founder note
The 2018 thesis: GTM work was duct tape, and the operator deserved a real tool. The 2024 thesis: when models can call tools, the tool catalog matters more than the UI. The 2026 thesis: the operator and the engineer are different buyers, and pretending one homepage serves both was costing us both.
RichAPI is the bet on the engineer. If you build GTM pipelines — in Python or in a Claude window — this is for you.
— Vikesh, founder · LinkedIn
Operator surface? TexAu — same engine, different door.