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.
30 calls · $0.36 billed
run 2026-09-14
Decision guides
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.
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.
The site is published by the team behind Treg. When a page evaluates Treg it says so at the top. Read the methodology for what these numbers can and cannot tell you, or the about page for who writes here.