Estimate routing, capacity source, and expected cost for a proposed Jungle Grid workload without submitting it.

Submit a Jungle Grid workload for execution. This may start managed compute infrastructure and incur usage charges.

Create a managed upload slot for an input file or script. Upload bytes to upload_url with HTTP PUT, complete the upload through complete_url, then pass input_id to submit_job.

List uploaded job inputs for the authenticated account, including mount paths.

List the authenticated user's Jungle Grid jobs, optionally filtered by status. Use this to find recent jobs before checking status, logs, or artifacts.

Retrieve current status, execution phase, stable phase-entry timing, latest provider/platform update timing, scheduling delay, routing, failure, and artifact contract details for a specific Jungle Grid job. phase_started_at is when the job first entered the current normalized phase; phase_last_updated_at is later provider/platform progress or heartbeat when present; delayed_start identifies a prolonged wait in the actual current phase. A supported estimate does not guarantee immediate or successful runtime startup.

Retrieve platform lifecycle events for a job, including scheduling and startup events that can appear before workload logs exist.

Retrieve paginated job logs. Entries include category so platform/runtime logs can be distinguished from workload_stdout/workload_stderr. If workload logs are empty while a job is queued/starting, call get_job_events for platform scheduling events.

Cancel an existing Jungle Grid job. This may stop active execution and prevent further outputs.

List output artifacts associated with a specific Jungle Grid job.

Retrieve download information for a specific output artifact from a Jungle Grid job.