Hard facts
BYOK primitives
Everything you need to know in one table.
| BYOK providers | 26 |
| Platform fee | $0/month |
| Markup on provider costs | 0% |
| Supported providers | Apollo, Hunter, Crustdata, PDL, LeadMagic, Prospeo, Dropleads, Icypeas, and 18 more |
| Setup time | Under 2 minutes per key |
| Managed credit option | From $0.08/credit |
| Mixed mode | Yes -- BYOK + managed credits in same waterfall |
| Key storage | AES-256 encrypted, per-workspace, never shared |
| OAuth providers | 3 (Attio, HubSpot, Salesforce) |
Straight talk
What this means
$0/month with your own API keys, zero markup on every call. You pay your providers directly at their published rates. Deepline adds orchestration, waterfall logic, and normalized output schemas for free.
If you already pay Apollo, Crustdata, Hunter, or PDL directly, BYOK lets you route those keys through Deepline without double-paying. You keep your negotiated rates, your usage dashboards, and your billing relationship.
Use BYOK for providers where you have contracts and managed credits for everything else. A single waterfall enrichment can use your Apollo key for step 1, managed credits for Hunter in step 2, and your LeadMagic key for step 3.
You have zero provider accounts and want to start enriching immediately. In that case, use managed credits instead -- they start at $0.08/credit, require no provider signups, and work across all 26 providers. Switch individual providers to BYOK later.
26 providers
Supported BYOK providers
Connect any combination. Each key is stored independently and encrypted at rest.
Plus 3 OAuth providers (Attio, HubSpot, Salesforce) connected via the Deepline dashboard.
Monthly cost
Cost comparison for 2,000 enrichments/month
3-provider email waterfall. Same enrichment, different pricing models.
| Model | Platform fee | Enrichment cost | Total |
|---|---|---|---|
| Full BYOK (3 keys) | $0/mo | Provider rates only (~$80-$200) | ~$80-$200/mo |
| Mixed (2 BYOK + 1 managed) | $0/mo | ~$100-$240 | ~$100-$240/mo |
| Full managed credits | $0/mo | ~$160-$250 at $0.08-$0.10/cr | ~$160-$250/mo |
| Clay Explorer (comparable) | $185/mo | + Clay credits | $185+/mo |
Deepline platform fee is $0/month regardless of mode. The difference is purely per-enrichment cost and whether you manage provider accounts directly.
Connect a key in one command
No dashboard clicks, no config files. Set a provider key from your terminal and it is available for all enrichment calls immediately.
deepline keys set apollo --key "your-apollo-api-key" deepline keys set hunter --key "your-hunter-api-key" deepline keys list # Provider Status Added # apollo active just now # hunter active just now
Common questions
FAQ
What happens if my BYOK key hits a rate limit?
Deepline respects provider rate limits. If your Apollo key is rate-limited, the waterfall moves to the next provider in the chain. If all BYOK providers are exhausted, the enrichment returns a partial result with a clear status code. Deepline does not retry rate-limited requests automatically; it moves forward to avoid wasting your quota.
Can I use BYOK and managed credits for the same provider?
No. For a given provider, your workspace uses either your BYOK key or managed credits, not both simultaneously. Connect a BYOK key and all calls to that provider use your key. Remove the key to fall back to managed credits. This prevents ambiguous billing.
Do I need BYOK keys for waterfall enrichment to work?
No. Waterfall enrichment works with managed credits, BYOK keys, or any combination. The waterfall engine is agnostic to how each provider is authenticated. Zero keys connected means managed credits handle everything. Three BYOK keys plus two managed-credit providers means the waterfall uses all five in configured priority order.
How do I know which mode was used for each enrichment step?
Every enrichment response includes a provider_chain array showing which providers were called, in what order, and which one returned the final result. BYOK providers show auth_mode: "byok". Managed credits show auth_mode: "managed". You can audit exactly where every API call went.
How are my API keys stored?
Every key is encrypted at rest using AES-256, scoped to your workspace, never shared across tenants, and never logged. Keys are deletable on demand via CLI or API. When Deepline makes a call using your key, the request goes directly to the provider API. No proxy stores or inspects the key beyond initial decryption.
Start enriching for free
Install the CLI, connect your API keys, and run your first waterfall. $0/month, zero markup, under 2 minutes.
curl -s "https://code.deepline.com//api/v2/cli/install" | bash