about
About this site
Who writes Enrichment API Guide, how it is funded, and how relationships with the routes it compares are handled.
Enrichment API Guide answers one question: which contact or company enrichment API should a given workflow use. It is written for people building agents and internal tools who buy data by the call, and for growth teams who have outgrown a browser extension but do not want a prospecting platform.
Who writes here
Guides are written and re-checked by Shirley Lou, who runs the data-API research behind this site. Additional bylines from the team will appear as they publish. There are no pseudonymous authors on this site.
Relationships {#relationship}
This site is run independently of the providers it compares, with one relationship to state: the people who run it also work on Treg, a pay-per-call API that routes data requests across providers, and Treg appears in some comparisons as one route among others. Every page that includes a Treg route says so in a note at the end of the page. Every Treg figure is a call we paid for, with the raw response downloadable, and the same fixture is run against the alternatives where their terms allow. Provider prices are quoted from each provider’s own pages with the URL and date next to the number. No affiliate links, no paid placements, no rankings.
What is not on this site
- No “best” rankings. Guides say who each option fits and where it fails.
- No claims about competitors’ data quality that we did not measure.
- No affiliate links. Vendor links go to the pricing or docs page the figure came from.
Corrections
If a price or term on this site is wrong or has changed, email corrections@enrichmentapiguide.com with the page and a source. Changes are logged on the corrections page with the date and what changed.