Jobs are batch workloads that run a command to completion and terminate automatically. Supports spot instances, multi-node, and progress tracking. Read operations use /{'{namespace}'}/jobs, write operations go through /auth/v1/seed/.
List jobs GET `/{namespace}/jobs`
Retrieve all jobs in a namespace.
Path parameters namespace
type: string
required The namespace (user or organization) to list jobs for.
Query parameters Filter by status. One of `queued`, `running`, `succeeded`, `failed`, `cancelled`, `timed_out`.
Page number for pagination.
Number of results per page. Maximum `100`.
Sort field. One of `created_at`, `started_at`, `completed_at`, `name`.
Sort order. One of `asc`, `desc`.
Request Response 200 Get a job GET `/{namespace}/job/{name}`
Retrieve details for a single job, including runtime metrics and artifact information.
Path parameters namespace
type: string
required The namespace (user or organization) the job belongs to.
name
type: string
required The job name (e.g., `finetune-llama-3-r1`).
Request Response 200 Get job logs GET `/{namespace}/job/{name}/logs`
Stream or retrieve the logs for a job.
Path parameters namespace
type: string
required The namespace (user or organization) the job belongs to.
name
type: string
required The job name.
Query parameters Number of most recent log lines to return. Maximum `10000`.
Return logs after this ISO 8601 timestamp. For example, `2026-03-18T12:00:00Z`.
If `true`, the response uses `text/event-stream` to stream logs in real time. Only available for running jobs.
Request Response 200 Streaming logs in real time For running jobs, you can stream logs using Server-Sent Events:
Get job analytics GET `/{namespace}/job/{name}/analytics`
Retrieve analytics and metrics for a job.
Path parameters namespace
type: string
required The namespace (user or organization) the job belongs to.
name
type: string
required The job name.
Request Response 200 Create a job POST `/auth/v1/seed/{namespace}/jobs`
Submit a new batch job for execution. Jobs run to completion and then terminate.
Path parameters namespace
type: string
required The namespace (user or organization) to run the job in.
Body parameters name
type: string
required A human-readable name for the job. Must be unique within the namespace. Allowed characters: alphanumeric, hyphens, underscores.
command
type: string
required The command to execute. This is run inside the container as the entrypoint.
Full repository name (namespace/repo) to clone into the job's working directory. Either `repo` or `image` is required.
Container image to run. Either `repo` or `image` is required.
Branch to clone when using `repo`.
gpu
type: string
required GPU type for the job. One of `A100-40GB`, `A100-80GB`, `H100-80GB`, `L4`, `T4`, `none`.
Number of GPUs. Must be `1`, `2`, `4`, or `8`.
Number of vCPUs. One of `2`, `4`, `8`, `16`, `32`, `64`, `96`.
Ephemeral disk size in gigabytes. Data is discarded when the job completes.
Environment variables as key-value pairs.
Deployment region. One of `us-east-1`, `us-west-2`, `eu-west-1`, `eu-central-1`, `ap-northeast-1`.
timeout_minutes
type: integer
Maximum runtime in minutes before the job is killed. Default is 24 hours. Maximum is `10080` (7 days).
Number of times to retry the job on failure. Maximum `5`.
Path inside the container to persist as job artifacts. Contents are uploaded to your namespace's artifact storage on completion.
Request Response 201 You can also submit jobs from a container image using an API key:
Cancel a job POST `/auth/v1/seed/{namespace}/jobs/{name}/cancel`
Cancel a queued or running job. Running jobs receive a SIGTERM followed by a SIGKILL after a 30-second grace period.
Path parameters namespace
type: string
required The namespace (user or organization) the job belongs to.
name
type: string
required The job name.
Request Response 200 Delete a job DELETE `/auth/v1/seed/{namespace}/jobs/{name}`
Delete a completed job record and its associated artifacts. Only completed, failed, or cancelled jobs can be deleted.
Path parameters namespace
type: string
required The namespace (user or organization) the job belongs to.
name
type: string
required The job name.
Query parameters delete_artifacts
type: boolean
Also delete uploaded artifacts from storage. This action cannot be undone.
Request Response 204 Returns an empty response body on success.
Error responses All job endpoints may return the following errors:
Status Description 400 Bad request -- invalid parameters or configuration 401 Unauthorized -- missing or invalid credentials 403 Forbidden -- insufficient permissions 404 Not found -- job does not exist 409 Conflict -- job is in an incompatible state (e.g., already completed) 422 Unprocessable entity -- invalid GPU/CPU/memory combination 429 Rate limit exceeded 500 Internal server error -- Seed orchestration failure