Which contact or company enrichment API should this workflow use?
Answered with dated prices from every vendor's own pages, and with receipts from calls we actually paid for.
175 calls · $2.93 billed
runs 2026-09-14 to 2026-09-17-verify
Decision guides
Choose a company enrichment API for scoring leads from a domain
Five company enrichment routes called on the same ten domains: which lead-scoring fields each one actually returned, what each record cost, and how far their employee counts disagree.
API options for teams replacing the data step of a Clay workflow
What Clay actually sells, what you lose by leaving it, and the three shapes of API that can take over the enrichment step: managed waterfalls, single providers, and a waterfall you run yourself.
Choose a contact enrichment API for an AI agent or growth team
Seventeen enrichment APIs compared on the terms that decide the bill for small, irregular batches: billing shape, minimum spend, cost per found email, whether misses are charged and whether the entry plan includes the API.
Enrichment for irregular workloads without a monthly subscription
Which enrichment APIs let you pay only when you use them, what company enrichment from a domain actually costs on each, and the usage level at which a subscription becomes cheaper.
Workflows
Google Maps to a verified owner email: what each API step finds and costs
Forty local businesses from two Google Maps searches, run through a website scrape, a domain search, an owner lookup, a finder and a verifier. Where each step loses rows, which step finds the owner and what one verified owner email cost.
Add contact enrichment to Claude Code without building each integration
How a coding agent gets work emails and company profiles through one MCP server instead of one integration per provider: the exact tool calls, what they returned on a ten-contact fixture, what it cost, and the provider-specific MCP servers you could use instead.
The cheapest way to find and verify work emails for 100 leads
Find-then-verify for a one-off list of 100 names plus company domains, costed four ways: a pay-per-call receipt scaled to 100, and the entry tiers of Icypeas, Hunter, Prospeo and Findymail with their free allowances, all from the vendors' own pages.
Benchmarks
Six email verification APIs, ten identical addresses, five different answers
The same ten work emails sent through six verification routes within seconds of each other: what each called them, what each charged, how long each took, and why 'valid' is not a shared definition.
How this site works
Each guide answers one buying question in the first paragraph, then shows the table the answer came from. Prices are quoted from the vendor's pricing or docs page on a stated date, with the link next to the number. Where we ran the job ourselves, the page shows a receipt: calls made, hits, latency and what the account was billed, with the masked raw responses available for download.
Read the methodology for what these numbers can and cannot tell you, and the about page for who writes here and how relationships with the routes compared are handled.