01
LinkedIn enrichment
enrich_profile, enrich_company, bulk variants, find_linkedin_url_by_email/name. 1 credit per profile.
api.richapi.ai · one key, two protocols
RichAPI is a GTM data API (REST + MCP) with 50+ endpoints behind one key: LinkedIn profile and company enrichment, people search, email/phone finding through multi-provider waterfalls, post and hiring signals, website intelligence, and AI enrichment. Billing is endpoint-based (per call or per result). 25 free credits to start.
POST /enrich_profile, /people_search, /email_finder, /post_keyword_search, /website_intelligence — 50+ endpoints that share one auth header, one schema philosophy, one credit pool, and one pricing model: explicit per endpoint.
The catalog
enrich_profile, enrich_company, bulk variants, find_linkedin_url_by_email/name. 1 credit per profile.
people_search (0.1 cr/result), company_search, lead_search, linkedin_company_employees_search, geo_id_search.
post_keyword_search (who's posting about what), post_activities (likers/commenters), profile_activities, company_posts, linkedin_job_search (hiring signals).
email_finder, phone_finder, email_verifier, person_enricher, company_enricher. Multi-provider, first-success, billed by published endpoint rates.
web_scrape, web_tech_stack, web_emails, web_meta_tags, website_intelligence, Google Maps/Search scrapers, Crunchbase company scraper.
Run GPT, Claude, Gemini, or Perplexity over any record server-side: classify, summarize, score against your own ICP definition in the prompt. 2 credits/call.
Domain cleaning, gender prediction, email-type identification, list normalization, sitemap discovery.
The receipt
{
"success": true,
"result": { "email": "priya.singh@acme.com", "email_status": "valid" },
"provider": "email_finding_prospeo",
"providers_tried": 2,
"execution_log": [
{ "provider": "email_finding_hunter", "status": "no_result", "latency_ms": 410 },
{ "provider": "email_finding_prospeo", "status": "success", "latency_ms": 342 }
]
}Which provider answered. Which were tried. How long each took. Whether you were billed. No other GTM data API shows you the waterfall — we bill by outcome, so we can afford to show the attempts. Your free /usage endpoint aggregates it monthly per endpoint.
Reliability engineering
Failing providers are auto-removed from waterfalls and probed back to health; you never wait on a dead vendor.
Atomic check-and-increment with refund-on-failure; 100K calls/endpoint/month default.
Hard fails bill nothing and are safe to retry after backoff.
On email finding/verification jobs (white-label available on Enterprise).
Structured logs, correlation IDs, zero-plaintext-PII log policy, CI test gate on every deploy.
On synchronous endpoints — we publish real latency distributions in the waterfall reports. (Roadmap: result caching on paid lookups, targeting <100ms cache hits.)
REST vs MCP
| REST | MCP | |
|---|---|---|
| Use when | You're writing pipelines/crons | Claude/Cursor/ChatGPT drives the workflow |
| Auth | x-api-key header | Same key (OAuth in claude.ai, header via shim elsewhere) |
| Coverage | 50+ endpoints | 35+ tools (expanding to parity) |
| Credits | Same pool | Same pool |
Use both. REST for the 6am cron, MCP for the human-in-the-loop afternoon.
Pricing
1 credit = $0.02. Endpoint pricing is per call or per result. 25 free credits to start. See full pricing →
FAQ
Yes — agencies and platforms do exactly that. Volume rate cards and white-label webhooks live on the Enterprise tier; partner program at /contact-sales.
Standard: 99.5% uptime target, public status page. Enterprise: 99.9% SLA with credits as remedy.
Web-scraping endpoints cache server-side for speed and cost; paid-provider lookups are fetched live today (result caching for those is on the near-term roadmap — changelog tracks it).
Licensed data providers (waterfalls), public web sources (scraping endpoints), and the customer's own inputs (AI enrich). Provenance per endpoint is documented; compliance posture at /security.
Python today (all core endpoints), TypeScript in progress; OpenAPI spec for everything else. /developers has the matrix.
The endpoint surface expands toward 75+ this quarter: deeper signals coverage, result caching on paid lookups, webhook coverage on all waterfalls. changelog at docs.richapi.ai.