Skip to main content
Human guide: work with your agent → Inspect one Apify action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

​
Existing outputs

Use Apify to read results from an existing, authorized run or dataset.
  • apify_get_dataset_items reads a dataset, with limit and offset pagination.
  • apify_get_actor_run and apify_list_actor_runs read run status and history.
  • apify_get_log reads a saved run’s log.
  • apify_get_kv_record reads a stored key-value record.
  • apify_check_credits reads the account’s available credits.
  • apify_stop_actor_run stops an existing actor run. confirm this mutation with the user.

​
SDK/API actor execution

SDK/CLI/API actor contracts remain available. Establish authorization from the source platform before designing collection. An actor listing or intermediary agreement does not establish that permission. Use only inputs and sources the user is authorized to process. Do not collect private profiles or saved searches through browser-session credentials. Actor wrapper fields (actorId, input, params, timeoutMs) and runtime validation can differ from actor-page docs. Inspect the current operation schema. Actor IDs use username/name. Store search quality ranking considers rating, review count, total runs, and 30-day success rate. rankBy: "relevance" selects Apify’s native sort. Deepline permits four unresolved actor jobs per organization by default. An explicit execution limit can override this. Capacity refusals are retryable and occur before another billable launch. An HTTP 200 with an empty dataset is classified as meta.resultOutcome.classification = "ambiguous_empty". It does not prove the input was attempted or that there was no result. Do not automatically retry: the first run remains billable and a retry may create a second charge.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.