Key Takeaways (TL;DR)
Connect your existing data provider accounts (Apollo, Better Contact, Prospeo, Lead Magic, Contact Out) directly to Clay via Settings → Connections → Add Connection. You pay those vendors directly instead of paying Clay's marked-up credit rate.
Connecting your own OpenAI or Anthropic API key brings AI enrichment clay credit cost down by 80 to 95 percent, taking per-row spend from 1 to 5 cents down to fractions of a cent.
Clay bring your own API key (BYOK) removes the data credit charge on each enrichment step, but Clay still charges an Action for executing the workflow. Both cost levers matter.
Set your API keys once at the workspace level and every table you build in that workspace will use them automatically.
Use conditional logic on enrichment columns (only run if field is empty) to stop Clay from running enrichments on rows that already have data.
Why Clay Credits Get Expensive Fast
Clay is one of the most capable tools available for building outbound infrastructure at scale. But if you are running enrichment waterfalls across large lists, the clay credit cost adds up in ways that catch most teams off guard. Deloitte found that AI has become the single fastest-growing line item in corporate technology budgets, consuming between a quarter and a half of IT spend at some firms.
Here is what is happening under the hood: when you run an enrichment inside Clay without a connected API key, Clay calls that third-party provider on your behalf and charges you a marked-up rate for the convenience. You are paying for Apollo data through Clay's pricing model, not Apollo's. The same logic applies to AI enrichments. Every Claude or GPT call you run through Clay's default setup is billed at Clay's credit rate, not Anthropic's or OpenAI's raw API rate.
The solution is connecting your own API keys. When you do, Clay routes the request through your own account at that provider. You pay the provider directly at their published rate. Clay's markup disappears entirely.
For AI enrichments, this is where the numbers become hard to ignore. Running a thousand rows through an AI enrichment step using Clay's default clay credits might cost you $30 to $50. Running the same thousand rows through your own Anthropic or OpenAI API key costs closer to $1 to $3. At 100,000 rows, that gap is the difference between a $3,000 to $5,000 bill and a $100 to $300 bill.
This is not a workaround or a loophole. Clay built this feature intentionally. It is called Bring Your Own Key (BYOK), and it is the correct way to operate Clay at any meaningful volume.
Data Credits vs. Actions: The Distinction That Matters
Before walking through the setup, there is one thing you need to understand clearly: BYOK saves you on data credits, not on Actions.
Clay has two separate cost mechanisms:
Data Credits are what you spend when Clay calls a third-party provider to fetch or enrich data, whether that is an email lookup, a phone number search, or an AI-generated field. When you connect your own API key, the data credit cost for that step drops to zero. Clay routes the call through your account instead.
Actions are what Clay charges for running the workflow itself, the orchestration cost of executing each step across each row. Connecting your own API key does not remove the Action cost. Clay still counts the workflow execution.
In practice, data credits tend to be the larger cost driver, especially for AI enrichments and multi-step waterfall lookups. So BYOK still produces meaningful savings. But go in with accurate expectations: your Clay bill will not drop to zero. The Action costs remain.
If your goal is to cut both, the answer is a combination of BYOK plus conditional logic (covered below) to reduce how many Actions Clay runs in the first place.
Step 1: Audit Your Existing Vendor Stack
Before you add a single API key to Clay, do this first: open your Clay workspace, go to Settings → Connections → Add Connection, and scroll through the full list of available integrations.
Then open your company's active software subscriptions and compare the two lists.
If you are running any kind of mature GTM motion, you will recognize a lot of names on that integration list. Tools you are already paying for. Tools your team uses every day. The opportunity here is finding the overlap. Every tool that appears in both your subscription list and Clay's connection list is an unused clay credit saving waiting to be switched on.
The highest-impact connections for most B2B sales and marketing teams are:
Data Providers
Apollo: the most common data source for SDR and BDR teams. If you have an Apollo subscription, connect it.
Better Contact: strong for mobile phone enrichment, particularly for US-based contacts.
Prospeo: a solid email finder with competitive per-credit pricing at volume.
Lead Magic: well suited for LinkedIn-based enrichment workflows.
Contact Out: a reliable option for personal email and direct phone data.
AI Models
Anthropic (Claude): the single highest-impact connection for reducing AI enrichment clay credit cost.
OpenAI (GPT-4o, GPT-4o-mini): particularly GPT-4o-mini, which is very cheap at high volumes.
If you are running email waterfall searches, phone number lookups, or contact enrichment at any scale, connecting the data providers you already pay for is the fastest way to cut your clay credit spend. In most cases, using your own API key for these providers reduces the per-row cost by 80 to 90 percent compared to Clay's default credit rate.
Step 2: Add Your Data Provider API Keys to Clay
The process is identical for every data provider. Here is how to do it at the workspace level, which is the right approach for any key you plan to use across multiple tables.
Navigate to your connections settings: go to your Clay workspace → Settings (bottom-left) → Connections → Add Connection.
Find your provider: search for the provider by name (Apollo, Better Contact, Prospeo, etc.). If it has a native Clay integration, it will appear in the results.
Retrieve your API key from the provider: log into your account at that provider. API keys are typically found under Settings → API, Developer Settings, or Integrations. Copy the key.
Paste and save in Clay: paste the API key into the designated field in Clay's connection setup. Click Test to confirm the connection is working, then click Save.
Repeat for each provider you want to connect.
Once a connection is saved at the workspace level, it becomes available as a selectable option in every enrichment step across every table in your workspace. When you add an enrichment column and select Apollo, for example, Clay will ask which connection to use. Select your own API key instead of Clay's default, and that step will bill your Apollo account directly.
For email waterfall setups specifically, where you run multiple email finders in sequence until one returns a result, connecting your own keys for each provider in the waterfall is where the savings compound. Each successful hit in the waterfall bills your provider account, not Clay's clay credits.
Step 3: Connect Your AI Model API Keys
AI enrichments are where BYOK produces the most dramatic reduction in clay credit cost. If you are using Clay to write personalized outreach copy, summarize LinkedIn profiles, score leads, or generate any kind of AI-written field at scale, this step is non-negotiable.
The math is straightforward. Using Clay's default credits for an AI enrichment step typically costs 1 to 5 cents per row depending on the model and prompt length. Using your own Anthropic or OpenAI API key for the same step costs fractions of a cent per row, often 10 to 20 times cheaper.
At 10,000 rows, that is the difference between a $100 to $500 AI enrichment run and a $5 to $50 run. At 100,000 rows, the savings are in the thousands of dollars.
The connection process mirrors the data provider setup: Settings → Connections → Add Connection → search for Anthropic or OpenAI → paste your API key → test → save.
The next section walks through the Anthropic setup in full detail, including the account funding step that most guides skip over and that will block you if you miss it.
What to Do When There's No Native Integration
Not every tool you use will appear in Clay's native connection list. That does not mean you cannot use your own API key. It means you use Clay's HTTP API enrichment instead.
The HTTP API option lets you call any external API endpoint directly from a Clay table. You configure the request (endpoint URL, headers, authentication method, request body) and map the response fields back into your table columns.
This is the approach for connecting a custom data provider, an internal database, or any API that Clay does not have a pre-built integration for. It requires more configuration than a native connection, but it works for any tool with a documented API and a standard authentication pattern.
To access it: Add Enrichment → search for HTTP API → configure your request.
The practical benefit is that you are not constrained by Clay's native integration list. If you have a vendor relationship with a data provider that is not natively supported, you can still route calls through your own account and eliminate Clay's markup entirely.
Conditional Logic: The Other Credit Drain You Are Ignoring
Connecting your own API keys addresses the data credit side of how to reduce clay credit usage. But there is a second way teams burn through credits that has nothing to do with which API key is connected: running enrichments on rows that already have the data.
If your Clay table re-runs an email enrichment on a contact who already has a verified email in that column, you have spent an Action and potentially a data credit on a step that produced no new information. Multiply that across thousands of rows and regular table refreshes, and it becomes a significant cost.
The fix is conditional logic on your enrichment columns. Most enrichment steps in Clay let you set a condition for when the step should run. The most useful condition is: only run if [field] is empty.
Set this on every enrichment column. If the email field is already populated, skip the enrichment. If the phone field already has a value, skip the lookup. Clay will not run the step, will not charge an Action, and will not touch your API credits.
This is especially important for tables that refresh on a schedule or receive new rows regularly. Without conditional logic, every refresh re-runs every enrichment on every row. With it, only new or incomplete rows get processed.
Combined with BYOK, conditional logic is how you build a Clay workflow that stays cost-efficient as it scales.
SaveClay Credits: Complete Overview
Area | What to Do | Expected Savings |
Data Providers | Connect Apollo, Better Contact, Prospeo, Lead Magic, Contact Out via Settings → Connections | 80 to 90% reduction in per-row data credit cost |
AI Enrichments | Connect Anthropic and OpenAI API keys; use your own key for all Claude and GPT enrichment steps | 80 to 95% reduction in per-row AI cost |
Anthropic Tier | Fund account with $200+ to reach Tier 3 and avoid rate limit errors at scale | Prevents failed runs on large tables |
OpenAI Model Choice | Use GPT-4o-mini for high-volume, lower-complexity tasks | Lower cost per token vs. GPT-4o |
Non-Native Tools | Use HTTP API enrichment to call any external API directly | Avoids Clay markup on unsupported tools |
Action Costs | BYOK does not eliminate Action costs — Clay still charges for workflow execution | No reduction; manage via conditional logic |
Conditional Logic | Set "only run if field is empty" on every enrichment column | Prevents redundant Actions on existing data |
Key Management | Set API keys at workspace level, not table level, for reuse across all workflows | Saves setup time; ensures consistent routing |
Security | Never share API keys; monitor account balances at each provider | Prevents unauthorized usage and service interruptions |
Watch Out: API Key Security and Account Funding
Two things will cause real problems if you skip them.
API key security: Your API keys are credentials, not just configuration settings. Anyone with access to your Anthropic or OpenAI API key can run calls that bill your account. Do not paste keys into shared documents, Slack messages, or anywhere outside of Clay's encrypted connection settings. If you suspect a key has been exposed, revoke it immediately in the provider's console and generate a new one.
In Clay, only workspace admins should have access to the Connections settings. Review who holds admin access to your workspace before adding high-value API keys.
Account funding and rate limits: The Anthropic tier system is the most common point of failure for teams going through this setup for the first time. If you fund your Anthropic account with $5 or $10 to test the connection, you will be on Tier 1 or Tier 2. When you run a Clay table with 5,000 rows, you will hit rate limits partway through and the run will fail or return incomplete results across your table.
Fund your Anthropic account with at least $200 before connecting it to Clay. This moves your account to Tier 3, which provides the rate limits and model access you need to run Clay workflows at volume without interruption. Monitor your balance at each provider regularly. If an account runs out of funds mid-run, that enrichment step will fail silently or return errors across your table.
Set up billing alerts at each provider so you are notified before balances run low.
Work With Us
Most Clay users are leaving significant money on the table. Not because they're using the wrong tools, but because their infrastructure isn't built to use those tools efficiently. Connecting your own API keys is one piece of that. Building the right waterfall logic, conditional rules, and enrichment architecture is the rest.
The GTM Engineering Company builds custom, tool-agnostic outbound infrastructure for VC-backed B2B startups. We don't sell you software. We build the system around Clay tables, enrichment waterfalls, AI enrichment workflows, CRM integrations, and we build it so you own it without vendor lock-in.
If you're spending more than you should on Clay credits, or if you're running Clay workflows that aren't producing the output quality you need, that's an infrastructure problem. We fix infrastructure problems.
This is the right fit if you're a technical founder, GTM leader, or RevOps professional who wants a production-grade outbound system, not a template. Feel free to book a strategy call.
Frequently Asked Questions (FAQs)
What is the Clay API and how does it help with saving clay credits?
The Clay API connection feature, also referred to as Bring Your Own Key (BYOK), lets you connect your own accounts at third-party providers like Apollo, Anthropic, or OpenAI directly to your Clay workspace. When you run an enrichment step using your own API key, Clay routes the request through your provider account and bills that provider directly, instead of charging you Clay's marked-up clay credit rate. This can reduce the clay credit cost of data and AI enrichment steps by 80 to 95 percent depending on the provider and use case. The clay api documentation covers the connection setup process under Workspace Settings → Connections.
Does using my own API key in Clay eliminate all clay credit costs?
Using your own API key in Clay eliminates the data credit cost for enrichment steps, but it does not eliminate Action costs. Clay charges Actions for running the workflow itself. BYOK removes the markup on the data or AI call, but Clay still counts the Action for executing that step. To reduce Action costs, use conditional logic on your enrichment columns so steps only run when needed, for example only when a field is empty.
Which Clay connections save the most clay credits?
The highest-impact connections for clay credit savings are AI model keys (Anthropic and OpenAI) and high-volume data providers. Connecting your own Anthropic or OpenAI API key typically saves 80 to 95 percent on AI enrichment costs, bringing per-row costs down from 1 to 5 cents to fractions of a cent. For data providers, connecting Apollo, Better Contact, Prospeo, Lead Magic, or Contact Out saves 80 to 90 percent on email and phone enrichment costs compared to Clay's default credit rate.
How do I add my own API key to Clay?
To add your own API key to Clay, go to your workspace Settings → Connections → Add Connection. Search for the provider you want to connect (Apollo, Anthropic, OpenAI, etc.), retrieve your API key from that provider's account settings, paste it into Clay's connection field, click Test to verify the connection, and click Save. Setting the key at the workspace level makes it available across all tables in your workspace. When you add an enrichment column, select your own API key as the connection rather than Clay's default, and that step will bill your account at the provider directly.
How much should I fund my Anthropic account before connecting it to Clay?
Fund your Anthropic account with at least $200 before connecting it to Clay. Anthropic uses a tiered access system where Tier 1 and Tier 2 accounts have rate limits that will cause enrichment runs to fail when processing large Clay tables. Depositing $200 moves your account to Tier 3, which provides higher rate limits and full model access. Starting with a smaller amount under $50 will very likely result in rate limit errors mid-run when processing tables with thousands of rows.
Can I use my own API key for tools that do not have a native Clay integration?
Yes. For tools without a native Clay integration, use Clay's HTTP API enrichment option. Go to Add Enrichment → search for HTTP API, then configure the request with your endpoint URL, authentication headers, and request body. Map the response fields back into your table columns. This approach works for any tool with a documented API, so you are not limited to Clay's native integration list. The HTTP API route requires more manual configuration than a native connection but gives you the same ability to route calls through your own account and avoid Clay's markup.
Does Clay bring your own API key work for email waterfall searches?
Yes, clay bring your own API key works for email waterfall searches and is one of the highest-value places to apply it. In a waterfall setup, Clay runs multiple email finders in sequence until one returns a verified result. If you connect your own API keys for each provider in the waterfall (Apollo, Prospeo, Better Contact, etc.), each successful hit bills your provider account directly instead of consuming Clay's data credits. The savings compound across each step in the waterfall, particularly on large lists where many rows require multiple lookup attempts before a result is found.
Will connecting my own API key slow down my Clay enrichment runs?
Connecting your own API key does not meaningfully slow down Clay enrichment runs under normal conditions. The primary factor affecting run speed is your API tier at the provider. Lower tiers have stricter rate limits, which can cause Clay to throttle or pause mid-run. This is why funding your Anthropic account to Tier 3 ($200 or more) matters in practice. At Tier 3, rate limits are high enough that most Clay table sizes will run without interruption. OpenAI's rate limits vary by model; GPT-4o-mini has generous limits that are well suited to high-volume Clay workflows.
Is it safe to add my API keys to Clay?
Adding API keys to Clay is safe when handled correctly. Clay stores connection credentials in encrypted workspace settings, not in plain text. The risk comes from who has access to your Clay workspace. Anyone with admin access can view and use connected API keys. Limit admin access to trusted team members, never share API keys outside of Clay's connection settings, and set up billing alerts at each provider so you are notified of unexpected usage. If you suspect a key has been compromised, revoke it immediately in the provider's console and generate a new one before reconnecting.
