A job is one run of one tool: a job_type (for example autodockvina), a payload of inputs and settings, and the hardware to run on. Each tool's page lists its job types and payload fields; start from the tools index.
Lifecycle
| Status | Meaning |
|---|---|
queued | Accepted and paid for (the reservation is held); waiting for hardware or for a free slot under your plan's limit. |
dispatched | Sent to a machine that is starting up. |
running | Computing. |
completed | Finished; the result is ready to download. |
error | Failed. message on the status says why. |
cancelled | Stopped by you. |
Check one job with Get job status, or all of them with List jobs (paged, with filters by status, job type, and name). Rather than polling many jobs, long-poll completion events.
Jobs started by a workflow don't appear in your job list; they show up on the workflow run.
Hardware
Set resource on submit to choose where the job runs: cpu, or a GPU such as a10 or h100. Each job type supports its own set, listed on its tool page; omit resource to use the job type's default. A GPU costs more per second but finishes GPU-bound work far sooner.
What a job costs
- Estimate (free). Estimate job reservation cost prices the job: the catalog's expected runtime for that job type and hardware, scaled up for larger inputs, times your plan's per-second rate.
- Reserve. Submitting holds that amount in your wallet. If your balance minus what is already reserved can't cover it, the submit fails with a
400and nothing is queued. - Charge. When the job ends you pay for the seconds it actually ran, at your plan's rate for its hardware, and the reservation is released.
A job that fails or is cancelled is charged for the time it ran, except one that stops within its first few seconds, which is free. A job whose result could not be saved is not charged. Per-hour prices for every plan and machine are in Wallet and billing.
How many run at once
Your plan limits how many jobs run at the same time. Extra jobs wait in queued and start as others finish.
| Jobs | Basic | Starter | Pro | Enterprise |
|---|---|---|---|---|
| CPU jobs | 1 | 5 | 50 | 500 |
| GPU jobs | 1 | 1 | 5 | 50 |
| Total | 1 | 6 | 55 | 550 |
Results
A completed job's output is a zip of the tool's result files, stored as an artifact. Download it with Download a job result. The job's status also carries result_artifact_id, which lets you list the files and download a single one instead of the whole zip.
Results are kept for a period that depends on your plan, counted from when the job finished; see Plans and limits.
Names, cancelling, and deleting
job_nameis yours to choose and must be unique among your jobs.- Cancel a job stops a queued or running job.
- Delete a job removes it from your job list.
- Submit several jobs queues a batch in one request.