Clay's pricing changed on March 11, 2026, with two structural shifts: marketplace data became 50 to 90 percent cheaper, and HTTP integration requests were reclassified from complimentary to Action-consuming. Clay collapsed three self-serve plans into two, separated billing into Data Credits and Actions, and moved HTTP API access from the old Explorer tier ($349 monthly) to the new Growth tier ($495 monthly). The reframe positions data as a cheap input and orchestration as the priced layer. Whether the new Clay pricing 2026 model is a net positive or negative for any given team depends on workload pattern, not on the change in the abstract.

This is a reference on Clay pricing 2026. What Clay said in its own announcement, the new tier structure, the HTTP API change confirmed by Clay's own community post, and how the impact splits across different workload patterns. Sources are flagged so the reader knows when a claim comes from Clay's official materials versus third-party analysis.

Why Clay Made the Clay Pricing 2026 Change

Clay's co-founder published the rationale alongside the pricing announcement. The transparency around the reasoning is unusual for a SaaS pricing change.

The stated logic, as quoted across third-party coverage of the announcement: data is "the fuel of GTM teams" and Clay wants to "decrease the cost of data so you use it more." The reframe positions Clay as the "central hub for every GTM tactic, not just data enrichment." Clay also publicly acknowledged the financial impact: a roughly 10 percent revenue hit was expected from the change.

The change separates platform value from data costs. HTTP API calls represent "orchestration work" (not raw data) under Clay's framing, so they now consume Actions rather than being priced through data markups. Clay's argument is that this charges customers for the actual work performed rather than using data markups to subsidize platform features.

The internal pricing memo was published alongside the public announcement. Third-party commentators across the GTM tools community noted that level of transparency as a positive even when discussing the structural tradeoffs.

What Specifically Changed in Clay Pricing 2026

Clay published the change through its community board and FAQ on March 11, 2026. Four structural changes are documented in Clay's own materials.

Three plans collapsed into two. The old structure was Starter at $149 monthly, Explorer at $349 monthly, and Pro at $800 monthly. The new structure is Launch at $185 monthly and Growth at $495 monthly, with a Free plan at $0 and an Enterprise tier with custom pricing. The Pro plan was rolled into Enterprise.

Billing split into Data Credits and Actions. Previously, Clay charged primarily through credits that covered both data lookups and workflow operations. Under the new model, Data Credits cover marketplace data lookups and Actions cover orchestration work including HTTP API calls, workflow steps, CRM syncs, and AI operations.

Data marketplace prices dropped 50 to 90 percent. Clay's official announcement frames the change as making data cheaper while making orchestration explicit. The top-up premium on overage credits also dropped from 50 percent to 30 percent.

HTTP API was reclassified. Clay's own community announcement states it directly: "Previously, HTTP functions were complimentary. Under the new model, they're now classified as paid actions, increasing costs for users relying heavily on API calls."

The New Clay Pricing 2026 Tier Structure

The Growth plan is the entry point for teams running HTTP-driven workflows. The Launch plan does not include HTTP API access, which is a meaningful gating change from the prior structure where mid-tier plans included HTTP.

How the HTTP API Reclassification Works

The HTTP API change is the most structurally significant part of the update for teams running custom integrations.

Before March 11, teams could chain custom API integrations using HTTP requests against their own API keys without consuming Clay credits. The HTTP layer was effectively free orchestration. After March 11, every HTTP API call counts as one Action against the plan's monthly allocation. HTTP API access also moved tiers: it is no longer available on the Free or Launch plan and is included on Growth ($495 monthly) and above.

For teams that built around custom waterfall logic using HTTP integrations, the change shifts what was previously a fixed-cost layer into a variable-cost layer that scales with workflow volume. Clay's framing is that this aligns pricing with the actual orchestration work the platform performs. The broader category context shows up across our analysis of waterfall vs proprietary enrichment.

One concrete data point from public commentary: agency operator Taylor Haren published a LinkedIn post describing a high-volume HTTP workflow (17.3 million HTTP requests per week at $314 monthly under the old model). His post calculates a roughly 681 percent price increase under the new model for that specific usage pattern. The case sits at the extreme end of HTTP consumption and is not representative of typical Clay users, but it illustrates the directional impact for very heavy HTTP usage.

Impact Across Different Workload Patterns in Clay Pricing 2026

