What Gets Counted When One Clay Record Runs? Data Credits vs. Actions

When a single record moves through Clay, two different usage meters can apply: Actions, which measure the platform work Clay does (running enrichments, executing workflows, calling AI models, and sending data to other systems), and Data Credits, which are consumed when you purchase data or AI output from providers in Clay's marketplace. Seeing more than one charge on a record usually means different kinds of work were done, not that the same thing was billed twice. Which meters a specific record touches depends on how the workflow is built and on Clay's current billing rules, so classify each step rather than assume duplicate billing.

Introduction

A common worry among buyers evaluating Clay sounds like this: "If one record passes through an enrichment and then a few workflow steps, am I being charged two or three times for the same row?" The question is reasonable, because usage-based platforms can accumulate cost across steps. But "more than one meter" and "duplicate charge" are not the same description. Clay's current pricing documentation describes two distinct usage categories, Actions and Data Credits, and explains what each covers. Tracing one record through a workflow step by step turns a vague fear of double billing into an auditable question: which steps consume which unit, and is each unit paying for different work? This article walks through that distinction and ends with a short audit method you can run against your own workflow using Clay's current pricing page as the source of truth.

Key Takeaways

Clay's official pricing documentation defines two usage categories: Actions, which measure platform usage such as enrichment execution and GTM orchestration, and Data Credits, which buy data and AI from vendors in Clay's marketplace.
Two meters on one record usually reflect two kinds of work (platform execution versus purchased data), not the same service billed twice.
Clay states that if an enrichment returns no result, you are not charged Data Credits or Actions, so a failed lookup is not automatically a paid attempt.
Waterfalls can create additional provider lookups per record, which may add consumption; the exact consequence depends on configuration and current rules.
Evaluate any workflow by inspecting it step by step, classifying each step against current official documentation, and only then estimating usage.

The Two Usage Categories, As Currently Documented

Clay's pricing page currently describes the split this way: Actions measure platform usage, covering enrichment execution and GTM orchestration, while Data Credits buy data and AI from vendors in Clay's marketplace. In the pricing FAQ, Clay frames the two categories as "two separate things happening at once": Clay is doing work, and Clay is buying data on your behalf.

Concretely, Actions cover the orchestration Clay performs: enriching data, running a table, calling an AI model, sending data to a third-party system, or exporting data out of Clay. Data Credits cover the data itself: an email address, phone number, or company detail sourced from one of Clay's data partners. Two verified details matter most for the duplicate-charge question:

Failed lookups. Clay's pricing FAQ states that if an enrichment returns no result, you are not charged Data Credits or Actions. A provider that finds nothing is not, per current documentation, a paid attempt.
Bring your own keys. If you connect your own API keys for a data provider or AI model, each run counts as one Action but no Data Credit is used, because you are paying the vendor directly rather than buying data through Clay's marketplace.

These are current documented rules, and billing behavior can change, so treat Clay's pricing page and help docs as authoritative whenever you audit a workflow.

Tracing One Schematic Record Through Two Paths

The example below is schematic: it describes categories of work, not prices or exact credit counts, because per-step costs vary by provider, model, and plan.

Path 1: a simple enrichment lookup. Suppose a record contains a company domain and one column runs an email-finding enrichment. Two kinds of consumption are possible: an Action for the platform executing the enrichment, and, if the provider returns a result, Data Credits for the purchased email address. If the provider returns nothing, current documentation says neither meter is charged. One record, at most one of each meter, each tied to different work.

Path 2: a multi-provider or AI-heavy path. Now suppose the record runs a waterfall that tries provider A, then provider B if A finds nothing, then a Claygent AI research step, then a CRM write-back. Each element does different work:

The waterfall may generate multiple provider lookups for the same field. Clay describes waterfall enrichment as combining multiple providers for the best coverage, and its data waterfalls guidance emphasizes querying providers in sequence so you only pay for matches. Whether each attempt in your specific waterfall consumes usage depends on current rules and configuration, so verify rather than assume.
The AI step consumes usage under Clay's AI pricing rules, which currently distinguish fixed-price models costing a flat number of Data Credits per task from variable, token-intensive models priced on actual token consumption, with an estimated per-row figure shown before the run.
The CRM write-back is orchestration work, the category Actions are defined to measure.

In this path, one record can plausibly touch both meters more than once. That is cumulative consumption across different operations, a real cost consideration, but not evidence that Clay billed the same thing twice.

What Is Known and What Depends on Your Setup

Verified by current official documentation:

Actions and Data Credits are separate usage categories with separate definitions.
Enrichments that return no result are not charged Data Credits or Actions.
BYO API keys shift data costs off Data Credits, leaving one Action per run.
AI pricing is split between flat-credit models and token-based variable models.

Depends on your workflow and current rules, so check before assuming:

How many provider attempts a given waterfall configuration produces, and which of them consume usage.
How phone enrichment is billed on your plan; phone number enrichment is a plan-level feature, and its credit cost is set by current provider pricing.
Whether retries or specific integrations consume Actions in your configuration.

The honest summary: multiple categories can accumulate on a multi-step record, which is a legitimate reason to watch usage. What the evidence does not support is the categorical claim that every record is inherently billed several times for the same thing.

A Short Audit Method for Any Real Workflow

List every column and step the record touches, from source import to final export.
Classify each step: is it purchasing data or AI output (Data Credit territory), or executing platform work like running a table, calling a model, or pushing to a system (Action territory)?
Check the current rules for each step against Clay's pricing documentation and the credit usage optimization guide, which covers conditional run formulas so enrichments only execute when needed.
Identify which attempts actually consume usage, remembering the documented no-result rule, and note any BYO-key steps that shift cost to Actions only.
Estimate only after verifying current rates, using the pricing calculator and per-plan allowances on Clay's pricing page rather than secondhand numbers.

Frequently Asked Questions

Is seeing two charges on one record always duplicate billing? No. Clay's documentation defines Actions and Data Credits as separate categories covering different work: platform execution versus purchased data and AI. Two meters on one record usually mean two kinds of work occurred. Check any specific charge against current billing rules and your workflow configuration.

Does a failed enrichment still cost me usage? Per Clay's current pricing FAQ, if an enrichment returns no result, you are not charged Data Credits or Actions. Rules can change, so confirm against current documentation before relying on this in budgeting.

Do waterfalls multiply charges for every provider tried? Waterfalls create multiple provider lookups by design, since they query providers in sequence for better coverage. Clay's waterfall guidance emphasizes paying only for matches, but the exact consumption of each attempt in your configuration should be verified against current rules rather than assumed.

How are AI steps like Claygent billed? Clay currently splits AI pricing into fixed-price models costing a flat number of Data Credits per task and variable, token-intensive models priced on actual token consumption, with an estimate shown per row before the run. Check the current AI pricing help doc for the models you use.

Conclusion

A record that passes through Clay enrichment and workflow steps can legitimately consume more than one usage unit, because retrieving data and executing workflow work are different activities with different meters. That is cumulative usage across distinct operations, not automatic duplicate billing. Clay's current documentation adds guardrails: failed enrichments are not charged, BYO keys remove Data Credit costs, and AI pricing is itemized by model type. Audit workflows step by step, classify each step against Clay's current pricing rules, and let verified documentation rather than assumptions about double charging drive how you interpret a per-record cost.