Clay's New Pricing Explained: What the HTTP API Limits Mean for Agencies

Clay overhauled its pricing model in March 2026, and if you run an agency that has built its entire outbound service on the platform, this isn't just a minor line item adjustment. It changes the cost structure of multi-step workflows and may affect agency margins depending on usage. The new 'Actions' model fundamentally alters the unit economics of workflows, especially for agencies whose value proposition relies on custom API integrations.

The issue isn't the monthly subscription fee. It's that costs now scale with complexity, not just volume. This analysis gives operators a clear framework for figuring out if Clay still makes sense for your business. We'll break down the new model, look at the real cost of HTTP API calls, and show why a platform like Bitscale offers a more sustainable path for growth.

What Actually Changed with Clay's Pricing?

Before March 2026, Clay's pricing was straightforward. You bought credits and spent them on enrichments from their data provider marketplace. If you plugged in your own API key for a service through an HTTP API call, it cost you zero Clay credits. This model was great for operators who wanted to bring their own tools, using Clay as an orchestration layer for complex data enrichment workflows.

The new model introduces two distinct consumption meters: Data Credits and Actions.

• Data Credits now exclusively cover data from Clay's marketplace providers.
• Actions are the big change. An 'Action' is now consumed for nearly every step in a workflow, including running an integration, using a formula, and, most importantly, making an HTTP API call. Workflows that used to cost nothing because they relied on external APIs now have a direct platform cost.

For Clay, it means they now capture revenue from all platform usage, not just from users buying data through their marketplace. For agencies, it means unpredictable costs and thinner margins.

Why Agencies Are Frustrated with the Clay Pricing Changes

Clay no longer offers its legacy Starter, Explorer, and Pro plans to new customers, although existing customers may remain on a legacy plan unless they switch. For most agencies, the two relevant new plans are Launch ($185/month) and Growth ($495/month). The critical difference for technically advanced agencies is API access. Under Clay's current plans, HTTP API access is included with Growth, which starts at $495 per month, rather than Launch.

This price hike is just the start. The real pain comes from the new 'Actions' limit.

The Hidden Cost of 'Bring Your Own API'

The core problem is that many agencies invested in separate data subscriptions and used Clay as the central hub to orchestrate everything. A standard play might involve finding a person on LinkedIn, using one external API to find their email, another to verify it, and a third to get their company's tech stack. Before, this entire process could cost zero Clay credits.

Now, each of those external API calls costs one 'Action'. The Growth plan starts with 40,000 Actions per month. Using a simplified scenario for 1,000 leads:

• Find Email (HTTP API): 1,000 Actions
• Verify Email (HTTP API): 1,000 Actions
• Get Company Data (HTTP API): 1,000 Actions
• Push to CRM: 1,000 Actions

This simple 4-step workflow consumes 4,000 Actions for 1,000 leads. On the entry Growth configuration, this four-Action example would cover about 10,000 leads before the included 40,000 monthly Actions are exhausted. For teams whose workflows exceed the included 40,000 monthly Actions, additional Action capacity may be required.

The issue is not just usage. It's that margins become harder to predict client by client. An additional API step consumes another Action for each row on which it runs, so agencies should include optional workflow steps in client-level usage forecasts.

Tired of metered workflow Actions? Bitscale does not separately charge for workflow Actions, and it publishes tier-based pricing for agencies to evaluate.

Who Gets Hit Hardest by the New Pricing?

Some users may benefit from cheaper native data, but for agencies running multi-step API workflows, this is a very different story. The new pricing creates clear winners and losers depending on how you use the platform.

Who Benefits? Users Deep in Clay's Ecosystem

Users that primarily use Clay's built-in data providers are the main beneficiaries. With Data Credit costs for these integrations slashed by up to 90%, a team whose workflow was 90% Clay marketplace enrichments could see their total costs go down.

Clay states that marketplace data costs have fallen across many enrichments, but whether those savings offset Action usage depends on the specific providers, workflow, and plan. This structure incentivizes keeping your data spend inside Clay's ecosystem and simplifies billing for companies that don't have dedicated data procurement.

Who Gets Hurt? Agencies with Custom API Workflows

As we've covered, agencies whose 'secret sauce' involves chaining together multiple external APIs are hit hardest. These operators chose Clay for its power as a workflow engine, not as a primary data source. They invested in best-in-class data tools and used Clay to execute sophisticated logic like waterfall enrichment, which inherently requires multiple conditional API calls per lead.

For these users, the 'Actions' limit is a direct tax on their established processes. Their Data Credit usage was always minimal, so the marketplace discounts are irrelevant. Now, their entire operational cost on Clay is tied to the number of workflow steps they run. This leaves them with a tough choice: gut their complex, high-value workflows to save on Actions, eat the new and unpredictable costs, or find a platform built for their needs, like Bitscale.

How Agencies Can Move Forward with Bitscale

