One API for enrichment, search, email and phone find-and-verify, company data, and signals — fetched live, not resold from a database that went stale months ago. Call it from your own code, from Claude or Cursor, or inside the tools you already run like Clay, n8n, and TexAu. $0.02 per verified record. No seats.
First call in under 5 minutes · Pay only for verified records · No credit card
# In Claude (no code) You: @richapi find 20 VPs of Marketing at 50–200 person SaaS companies who posted about pipeline this week, and get me verified emails. Claude: Done — 20 profiles, 14 verified emails. 126 credits ($2.52).
# In code: same thing, one call
// The receipt comes with the result
{ "success": true, "result": { "email": "priya.singh@acme.com", "email_status": "valid" }, "provider": "email_finding_prospeo", "providers_tried": 1, "execution_log": [ { "provider": "email_finding_prospeo", "status": "success", "latency_ms": 342 } ] }
// Same key in Claude — mcp.richapi.ai/mcp (35+ tools)
{ "mcpServers": { "richapi": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.richapi.ai/mcp",
"--header", "x-api-key: ${RICHAPI_KEY}"] } } }Every response shows the record, the cost, and the latency. We don't have a cache to serve you — fetched_at is the timestamp of your request.
Powers TexAu and the workspaces running live data on top of it.
The problem
Most B2B data isn't fetched, it's recalled. Apollo, ZoomInfo, even API players like People Data Labs sell you rows out of a database refreshed on their schedule, not at the moment you need it. By the time a record reaches your sequence, the person changed jobs, the email bounces, and the phone rings a desk nobody sits at.
You paid for 10,000 "verified" contacts. Half bounced. The database was over a year old.
You feel it as bounce rates your clients complain about, credits burned on people who left, and "verified" emails that weren't. The problem isn't your outreach — it's that you're working from a photograph and calling it a live feed.
The solution
When you request a record, RichAPI goes and gets it. Enriches the person, finds and verifies the email, finds the phone, reads the company, then streams back a record that was true a moment ago, not a fiscal quarter ago.
Our enrichment and verification waterfalls call licensed data providers live, at request time — no caching, today. Scraping endpoints (the ones reading public web pages) cache server-side for speed. Either way: no resold static dataset, no mirroring a single platform. How we source data →
The cost wedge
Enriching inside a GTM platform stacks markup on markup — you pay the platform to call a provider to call a source. RichAPI is the source-direct layer: $0.02 per credit, billed only on verified records. It's the same live-data engine that already powers TexAu — now available direct, at cost.
| RichAPI | Enriching inside a GTM platform | |
|---|---|---|
| Per verified record | $0.02 | Markup on markup — varies by platform |
| Charged for misses | Never | Often |
| Seats / minimums | None | Usually |
| Contract | Pay as you go | Annual, common |
$0.02 per credit. Pay only for verified results — no charge for misses, dupes, or unverifiable records.
Built for agencies
You're not buying data for one list — you're buying it for multiple clients at once, each with their own ICP, each watching their bounce rate, each squeezing your margin. RichAPI fixes the three things that hit your books.
Spin up a sub-key per client; every credit is tagged to whoever it was spent for. Export usage by client at month-end and bill it straight through — no more eating costs you can't trace.
You're charged when a record comes back verified. Catch-alls and unknowns are returned free and clearly labeled. That's the difference between a 40% margin and a 70% one on the same list.
Every record is pulled live, not dredged from a database scraped last spring. Lower bounce rates, fewer spam flags on your clients' domains, fewer Monday-morning complaints.
"I was paying for seats across three tools and still couldn't tell my clients apart on the invoice. Switched our enrichment to RichAPI, gave each client a sub-key, and our data spend dropped about 35% — mostly because I stopped paying for records that bounced anyway."
One API, every data job — wherever you build
Fill in the person behind an email, name, or profile. 1 credit.
Find the right people by title, company, and more. 0.1 credits/result.
Current firmographics and tech, fetched live. 1-2 credits/call.
Find it, then prove it lands. 0.5-5 credits (by endpoint).
Direct dials, checked. 25 credits/call.
Structured data from any page. 1 credit.
Funding rounds, job changes, hiring — the triggers that make outreach land. Credits vary by endpoint.
Three ways to call it
In your code — a plain REST API (api.richapi.ai). Drop it into any script, app, or pipeline.
In Claude, Cursor, or VS Code — connect over MCP (mcp.richapi.ai/mcp) and pull live records right in your editor or chat. Same key, same credits, same data as REST.
In your GTM tools — wire it into TexAu, Clay, Bitscale, or n8n and feed every workflow the same fresh source.
No new dashboard to learn. One key, every surface. Nothing to migrate into, nothing to migrate out of.
MCP Install Guidecurl https://api.richapi.ai/api/v1/enrich_profile \
-H "x-api-key: $RICHAPI_KEY" \
-d '{"email": "jane@acme.com"}'Accuracy, coverage & speed
Live fetch is slower than a cached database lookup and typically returns in a few seconds, with longer tails for hard-to-verify records. That's the trade for data that's current. For large jobs, use the bulk endpoint or async webhooks.
$0.02 per credit. Credits vary by endpoint, from 0.01 credits/result to 25 credits/call. Pay only for verified results — no seats, no minimums, no contract. Start with 25 free credits, no card.
What changes when the data's actually live
Your sequences hit inboxes instead of bouncing.
Your clients stop forwarding you their deliverability reports.
You stop paying for contacts who left their job in 2023.
The same record powers your code, your editor, and your GTM tools — bought once, not three times.
From teams running on the engine behind RichAPI (via TexAu)
“We modeled it as two BDRs of output without two BDRs of headcount — that's the line that got it through the board.”
“Wired enrichment, signal, and outreach into one Claude orchestration last quarter and cut research time by maybe 70%.”
“It turned into a context-engineering problem, not a data problem — RichAPI is the part I stopped having to think about.”
“Stopped asking where can Claude help and started asking what parts of our GTM motion can Claude do better than humans at scale.”
“Teams that treated this as plumbing rather than a feature shipped 3x faster.”
FAQ
Every call fetches and verifies at request time.
A result is verified only when our waterfall returns a positive deliverability or reachable signal. Misses and unknowns return free and labeled — see the per-record cost in your usage log.
Coverage is strongest in North America and Europe and expands continuously. Run a sample of your ICP to benchmark match rate by region.
Single calls are typically a few seconds. For large jobs, use the bulk endpoint or async webhooks.
Public web sources, verified at request time — see Data sourcing & compliance →. GDPR/CCPA opt-out and "do not sell" supported.
Published per-key rate limits. Versioned API with a 30-day deprecation notice. Export your keys and usage anytime.
No subscription. No seat math. No procurement to start.
25 free credits. No credit card. No seat to buy. Watch a verified record stream back — with its cost and latency right there — before you decide anything.
Operator who'd rather click than curl? See TexAu →