Skip to Content
supedocs

Long jobs

Video, research and calls that take minutes.

Some tools take minutes: making a video, deep research, a phone call. Their price is held while they run and charged only if they succeed.

With the CLI

supe run waits for a long job and prints the answer when it's done. To get on with other work instead:

supe run <tool> ... --no-wait      # prints the job id and exits
supe job <job_id>                  # collects it, waiting if it's still going

If a job is still running when the CLI stops waiting, it exits with code 6 and the job id. Run supe job <job_id> later.

Over HTTP

POST /v1/run returns 202 with status: "running", a job_id and check_again_in_s when a job is still going after about 45 seconds. Collect it:

curl -s "https://service.oex.sh/v1/jobs/<job_id>?wait=20" -H "Authorization: Bearer $SUPE_API_KEY"

wait=20 holds the request up to 20 seconds. You get 200 with the answer when it's done, or 202 while it's running.

Over MCP

execute_tool returns status: "running". The agent tells you it's under way, then calls get_job with the job_id after check_again_in_s.

On this page