RichAPI is one data layer for every GTM pipeline you build — in a Claude prompt or a Python script. Describe your target buyers; it finds them, enriches them, and verifies their emails across 50+ data sources. You pay full price only when you get results.
25 free credits, no card. Then pay-as-you-go bundles from $100 — credits never expire, no subscription. Same key for REST and MCP.
# 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. 60 credits ($1.20). Misses billed at half rate.
# 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}"] } } }RichAPI is the GTM data API for builders and B2B teams. One REST API (api.richapi.ai) and one MCP server (mcp.richapi.ai/mcp) put 50+ endpoints behind a single key: LinkedIn profile & company enrichment, people and company search, post and keyword signals, five multi-provider enrichment waterfalls (email finding, phone finding, email verification, person enrichment, company enrichment), website intelligence, job-change signals, and AI-powered enrichment. Success-weighted billing: you pay the full rate only when an endpoint returns a result — soft misses cost half or less, and if providers fail outright you pay nothing. Every response carries a receipt: the provider that answered, the providers tried, and the latency of each. Same engine behind 26,000+ TexAu workspaces since 2018 — now exposed as one key for REST and MCP.
Connect once. Ask in plain language. No code needed. →
One key, 50+ endpoints, REST. First 200 OK in five minutes. →
White-label-ready backend with volume pricing. →
Verified lists at ~$52 per 1,000 contacts, all-in. →
Rather click than prompt or curl? You want TexAu — same engine, no code at all. →
The problem
You know the drill. An "unverified" number still burns a credit. Unused credits vanish at month-end. The annual plan auto-renews without a reminder. And somewhere in week two, $700 of credits just… disappeared.
The data industry normalized charging you for its own misses. We didn't.
The solution
Most teams arrive here mid-sprint: stitching enrichment vendors together, ranking providers by guesswork, handling each vendor's auth, schema, and failure modes, and re-doing all of it when a provider changes their API. That's engineering time spent on plumbing instead of pipeline. RichAPI replaces it with one key, one schema, and waterfalls that pick the provider for you — and you keep full control of the logic in code.
LinkedIn profile & company enrichment, people/company search, post & keyword signals, jobs data, web intelligence, YouTube & directory data, AI enrichment — one schema, one bill.
Full rate only when you get a result. Soft misses bill half or less. Hard provider failures bill nothing and say so: "billed": false.
Five fallback chains across vetted providers, with circuit breakers and provider health tracking. First provider with valid data wins; you see the whole attempt trail.
api.richapi.ai when you want explicit code. mcp.richapi.ai/mcp when you want Claude, Cursor, or ChatGPT in the loop. Same credits, same actions.
provider, providers_tried, per-provider latency in execution_log, plus a free /usage endpoint. Build your cost dashboard from the responses themselves.
Quickstart
# 1. Get a key (25 free credits, no card)
export RICHAPI_KEY="rk_live_..."
# 2. Enrich a LinkedIn profile (1 credit)
curl -X POST https://api.richapi.ai/api/v1/enrich_profile \
-H "x-api-key: $RICHAPI_KEY" -H "Content-Type: application/json" \
-d '{"url": "https://www.linkedin.com/in/satyanadella"}'
# 3. Find + verify an email (2 credits on success)
curl -X POST https://api.richapi.ai/api/v1/email_finder \
-H "x-api-key: $RICHAPI_KEY" -H "Content-Type: application/json" \
-d '{"first_name":"Satya","last_name":"Nadella","domain":"microsoft.com"}'
# 4. Check what you spent (free)
curl https://api.richapi.ai/api/v1/usage -H "x-api-key: $RICHAPI_KEY"Same key works in MCP. Point Claude at mcp.richapi.ai/mcp and every endpoint above becomes a tool.
Inside one waterfall call
An email_finder call tries vetted providers in priority order and stops at the first valid result. You're billed 2 credits for the hit. If every provider answers but none has the email, you pay 1 credit — half rate for the work done. If providers are down or rate-limited, you pay nothing, the response says "billed": false, and it's safe to retry. The execution_log shows every provider tried and how long each took.
- DIY: 5 provider contracts, 5 schemas, 5 auths,
you write the fallback and eat the failures
+ RichAPI: 1 key, 1 schema, waterfall + circuit
breakers built in, billed by outcomeBuilt for the agent era
Point Claude at a single-vendor MCP and it searches that vendor's database. Point it at mcp.richapi.ai/mcp and one tool call runs multi-provider enrichment with success-weighted billing and a full execution trace the model can reason about. 35+ tools, auto-registered, namespaced richapi_*. One MCP server instead of five is also a context-window decision: fewer tools, better tool-use.
MCP install guide> find 20 Series-B SaaS CTOs who posted about
hiring this week, get verified emails
richapi_post_keyword_search → 20 authors
richapi_enrich_profile → 20 profiles
richapi_email_finder → 14 verified
✓ 20 profiles · 14 verified emails · 60 credits
misses billed at half rateWhy not the alternatives
From teams running on the engine behind RichAPI (via TexAu)
Heard around the industry
| What users say about the tools they're leaving | At RichAPI |
|---|
We don't claim our data never misses — nobody honest can. We claim you'll always see the miss, and you'll never pay full price for one.
Security documented like an engineering page → /security
Pricing
1 credit = $0.02, always. Success-weighted billing on waterfalls. Per-result billing on search. Inquiry and usage endpoints free. See full pricing →
FAQ
No subscription. No seat math. No procurement to start.
Get 25 free credits, make your first enrichment call in five minutes, and see the receipt in the response. When you're ready, $100 starts the meter — and credits never expire.
Operator who'd rather click than curl? See TexAu →