> ## Documentation Index > Fetch the complete documentation index at: https://docs.os.default.com/llms.txt > Use this file to discover all available pages before exploring further. # Enrichment providers > Connect the providers behind enrichment Waterfalls and Website Intent visitor identification. Default works with a range of enrichment providers. Default manages access to them, so you don't need to obtain or paste an API key. Turn on the providers you want. Then use them as sources in your enrichment [Waterfalls](https://docs.os.default.com/settings/configurations/waterfalls.md), which fill in fields on your **Company** and **Person** records. > [!NOTE] > > Select **Settings** in the sidebar, then **Connections** under **Workspace Settings**. Then choose > the **Enrichment** or **Website Intent** category. > > Admin access is required. ## How enrichment providers work **1. Turn the provider on** Select the provider on the Connections page and turn it on. If a provider is not available to your workspace, contact Default to have it enabled. **Vector** also needs the Default Pixel on your site. See [Website Intent](#website-intent). **2. Add it to a Waterfall** Once it is on, you can add the provider to a [Waterfall](https://docs.os.default.com/settings/configurations/waterfalls.md), which lists up to 5 providers in priority order. You can also pick a single provider in the **Enrich Data** workflow node. See [Enrichment nodes](https://docs.os.default.com/workflows/steps-enrichment.md). **3. Manage or turn it off** Select a provider's card at any time to review it or turn it back off. ## Available providers ### Person and company enrichment Fill in contact and company details. These 4 providers are the ones you can add under **Enrichment order** in a waterfall. | Provider | What it adds | | - | - | | [**Clearbit**](https://docs.os.default.com/settings/connections/clearbit.md) | Company and contact attributes, including the technologies a company uses. | | [**Apollo**](https://docs.os.default.com/settings/connections/apollo.md) | Person and company data. The **Apollo.io (Enrichment)** card is managed by Default and needs no Apollo account. It is separate from the **Apollo.io (Sequencing)** card, which connects your own Apollo account for sequences. | | [**People Data Labs**](https://docs.os.default.com/settings/connections/people-data-labs.md) | Person data with employment history and education, and company workforce and funding data. | | [**Wiza**](https://docs.os.default.com/settings/connections/wiza.md) | Work emails and phone numbers, best found from a LinkedIn URL. | ### Email and IP checks Check contact data you already have. These run as the **Email validation** and **IP validation** checks in a waterfall. Abstract Email Reputation and Icypeas can also run on their own in an **Enrich Data** node. | Provider | What it adds | | - | - | | [**Abstract Email Reputation**](https://docs.os.default.com/settings/connections/abstract.md) | Validates and scores email addresses. | | [**Icypeas**](https://docs.os.default.com/settings/connections/icypeas.md) | Verifies an email address you already have. It does not find new emails. | | [**Abstract Geolocation**](https://docs.os.default.com/settings/connections/abstract.md) | Adds location and network detail from an IP address. | ### AI research | Provider | What it adds | | - | - | | [**Parallel**](https://docs.os.default.com/workflows/steps-research.md) (Beta) | Researches the live web from a prompt and returns the answer as structured fields, through the **Deep Research** workflow node. | Parallel is in beta. If you do not see the **Deep Research** node in your workspace, contact support. ### Website Intent Identify the companies and visitors behind anonymous website traffic. These providers pair with the [Pixel](https://docs.os.default.com/settings/pixel.md). On the Connections page, these providers sit under their own **Website Intent** category, separate from Enrichment. Website Intent providers are available at an additional cost. Speak to the Default Customer Success team to learn more. The toggle on each provider controls spend. A provider that is off is never called for your visitors and never uses credits. Turn Clearbit Reveal or Demandbase off and Reveal stops paying that provider from the next visit. Turn Vector off and the Pixel stops loading it, and any deliveries still in flight are dropped without a charge. The cost of a Clearbit Reveal or Demandbase lookup is on the Reveal headers in Signals, and again when you turn Reveal on for a page. Vector's cost is on its own integration page. | Provider | What it does | | - | - | | [**Clearbit Reveal**](https://docs.os.default.com/settings/connections/clearbit.md#clearbit-reveal-in-default) | Identifies companies visiting your site, in real time, on pages with **Reveal** on. | | [**Demandbase**](https://docs.os.default.com/settings/connections/demandbase.md) | Identifies companies visiting your site, in real time, on pages with **Reveal** on. | | [**Vector**](https://docs.os.default.com/settings/connections/vector.md) | Identifies visitors as people, with name, title, and email, in batches about every 30 minutes. | > [!NOTE] > > **Vector** is connected and managed by Default. With Vector on, the Pixel loads Vector's script for > visitors who grant marketing consent. If any paths on a domain have Reveal on in Signals, the Pixel > only loads Vector on those paths and Default drops any visit that includes none of them, without a > charge; otherwise Vector runs on every page with the Pixel installed. Each identified visit Default > uses costs 3 credits. Pages the Pixel skips, such as login and checkout paths, never load Vector. > Vector only serves domains Default has registered with it. Turning Vector on registers your > workspace domains; if nothing arrives after that, contact your Default team. See > [Vector](https://docs.os.default.com/settings/connections/vector.md). Related: [Lead enrichment software from Default](https://www.default.com/product/lead-enrichment-software) and [Default integrations](https://www.default.com/integrations) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.