> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Clay Enrichment From AI Agents

> Let agents search Clay's people and company data, run enrichment routines, and query tables. The gateway injects your API key so agents never see it.

## Overview

Buckle connects AI agents to Clay with an API key. Agents can search Clay's GTM database for people and companies, run Clay-managed or custom functions to enrich records, and query Clay tables. The gateway injects the key into requests to `api.clay.com`, so your agent never sees it.

## What you will set up

* A Clay API key stored in Buckle
* Automatic key injection on requests to `api.clay.com`
* Per-agent, per-tool access, with approval for credit-spending runs

## Setup

**1. Create an API key in Clay**

In Clay, go to **Settings** > **Account** > **API keys** and create a key. Keys are tied to your Clay user and workspace. See [Find your Clay API key](https://university.clay.com/docs/guide-find-clay-api-key).

**2. Connect in Buckle**

Open the Buckle dashboard, go to **Settings** > **Apps** > **Clay**, and paste your key. The connection shows your Clay email and workspace.

![Buckle connect dialog for Clay, showing the required API key field, a link on how to find your Clay API key, an Advanced section with an optional connection label, and the Connect Clay button.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/clay/buckle-connect-clay.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=ead811bf7d22f54fab54451a142da7c0)

The Clay connect dialog in Buckle.

## What agents can do

| Area | Description |
| - | - |
| **Search** | Find people and companies with Clay's search query language |
| **Routines** | Run enrichment functions and workflows on 1 to 100 items, or in batches (uses Clay credits) |
| **Tables** | Query rows in Clay tables (Clay Enterprise) |
| **Runs** | Check routine progress and results, and search past workflow runs |
| **Credits** | Check the workspace's remaining credit balance |

## Quick example

No auth header is needed, the gateway adds it:

```bash theme={null}
# Who am I connected as?
curl -s "https://api.clay.com/public/v0/me"

# Check remaining credits before a large run
curl -s "https://api.clay.com/public/v0/credits/balance"
```

## Disconnecting

* In Buckle, open **Settings** > **Apps** > **Clay** and remove the connection.
* In Clay, delete the API key under **Settings** > **Account** > **API keys**.

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access.md) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked. Routine runs spend Clay credits, so consider requiring approval for them. Organization [rules](/docs/guides/rules.md) add guardrails on top, like rate limits. Everything is checked before credential injection, so a blocked request never reaches Clay.

## FAQ

> [accordion] How do I rotate my Clay API key?
>
> Create a new key in Clay under **Settings** > **Account** > **API keys**, then paste it into **Settings** > **Apps** > **Clay**. Agents pick up the new key automatically. Then delete the old key.

> [accordion] How do I keep the Clay key out of the agent's context?
>
> Store it in Buckle. The gateway adds it at the proxy, so agents call the API with no auth header. See [How it works](/docs/how-it-works.md).

> [accordion] How do I stop agents from burning Clay credits?
>
> Require approval for routine runs when you [grant](/docs/guides/agent-access.md) the connection, and add a rate limit with [rules](/docs/guides/rules.md). Agents can check the credit balance first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.