> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/product/people/adding-provider-keys.md).

# Adding Provider Keys

Rox allows Enterprise customers to supply their own API keys instead of using Rox’s shared keys. This lets your organization use its own provider agreements, manage usage and quotas independently, and keep enrichment running even if shared-key capacity is constrained. This feature is available on Enterprise plans only — self-serve accounts cannot add provider keys (except for HG Insights).

### Adding a Key

There are two ways to add a provider key. Both methods store the key at the organization level, making it available to all users and all future enrichment columns that use the same provider.

**Method 1: Via an Enrichment Column**

* Open or create an enrichment column for a provider that supports custom keys (e.g., Find Work Email using Hunter).
* In the column configuration panel, locate the key input field for that provider and enter your API key.
* Save the configuration. The key is automatically stored in your organization’s settings and will be available for any future enrichment column that uses the same provider.

<img src="/files/1H6wH38DWyOG7sLjf7b6" alt="" height="348" width="267">

**Method 2: Via Organization Settings**

* Navigate to Settings from the main navigation.
* Locate the Enrichment Provider Keys section and find the provider you want to configure.
* Enter your API key and save. The key is immediately available for selection in any enrichment column that uses that provider.

<img src="/files/Sx3EMGFNChOGsDopsn88" alt="" height="341" width="624">

### Using a Stored Key for Enrichments

Once a provider key has been stored (via either method above), it is available across all enrichment columns in your organization. When adding or configuring an enrichment column for that provider, you will see a toggle or selector indicating that a connected key is available. Click it to activate your key for that column - the column will then use your organization’s key rather than Rox’s shared key. The stored key is shown as “connected” once selected.

| <p><mark style="color:$primary;">Self-serve users can add keys for HG Insights only, following the instructions above.</mark><br><mark style="color:$primary;">Enterprise users can add keys for all supported providers listed in Rox, with the exception of HG Insights.</mark></p> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rox.com/development/product/people/adding-provider-keys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.