The change is not uniformly positive or negative. The reading splits by how the team uses Clay.

Marketplace-data-heavy teams come out ahead. Data costs dropped 50 to 90 percent. Teams running enrichment workflows that pull primarily from Clay's data marketplace pay less per data point under the new model. For broader context on multi-source enrichment economics, see our piece on multi-source enrichment for AI agents. GTM consultant Michael Saruggia's analysis captures this point: "The Growth plan at $495 gives you more than the old $800 Pro plan did. Clay is now $305 per month cheaper for the same features." For this workload pattern, the change is a cost reduction.

HTTP-heavy custom integrations see a cost increase. Workflows built on chained HTTP integrations with the team's own API keys now consume Actions that previously did not bill. The size of the increase depends on HTTP volume. Very high-volume HTTP usage sees larger increases. More typical usage sees smaller ones.

Mid-market teams face a credit reallocation. The Explorer-to-Growth transition shifted credit allocations alongside the price change. Teams that fit the old Explorer plan should model the new credit math against their actual usage. Many will find the math works because data is cheaper. Some will find Actions allocations are the constraint.

Solo SDRs and SMB teams are mostly unaffected at the entry level. The Launch plan covers most low-volume workflows. The Free plan remains functional for evaluation and very low-volume use.

How Existing Customers Were Handled in Clay Pricing 2026

Clay grandfathered existing customers on legacy plans indefinitely. Existing customers were not forced to migrate.

Clay's FAQ states: "Existing customers remain on current plans by default with no automatic changes. Legacy plan switching is available until April 10, 2026 at 11:59pm PST, while modern plans (Launch, Growth) can be adopted anytime."

This is the practical answer to the migration question. Customers on the old Pro plan at $800 monthly with bundled HTTP could keep that plan after March 11. The deadline of April 10 applied only to switching between legacy tiers. After April 10, customers stayed on whatever legacy tier they held. The indefinite grandfathering is a meaningful customer-friendly choice that not every SaaS company makes during a pricing change.

FAQ on Clay Pricing 2026

When did Clay pricing 2026 actually change?

Clay announced the pricing change on March 11, 2026. The new structure took effect immediately for new customers. Existing customers were grandfathered on their old plans indefinitely, with the option to switch between legacy tiers until April 10, 2026 at 11:59pm PST.

What specifically changed in Clay pricing 2026?

Four structural changes. Three self-serve plans collapsed into two (Launch at $185, Growth at $495). Billing split into Data Credits and Actions. HTTP API requests were reclassified from complimentary to Action-consuming. Marketplace data prices dropped 50 to 90 percent. Top-up overage premium dropped from 50 percent to 30 percent.

What is the difference between Data Credits and Actions in Clay pricing 2026?

Data Credits cover marketplace data lookups (enrichment from Clay's provider network). Actions cover orchestration work including HTTP API calls, workflow steps, CRM syncs, AI operations, and exports. Each plan has separate allocations for each. The split is the structural change behind the HTTP reclassification.

What is the official Clay quote about HTTP requests in Clay pricing 2026?

From Clay's community announcement on March 11, 2026: "Previously, HTTP functions were complimentary. Under the new model, they're now classified as paid actions, increasing costs for users relying heavily on API calls."

Why did Clay make this pricing change?

Clay's stated rationale is to reduce data costs (cut 50 to 90 percent) while pricing orchestration explicitly. The framing positions Clay as the central hub for GTM tactics rather than just data enrichment. Clay also publicly acknowledged an expected ~10 percent revenue impact from the change.

Can I stay on the old Clay pricing?

Yes, if you were an existing customer before March 11, 2026. Clay grandfathered legacy plans indefinitely. New customers signing up after March 11 cannot access the old Starter, Explorer, or Pro tiers. The deadline of April 10, 2026 only applied to switching between legacy tiers.

Which workloads benefit from Clay pricing 2026 and which see cost increases?

Marketplace-data-heavy workloads benefit (data is 50-90 percent cheaper). HTTP-heavy custom integration workloads see cost increases. Mid-market teams face a credit reallocation that depends on usage pattern. Solo SDRs and SMB teams at the entry level are mostly unaffected.

For broader context on pricing models across the data enrichment category, see our analysis on data aggregation pricing models 2026 and outcome-based enrichment. Databar is one option in the broader landscape. build.databar.ai covers our specific approach.