deepline run

Usage: deepline run [options] [name]

Run a tool, a play, a play file, or inline code.

Options:
  -e, --eval <code>        Code to run as a play body, instead of a name
  --input <json>           Input as a JSON object
  --input-file <path>      Input from a JSON file; - reads stdin
  --json-out <path>        Save the result as JSON to this new file
  --csv-out <[list=]path>  Save rows as CSV to this new file; repeat for more
                           lists
  --fields <paths>         Only these dotted paths, comma-separated
  --dry-run                Check the input and show the price; runs nothing
  --timeout <duration>     Stop waiting after 90s, 10m, 1h; 0 returns at once
  --max-credits <credits>  Stop a play run that would spend more
  --fresh                  Call providers again instead of reusing saved results
  --json                   Print the receipt as JSON
  --full                   Show every field of the result
  --lines <n>              Lines of values in the receipt (default 32)
  --receipt-out <path>     Also save the receipt as JSON
  --logs-out <path>        Save a play's live logs here; - prints them
  -h, --help               display help for command

Explanation:
  Purpose:
    Run a tool, a play, a play file, or a few lines of code. One command for
    all of them.
  When:
    After describe, once you know the inputs. For paid work, add --dry-run
    first to check the input and see the price.
  Input:
    The id from search, and one JSON object: --input '{...}' or
    --input-file input.json. A play that reads a CSV takes its path:
    --input '{"csv":"leads.csv"}'. -e '<code>' runs code as a play body.
    <play>@latest runs the newest revision; deepline/<id> runs Deepline's
    version when your workspace has one with the same name.
  Examples:
    deepline run hunter_email_verifier --input '{"email":"a@b.com"}'
    deepline run person-to-email-batch --input '{"csv":"leads.csv"}' --dry-run
    deepline run person-to-email-batch --input '{"csv":"leads.csv"}' --csv-out emails.csv
    deepline run my.play.ts --input-file input.json --json-out result.json
    deepline run -e 'return { doubled: input.n * 2 };' --input '{"n":21}'
  Output:
    A receipt: what ran, its status and cost, where the data was saved, and
    the first values. The full data is always saved to a file; --csv-out and
    --json-out choose where. --fields picks values and CSV columns. Exit code
    0 completed, 1 failed or still running, 2 nothing ran.
  Cost:
    What the tool or play charges. --max-credits caps a play run. Running an
    interrupted call again replays it without paying twice.
  Next:
    Read the saved file. deepline runs get <id> shows the run again.