Skip to main content
/enrich returns everything Prefetch knows about the company behind a URL: its brand, its company details and its industry. The page is loaded once, so it costs less than calling the three separately. Each block sits under the same key its own endpoint uses: data.brand, data.company and data.classification. Code written for /brand or /classify reads an /enrich response unchanged. The one difference is social_links, which sits on data.company here and on data.brand in /brand.

Example requests

Example response

A real response for stripe.com, shortened where marked with …:
Well-known companies like Stripe are answered from curated data in milliseconds. Other sites are read live, which takes 5 to 20 seconds, and the fields can differ a little. Treat every field as optional. See Caching.

Parameters

/enrich takes the same options as /brand. Like /brand, its parameters are camelCase. Batches and MCP take the snake_case spelling (screenshot_colors). The screenshot settings here only shape the screenshot /enrich takes for itself. To capture pages, use /screenshot, which has its own options and limits.

For many domains

Send up to 500 domains as one job with POST /batch/enrich. Each domain costs the same 12 credits, and you don’t have to manage concurrency yourself.

Next

Enrich signups and leads

A complete recipe: from a work email to a prefilled profile.

API reference

Every parameter, and a playground to try it.