Using Apollo in Claude Code vs Deepline's Waterfall.

The Coverage Gap

Single-provider enrichment leaves gaps

Apollo's enrichment API works well, but single-provider enrichment leaves coverage gaps. Every contact Apollo can't match is a lead you already paid to source that comes back without an email.

The math is simple: any single-provider lookup leaves the remainder of your pipeline on the table. Every empty row is a contact your SDRs can't reach. Every missing email is a deal that never starts.

Adding a waterfall changes that math. Apollo runs first. Crustdata, People Data Labs, Hunter, and LeadMagic pick up the misses. Result: higher combined coverage from one command (depending on ICP and region), using the providers you already have accounts with.

Calling Apollo

Calling Apollo from Claude Code

Apollo has a REST API. Claude Code can call it - you'd write a Bash command with curl or have Claude Code generate a script that loops through your CSV and calls the People Match endpoint for each row.

This works for single-provider enrichment. But when Apollo doesn't have a match, you're on your own. You'd need Claude Code to write custom fallback logic: try Crustdata next, then PDL, then Hunter - handling different API schemas, error codes, rate limits, and response formats for each.

# Calling Apollo's API directly from Claude Code
# You'd need to write something like this for EACH provider:

curl -s -X POST "https://api.apollo.io/api/v1/people/match" \
-H "Content-Type: application/json" \
-H "X-Api-Key: $APOLLO_API_KEY" \
-d '{"first_name":"Jane","last_name":"Doe","organization_name":"Acme"}'

# Then parse the response, check if email exists,
# if not, call Crustdata with a different API schema,
# then PDL with yet another schema...
# Plus handle rate limits, retries, and validation.

Each provider has a different API schema, auth method, and response format. Claude Code would need to orchestrate all of this.

Deepline

Using Deepline's waterfall in Claude Code

Deepline is a CLI that Claude Code calls directly - the same way it calls git or curl. One command, one flag, and Apollo becomes the first step in a 15-provider waterfall. No custom orchestration code. No fallback logic. Minimal token overhead.

# In Claude Code - one command, one flag:
deepline enrich --input leads.csv \
--with-waterfall email \
--providers apollo,crustdata,pdl,hunter \
--with '{"alias":"verify","tool":"leadmagic_email_validation","payload":{"email":"{{email}}"}}' \
--with '{"alias":"score","tool":"deeplineagent","payload":{"prompt":"Score this lead 1-10: {{verify}}","json_mode":true}}'

# Apollo is tried first. If it returns an email, the waterfall stops.
# If not, Crustdata tries next, then PDL, then Hunter.
# The winning email is validated via LeadMagic.
# Total token cost in Claude Code: minimal overhead.

Your existing Apollo API key is used. Apollo credits are only consumed when Apollo is the provider that finds the match.

Code Comparison

Compare the workflows

# Apollo API alone in Claude Code
# For each row in CSV:
curl -X POST \
"https://api.apollo.io/api/v1/people/match" \
-H "X-Api-Key: $KEY" \
-d '{"first_name":"...",
  "last_name":"...",
  "organization_name":"..."}'

# If no email -> no fallback
# Coverage: single-provider only
# Tokens: high orchestration overhead
# Providers: 1

# Deepline waterfall in Claude Code
deepline enrich --input leads.csv \
--with-waterfall email \
--providers \
  apollo,crustdata,pdl,hunter \
--with '{"alias":"verify","tool":"leadmagic_email_validation","payload":{"email":"{{email}}"}}'

# Apollo first -> fallback chain
# Coverage: high (multi-provider waterfall)
# Tokens: minimal overhead
# Providers: 30+

Who should use what

Choose Deepline if you...

• Use Claude Code for GTM workflows and want higher coverage
• Already have an Apollo account and want waterfall fallback
• Want one CLI command instead of custom API orchestration
• Need higher email coverage than a single provider offers
• Want AI agents to run enrichment autonomously
• Want data in your own PostgreSQL database

Choose Apollo alone if you...

• Need a built-in B2B contact database for prospecting
• Want a CRM alongside your enrichment
• Prefer a point-and-click prospecting UI
• Single-provider email coverage is sufficient for your use case

Feature Comparison

Side-by-side

Common questions

FAQ