Contract
The route is a Play, not a promise in a landing page
Waterfall enrichment queries providers in an explicit sequence and stops or continues according to the Play's validation rules. The maintained Play is the source of truth for its current stages. Describe it before you run it:
deepline plays search "verified work email waterfall" --json deepline plays describe prebuilt/name-and-domain-to-email-waterfall-batch --json
The live contract shows the accepted input, output shape, and current workflow identity. The broader Deepline catalog contains 105+ integrations; an individual waterfall uses only the stages declared by its Play.
Pilot
Test the production-shaped workflow
Create a small representative file, then run the same maintained Play you plan to use for the full dataset:
awk 'NR <= 4' leads.csv > leads-pilot.csv deepline plays run prebuilt/name-and-domain-to-email-waterfall-batch --csv leads-pilot.csv --watch
Review returned fields, provider provenance, no-result rows, validation status, usage, and errors. If the contract and result fit the job, run the full input:
deepline plays run prebuilt/name-and-domain-to-email-waterfall-batch --csv leads.csv --watch
Ownership
Own the workflow when the route is part of your system
Use an owned Play when you need a different provider sequence, custom validation, approvals, CRM writes, schedules, or webhooks. Your agent inspects the live tool and Play contracts, authors the workflow, and checks it before execution:
deepline tools search "work email finding and validation" --json # Your agent authors email-waterfall.play.ts from the inspected contracts. deepline plays check email-waterfall.play.ts deepline plays run --file email-waterfall.play.ts --csv leads-pilot.csv --watch deepline plays publish email-waterfall.play.ts deepline plays describe email-waterfall --json deepline plays versions --name email-waterfall --json
Billing
Review the result path, not a universal per-row estimate
- BYOK: Deepline charges no platform fee for provider requests. You pay providers under your own contracts.
- Managed billing: Charges depend on the pricing unit of each stage that executes. Some providers charge for a result; others charge for a request or page.
- Pilot first: Use the pilot's run usage as evidence for your input mix. Do not multiply a standalone tool price into a claimed waterfall average.
Related
Keep reading
FAQ
Common questions
1How much does a waterfall run cost?+
The total depends on which stages execute, the result path, and whether your workspace uses BYOK or managed billing. BYOK means you pay providers directly. Managed runs can include provider charges for attempted calls as well as returned results. Inspect the live Play and run a representative pilot before estimating a full dataset.
2How does Deepline choose a waterfall?+
Your agent searches the live Play catalog for the job and input shape, then describes the candidate contract. The selected maintained Play is explicit; Deepline does not silently invent a route from a marketing page.
3What happens when every provider misses?+
The Play returns its defined no-result output. Review the Play run status, usage, and errors. Deepline charges zero credits for BYOK operations, but the provider can charge the connected account. Managed charges depend on each operation that runs.
4Can I customize provider order or validation?+
Yes. Start from the inspected maintained contract, create an owned .play.ts workflow, edit its stages, and run deepline plays check. The owned Play keeps ordering, validation, retries, review boundaries, and output shape in version control.
5Does a waterfall guarantee a match rate?+
No. Another provider can fill a gap left by the first source. The lift depends on the input, field, route, and validation rules. Measure the maintained Play on representative data.