BYOK Enrichment Explained: Use Your Own API Keys to Cut Enrichment Costs

If you're already paying for enrichment providers, the real question is simple: do you also need to pay a platform to resell those same lookups back to you?

That is the appeal of BYOK enrichment. You connect your own provider accounts, the platform runs the waterfall, and you pay providers directly instead of buying everything through a bundled credit model.

The workflow does not really change. The economics do. And if you run enrichment at real volume, that difference adds up fast.

What BYOK Enrichment Actually Means

BYOK stands for Bring Your Own Keys.

In a managed setup, the platform owns the provider accounts. You buy credits from the platform, the platform decides how the underlying calls are made, and you live inside that pricing model.

In a BYOK setup, you plug in your own provider API keys. The platform still gives you the interface, the waterfall logic, and the execution layer. The difference is that the calls run on your credentials, not theirs.

That changes three practical things:

1. Billing visibility: you can see what you're paying at the provider level.
2. Routing control: you can decide which providers belong in your sequence.
3. Margin profile: you avoid paying markup on top of provider rates when the platform supports BYOK cleanly.

That is the cleanest way to think about it:

Why BYOK Changes the Cost Equation

Most teams do not move to BYOK because they want a different workflow. They move because they are tired of paying markup on top of provider costs they could manage directly.

If you already pay for providers like Hunter, Prospeo, or Findymail, a managed platform can end up feeling like an extra billing layer. The orchestration is still useful. The markup is the part people start questioning.

That becomes more obvious when any of these are true:

• You enrich larger volumes every month.
• You manage multiple client workspaces or billing entities.
• You already know which providers fit your ICP.
• You want to mix direct provider accounts with aggregator-style providers inside one sequence.

At low volume, this is less dramatic. Managed pricing can still be the right call when you want the fastest start, do not want to open multiple vendor accounts, or are still figuring out whether enrichment matters enough to optimize.

For most teams, the decision is not "BYOK forever" versus "managed forever." It is when direct provider billing becomes worth the extra setup.

When BYOK Usually Makes Sense

BYOK tends to be strongest in three situations.

Agencies Running Multi-Client Workflows

Agencies usually feel the BYOK benefit first. If each client has different provider preferences, separate keys, or a different tolerance for cost versus coverage, BYOK is easier to reason about operationally.

Instead of pushing every client through one managed credit pool, you can keep billing closer to the underlying providers and tune provider order by segment.

Technical GTM Teams

If your team already works in APIs, automation, or custom RevOps systems, BYOK usually feels natural. You already manage credentials, vendors, and workflow logic elsewhere.

Clay's current FAQ makes the same point from a different angle. Clay says you can use existing enrichment subscriptions inside its workflow layer "free of cost," and it also notes that private API keys reduce the data credits you spend. That is the core BYOK logic in plain terms: keep the workflow layer, cut unnecessary credit usage.

The operational difference is how reusable that setup is. Clay's docs do support waterfall templates, but they are still created from within a table and Clay notes that those templates cannot be edited after creation. If your team wants a reusable enrichment config that behaves more like a product-level setting than a table artifact, that is a real distinction. See Clay's BYOK FAQ, Clay's pricing and credits FAQ, and Clay's waterfall docs.

Cost-Conscious Teams Past the Trial Phase

Once enrichment becomes part of your core outbound system, convenience stops being the only thing that matters. You start caring about repeatability, provider fit, and unit economics.

That is usually when BYOK stops feeling optional.

BYOK Is Not the Same as "Cheapest Possible"

One important caveat: BYOK does not automatically mean lowest total cost.

It does not.

What it lowers is reseller markup. It does not eliminate:

• Provider subscription costs
• Minimum commitments
• Operational overhead from managing more vendor accounts
• Sequence design mistakes
• Paying for providers that do not fit your market

If your provider mix is wrong, BYOK can still be expensive. You are just paying with more visibility.

That is why the best BYOK setup is not "connect every provider." It is usually:

• choose providers that fit your market,
• order them based on expected marginal value,
• and review step-level outcomes often.

If you need the waterfall model behind that thinking, start with Waterfall Enrichment: How It Works, Costs, and Provider Order and Email Enrichment Cost Model: Expected Cost per Enriched Contact.

How LeadModule Handles BYOK

LeadModule is built around a simple idea: orchestration and provider spend should be separate decisions.

