About RichAPI
The engine behind GTM data.
RichAPI is the GTM data API and MCP layer built from the infrastructure behind TexAu, which has been running in production since 2018.
After years of building prospecting and enrichment infrastructure, we realized the same engine could serve a different kind of customer: developers and GTM teams who want to build their own workflows instead of working inside another platform.
RichAPI gives them that engine through REST + MCP, with 65+ endpoints behind one key.
Our story
Eight years of building GTM infrastructure.
TexAu started in 2018 as a B2B prospecting automation platform. Over the years, the infrastructure underneath it evolved to handle the hard parts of GTM data at scale: multi-provider enrichment, waterfalls, rate limits, retries, webhooks, observability, and reliable billing.
More than 26,000 workspaces have run on that underlying engine.
RichAPI takes the same infrastructure and makes it available directly to builders.
No UI to work around. No platform subscription required. Just the data layer, exposed through an API and MCP.
TexAu & RichAPI
Two products. One engine.
TexAu
For operators who want to build and run workflows without code.
A visual interface, managed workflows, and monthly plans.
RichAPI
For developers and GTM teams who want to build with the infrastructure directly.
REST + MCP, 65+ endpoints, one API key, and pay-as-you-go credits.
Same engine. Different way in.
Principles
What we believe
- 01
Failed calls cost nothing.
A failed lookup shouldn't cost the same as a successful one.
Hard failures never use credits. On email and phone waterfalls, a lookup that finds nothing costs nothing too.
- 02
Make the work visible.
Every waterfall should tell you what happened.
We expose providers tried, execution details, latency, and usage so your team can understand what ran and what it cost.
- 03
Coverage comes from multiple sources.
No single provider has the best data everywhere.
Our waterfalls combine multiple sources and stop when they get a successful result. The routing layer is part of the product.
- 04
Give you the data. Let you own the system of record.
RichAPI returns clean data. Your application decides where it belongs.
We don't need write access to your CRM to provide the infrastructure underneath your GTM workflows.
- 05
Reliability should be boring.
Circuit breakers, retries, rate limits, structured observability, zero-PII logs, and automated tests are part of the foundation.
You shouldn't have to think about them when the system is working.
Where we are
Built in Tallinn, Estonia.
RichAPI is built and headquartered in Tallinn, Estonia.
We're a small team by design, focused on building infrastructure that developers can depend on.
EU-based. GDPR-first. Built around APIs from the ground up.
By the numbers
The numbers
- Engine in production
- 2018
- Workspaces on the underlying engine
- 26,000+
- API endpoints behind one key
- 65+
- Multi-provider waterfalls
- 3
- MCP tools
- 65+
- RichAPI launched as its own brand
- 2026
Why RichAPI exists
GTM infrastructure should be accessible directly.
GTM infrastructure has traditionally been hidden inside the tools that use it. We think it should be accessible directly.
If you're building a GTM product, automating research, enriching leads, or giving an AI agent access to sales data, you shouldn't need to rebuild the data layer yourself.
RichAPI is that layer.
Build your workflow. Bring your own system of record. Use the infrastructure underneath.
One key. 65+ endpoints. Credits that never expire.
Build with RichAPI.
Start with 100 free credits and see what you can build.
Operator looking for a visual workflow? TexAu — same engine, different door.