01 / THE USE CASE
Enrich a domain from the company's own pages
Outreach, vendor research, and CRM enrichment often start with a hostname. The Website Contacts API reads what that company already posted: mailto, tel, JSON-LD people, and social profile URLs.
It is not a people-search database, not a breach dump, and not a logged-in scrape of a SaaS app. If the company did not publish a path, Clair does not invent one.
02 / HOW TO CALL IT
One domain, one live lookup
Call GET /v1/contacts?domain=example.com. The domain may include a scheme. Read emails[], phones[], social[], and contacts[] when named people are labeled on the page. See the Website Contacts API for the full contract.
Each call costs 10 credits because the work happens at request time.
03 / BOUNDARIES
Public pages and source rights still apply
Use results in line with the source site's terms and applicable law. Do not treat this SKU as a way to assemble a competing contact directory. Keep the originating domain visible in your own product wherever context permits.
For public reviews of the same company, see review intelligence. One key covers both.
04 / FAQ
Questions from enrichment teams
Does Clair crawl the whole site?
No. It fetches the homepage and, when linked, one same-origin contact or about page. There is no login and no sitemap walk.
Are these verified working inboxes?
No. Clair returns addresses published on public pages and filters obvious placeholders. Deliverability is your responsibility.
Can I pass an IP or localhost?
No. Those hosts are rejected before the fetch.