The current public pricing on the marketing site includes BYOK on both plans:

• Free: $0, BYOK, API access, and 1 waterfall config
• Starter: $49/month, BYOK, API access, 250 credits/month, and unlimited configs

That matters because you can use the workflow layer without being forced into managed credits first.

In the current product, LeadModule supports BYOK across eight enrichment providers:

• Prospeo
• Findymail
• LeadMagic
• Hunter
• Dropcontact
• BetterContact
• FullEnrich
• Wiza

It also supports mixed waterfall behavior. In practice, that means you can combine direct providers with aggregator-style providers in one config, then tune the order based on what actually works for your list.

There is a second operational benefit here too: some providers return immediately and others complete by callback later. LeadModule handles both patterns in the same workflow layer, so BYOK does not turn into an integration project.

The onboarding path is straightforward:

1. Create an account.
2. Open workspace settings.
3. Add your provider secrets.
4. Create a waterfall config.
5. Order providers based on your market and latency tolerance.
6. Run enrichment from the app or through the API.

If you want the API path, see LeadModule API Quickstart: Enrich Your First 1,000 Contacts.

How BYOK Availability Differs Across Tools

This is where comparison pages usually get sloppy. "Supports BYOK" sounds binary, but in practice it is often plan-specific.

As of March 27, 2026:

• Clay documents BYOK/private API key usage in its FAQ and says existing enrichment subscriptions can be used free of cost inside Clay. Clay also documents waterfall templates, but those templates are still table-created and Clay notes they cannot be edited after creation.
• BetterContact's pricing page lists "Use your own API keys" as a $199 add-on on Starter and Pro, and included on Enterprise.
• FullEnrich's public product/help content is centered on its managed credit model, and FullEnrich publicly compares that approach against BYOK rather than marketing BYOK as a core standard feature. Its separate partner/API page does mention BYOK for certain tiers, which is a different surface from the main product positioning.

What matters is not who has the letters "BYOK" on a landing page. What matters is:

• where the feature is available,
• whether it is included or gated,
• and whether the product is designed around your own provider economics or around bundled credit resale.

That is where LeadModule's positioning is cleaner. The point is not that nobody else supports BYOK. The point is that LeadModule makes it usable early instead of treating it like a gated enterprise feature.

What to Look For in a BYOK-Compatible Enrichment Tool

If you are comparing BYOK tools, these are the five questions worth asking:

1. Is BYOK Included or Gated?

This is the first filter. A tool that technically supports BYOK but only on an expensive or specialized plan may not solve your real problem.

2. Can You Configure the Waterfall Yourself?

BYOK matters less if the tool still hides sequence control. The value is highest when you can decide provider order rather than just drop keys into a black box.

3. Does the Tool Handle Async Providers?

Some providers are not instant. If the tool cannot handle async callbacks cleanly, you will feel that friction quickly.

4. Can You Mix Managed and BYOK Behavior?

You may not want every provider on your own billing from day one. A practical tool should let you move gradually.

5. Do You Get Step-Level Visibility?

Without step-level visibility, you cannot tell whether a provider belongs earlier, later, or not at all.

The Practical Tradeoff

BYOK is not the right starting point for everyone.

If you are doing a few hundred enrichments a month, do not already have provider accounts, and mostly want speed, managed credits can be the right starting point.

If you are already paying providers directly, care about margin, or want explicit control over waterfall economics, BYOK is usually the cleaner long-term model.

That is especially true for the two LeadModule core use cases already visible across the repo and current content:

• agencies managing multiple enrichment workflows,
• and technical GTM teams building API-first systems.

TL;DR

• BYOK enrichment means you connect your own provider API keys and let the platform run the workflow.
• It is mainly a cost-control and control-of-routing decision, not a different enrichment methodology.
• The value grows as your volume, provider knowledge, or operational complexity grows.
• LeadModule includes BYOK on its public Free and Starter plans and supports eight BYOK-capable enrichment providers in the current product.
• When comparing tools, focus on where BYOK is actually available, not whether the letters appear somewhere in the marketing.

Related Reading

• Waterfall Enrichment: How It Works, Costs, and Provider Order
• Email Enrichment Cost Model: Expected Cost per Enriched Contact
• LeadModule vs BetterContact vs FullEnrich: Waterfall Enrichment Compared
• LeadModule API Quickstart: Enrich Your First 1,000 Contacts