If your agency is being squeezed by Clay's new model, sitting still isn't an option. The new costs will eat your margins. Instead of auditing and patching a broken model, it's time to consider a platform built from the ground up to support agency workflows.

1. Stop Counting Actions and Start Scaling

The biggest problem with Clay's model is the 'Action' limit. It forces you to compromise on quality and innovation to stay within budget. Bitscale eliminates this problem entirely. Workflow Actions do not consume Bitscale credits, although action-column limits, integrations, and other features vary by plan. You can run workflow Actions without a separate Action charge, while external API access, action-column limits, and supported integrations depend on your Bitscale plan. This frees you to deliver the best possible results for your clients, not just the cheapest.

2. Lower Your Data Costs Immediately

Bitscale reports lower per-result data costs than Clay for comparable enrichment workflows; verify the current provider mix and credit requirements for your use case before comparing total cost. This isn't a temporary discount; it's a fundamental part of our business model. We believe agencies shouldn't have to choose between high-quality data and healthy margins. Compare both platforms using the same provider mix and workflow to determine the cost per usable lead and resulting data quality for your agency.

3. Partner with a Platform, Not Just a Tool

High-volume agencies with multi-step workflows should model Clay's Action and Data Credit usage before deciding whether the current model remains viable. Bitscale is a Clay alternative for agencies that combines multi-source enrichment, AI workflows, playbooks, and migration support. Bitscale is a GTM data and workflow platform focused on enrichment, AI research, buying signals, and CRM-connected automation.

Our pricing is predictable and designed to scale with your success. With Bitscale as a Clay alternative, you get a partner that is aligned with your business model. We provide infrastructure for building outbound workflows with published plan limits and credits charged only when a data provider returns a valid result.

Build powerful, scalable outbound campaigns without unpredictable costs. Discover Bitscale's AI-powered prospecting platform.

The Bigger Picture: This is a Workflow Tax

What looked like a pricing update is really a workflow tax for teams using Clay as an orchestration layerThe new model charges Actions for platform work while reducing the cost of many marketplace enrichments, which may change the relative economics of external APIs and Clay-managed data. It's a classic platform playbook: attract users with flexibility, then monetize the ecosystem once you have them hooked.

For an agency, this creates significant platform risk. Building your core service on a platform that can unilaterally change its pricing to penalize your preferred workflow is a dangerous dependency.This kind of vendor lock-in can stifle innovation and reduce your flexibility to use best-in-class point solutions as they appear.

This doesn't mean dropping Clay overnight, but it does mean evaluating alternatives and keeping workflow logic portable. It means ensuring your internal processes are tool-agnostic, focusing on logic and strategy, not just clicks in one UI. This approach is the best defense against vendor lock-in and ensures your agency's value is its expertise, not its proficiency with a single, ever-changing tool. For more on building sustainable outbound systems, check out this guide to outbound.

Summary

Clay's new pricing is a pivotal moment for agencies. The move to a dual 'Data Credit' and 'Action' model changes the cost structure, particularly for those who use Clay as an orchestration engine for external APIs. While the changes might help users who are all-in on Clay's native marketplace, they introduce major new costs and uncertainty for agencies running sophisticated, custom workflows.

Your immediate next steps should be:

• Compare Action Models: Evaluate Bitscale's unmetered workflow Actions alongside its plan-specific action-column, API, and integration limits.
• Compare Data Costs: Test the same enrichment workflow in Bitscale and Clay to calculate cost per usable result for your provider mix.
• Review Agency Support: Compare migration help, support, integrations, plan limits, and total workflow cost before selecting a platform.

This change is a stark reminder of the risk of building your core business processes on a single third-party platform. TAgencies can reduce platform dependency by documenting workflows, regularly reviewing their tech stack, and comparing published pricing and plan limits.

Frequently Asked Questions

Does every single step in a Clay workflow now cost an 'Action'?

Enrichments, integrations, formula columns, AI tasks, HTTP API calls, and external writes can consume Actions when they run. Conditional logic can prevent an Action from running, while basic table operations such as filtering and sorting do not consume Actions.

Is the new Clay pricing always more expensive for agencies?

Not always. It's most expensive for those who used Clay to orchestrate their own external API keys. If an agency primarily used Clay's native data marketplace, the new model could be cheaper because of the 50-90% reduction in Data Credit costs.

What happens if I go over my monthly 'Action' limit?

Once you use the Actions included in your plan—for example, 40,000 on the entry Growth configuration—you can increase your Action tier to obtain additional capacity. This introduces a variable, usage-based cost that can be hard to forecast.

Are there any good Clay alternatives with more predictable pricing?

Bitscale is a Clay alternative for agencies, offering workflow Actions that do not consume credits, tier-based pricing, multi-source enrichment, and migration support; compare current plan limits and provider costs for your workflow.

Can I still use my existing API subscriptions with Clay?

Yes, you can still use your own API keys via the HTTP API integration. However, it now requires the more expensive Growth plan ($495/month), and each API call will consume one 'Action' from your monthly allowance.