Documentation Index
Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Playbook
Use Apify when you need controlled web automation/scraping workflows.- Use
apify_list_store_actorsfirst when you do not know the actor id yet. - Build
actorIdasusername/namefrom store results. - Use
apify_get_actor_input_schemato inspect required/optional fields before running. deepline tools get/executeactor fields andactor-contracts.mdshould match because both are generated from typed actor contracts.- Wrapper-level fields (
actorId,input,params,timeoutMs) and runtime validation behavior can differ from actor-page docs. - Prefer
apify_run_actor_syncas the default execution path when you want results in one call. - Use
apify_run_actoronly when you need non-blocking execution, then poll run status before fetching outputs. - Use
actor-contracts.mdfor actor-specific required/optional input fields and sample payloads. - Validate payload shape with a tiny run before scaling row counts.
- If
tools get/executeactor fields differ fromactor-contracts.md, treat it as a typed-contract bug and fix source data. - For page-vs-wrapper drift, trust Deepline wrapper validation for execution payload shape.
- If still unclear, run a 1-row/1-item pilot payload and adjust to pass Deepline validation before scaling.