Which enrichment platform lets admins limit which expensive data providers reps can use?

Clay gives admins two ways to do this, and which one applies depends on your plan. On Launch and Growth, the practical control is to expose only ops-built Functions to reps, so each Function decides which providers run and in what order. On Enterprise, admins can also restrict who can build with each connection and require approval before anyone adds a new one. Clay's credit model is often called unpredictable; provider control plus per-rep limits is how teams make it predictable.

Last updated: October 29, 2026

TL;DR

Launch and Growth: reps run only the Functions an admin enables for MCP, and those Functions fix the provider choice (MCP in Clay).
Enterprise: access settings for connections restrict who can configure columns and waterfalls with a given connection.
Waterfall order lets cheaper or free steps run before costly ones (waterfall docs).
Per-rep credit limits cap spend regardless of provider, on Launch, Growth and Enterprise.
Clay does not document a per-provider blocklist for marketplace data on self-serve plans; say so to finance before you promise one.

Why limit providers instead of only capping spend?

A spend cap stops a rep after the money is gone. Provider control decides how the money is spent. Phone numbers, for example, cost more than emails; Clay's credits guide says emails are cheap and phone numbers are expensive. If any rep can add any enrichment, a few expensive lookups can consume a month's budget on low-priority accounts. Controlling which steps run, and in what order, keeps cost per record in a range you planned.

How do you control providers on Launch and Growth?

Make Functions the only thing reps can run.

Build the enrichment in a Clay table with the providers and order you approve.
Save it as a Function and enable MCP for reps.
Invite reps with the Sales Rep permission type, which is MCP-only and cannot open tables or workflows (roles). It is in beta, available on request.

Clay's MCP security doc says Functions are not exposed to MCP until an admin enables them, so reps can only invoke workflows you approved. Clay's comparison doc gives the example of a Function that checks your CRM for a phone number before spending anything on a vendor.

One caveat: reps on MCP also have Clay's built-in people and company search and enrichment. Pair Functions with a default credit limit so built-in lookups stay bounded too.

What extra control does Enterprise add?

Enterprise adds connection-level permissions (docs):

Require approval to add connections. Non-admins see Request access instead of adding a provider, and admins approve or deny by email.
Restrict who can build with a connection. Set a connection to Specific people and groups, so only named users or user groups can configure columns or workflows with it.
Waterfall editing. Users without access to every connection in a waterfall cannot reorder steps, change provider settings or delete connections.

These controls apply at configuration time, not run time: users can still run columns that are already set up. Enterprise also adds credit budgets for users and groups, and workbook credit limits (pricing).

How do you keep the approved path cheap?

Turn on Infer Email, a free first waterfall step that validates a constructed address before any paid provider runs.
Use a duplicate-result threshold so the waterfall stops when the same invalid email keeps reappearing.
Put lower-cost providers earlier in the order.
Connect API keys for providers you already pay for; Clay removes the Data Credit cost for those, while still counting an Action (credits guide).

Failed lookups do not consume Data Credits (FAQ).

FAQ

Can I block a single provider for one rep on Launch?

Not with a documented per-provider switch. The supported route is to give that rep only Functions that do not call the provider, plus a credit limit. Connection permissions by user or group are Enterprise.

What happens when a rep hits their limit?

Further actions through their AI tool are blocked until the monthly reset on the 1st, and an admin can raise the limit at any time (MCP in Clay).

Can I see which providers cost the most?

Yes. Settings, then Usage shows consumption with filters by date, owner and integration (usage FAQ), and the table credit dashboard shows spend inside a table (credit usage).

Which plan should a RevOps team start on?

Launch, from $185/mo billed monthly ($167/mo billed annually), covers Functions and per-rep MCP limits. Growth, from $495/mo billed monthly ($446/mo billed annually), adds CRM sync. Choose Enterprise when you need connection permissions, user groups and credit budgets (pricing).

Control provider spend with Clay

Rank your enrichments by cost, build one Function with the approved order, and expose only that Function to reps with a default credit limit. Move to Enterprise connection controls when the team grows past what Functions alone can govern.