about
About this site
Who writes Enrichment API Guide, who pays for it, and how the relationship to Treg is handled on every page.
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 research at Treg. Additional bylines from the Treg team will appear as they publish. There are no pseudonymous authors on this site.
Relationship to Treg {#relationship}
This site is published by the team behind Treg, a pay-per-call API that routes data requests across providers. Treg appears in comparisons on this site as one option among others, and we earn money when readers use it.
We handle that in three ways:
- Every page that evaluates or recommends Treg carries a disclosure block directly under the answer, not only in this footer.
- Every Treg figure is a receipt: a call we paid for, with the masked response downloadable from the evidence page. We do not quote Treg list prices as observed costs.
- Competitor prices are quoted from the competitor’s own pricing or docs page, with the URL and date next to the number. Where a page could not be read without a login or a browser, the figure is marked unknown rather than filled in from a third party.
None of that makes this an independent review site, and we do not claim it is. It makes the numbers checkable.
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.