Submit a job

Submitting a job is two calls to POST /v1/jobs with the same order: the first returns a quote, the second carries the payment signature and the sealed payload.

This guide assumes the shell variables from the Quickstart (VORQ, KEY, ADDR, CHAIN_ID, JOB_REGISTRY).

1. Seal the payloadCopy Anchor Link

The coordinator never sees plaintext. Build the sealed container on your side:

container = 0x01 ‖ seed_wrap (80 bytes) ‖ ciphertext

seed_wrap seals a random 32-byte seed to one of two keys:

• Designated order: the box_key of the provider you pick (from a quote's candidates, or from GET /evm/providers/{id}). Set designated to that provider's id.
• Open bid: the escrow key from GET /key, on a coordinator that hosts an escrow. Set designated to 0.

The VORQ client SDKs implement the sealing. The coordinator checks only the framing and the commitment. See Payloads and file retention and Escrow and key release.

2. Compute the commitment and job idCopy Anchor Link

c      = keccak256(0x01 ‖ seed_wrap ‖ keccak256(ciphertext))
job_id = keccak256(owner ‖ c)

A fresh c gives a fresh job_id. Reusing one answers 409 DuplicateJob.

3. Sign the order and get a quoteCopy Anchor Link

Sign the Order (see Signed messages) and post the order fields without auth_sig, as in the Quickstart. The answer is 402 with a quote.

If you seal to a candidate, set designated to its provider_id before signing: the order you quote must be the order you submit.

4. Sign the paymentCopy Anchor Link

Sign the EIP-3009 ReceiveWithAuthorization described by quote.authorization, using the payment token's own domain (quote.authorization.domain):

The owner must be an account with no contract code: a smart account or an EIP-7702-delegated account is refused with 400 payer_has_code. Funds move only when a provider claims the job, so the owner needs a balance of at least amount by then.

5. SubmitCopy Anchor Link

Send the same order fields again, plus auth_sig, amount and the container.

Inline, for containers up to 15 679 488 bytes, as base64:

curl -s -X POST "$VORQ/v1/jobs" -H 'content-type: application/json' -d @submit.json

{
  "c": "0x…", "model_id": 3, "sla_secs": 3600, "rate_in": "1200", "rate_out": "5000",
  "units_in": 1000, "units_out": 1000, "designated": 7, "expires_at": 1786003600,
  "owner": "0x…", "job_id": "0x…", "signature": "0x…",
  "auth_sig": "0x…", "amount": "2007",
  "container": "AQ…"
}

By upload, for larger containers. Open a session, upload the container, then post its cid as container_cid instead of container:

curl -s -X POST "$VORQ/v1/files" \
  -H "authorization: Bearer $TOKEN" \
  -F purpose=input \
  -F file=@container.bin | jq -r .vorq.cid

The upload must come from the order's owner. An upload that is not attached to a job within 300 seconds is deleted, so upload right before you post.

The answer is 201:

{ "job_id": "0x…", "task_cid": "bafy…", "tx_hash": "0x…" }

6. Handle a changed priceCopy Anchor Link

If the node's gas_fee or the protocol fee_bps changed after your quote, amount no longer matches and the answer is 409 with a fresh {quote, candidates, accepts} body. Sign a new payment for the new amount and submit again. The order signature stays valid.

For any other failure, see Errors. Retry only when the x-vorq-retryable header is true. A 504 receipt_timeout means the transaction was sent: poll the job instead of posting again.

7. Collect the resultCopy Anchor Link

Poll the job until its status is terminal:

curl -s "$VORQ/v1/jobs/$JOB_ID" | jq '{status, result_cid}'

result_cid is an IPFS content identifier. Fetch the sealed result from an IPFS gateway and open it with your key. The coordinator does not serve result bytes to clients.

To stop an open job, see Cancel a job.