Runs

Get Run

Poll run status, outcome, buyer-facing charge, and final outputs.

curl -X GET 'https://api.edgaze.ai/v1/runs/7c9e6679-7425-40de-944b-e07fc1f90ae7' \
  -H 'Authorization: Bearer edgaze_sk_live_YOUR_KEY'

GEThttps://api.edgaze.ai/v1/runs/{run_id}

Overview#

Poll this endpoint after POST /runs to track execution. The response includes `status`, `outcome`, buyer-facing charge (`displayedChargeUsd`), and final `outputs` once the run completes.

Runs are scoped to the API key owner. You only see runs started by keys belonging to the same account: cross-tenant ids return 404, not 403.

Poll every 1-3s until status is completed, failed, cancelled, or timeout. On success, read outputs from the response. On failure, inspect status and outcome; billing may still show displayedChargeUsd as null.

Authorization#

run:read

Parameters#

Headers

Authorizationstringheaderrequired

Bearer token with run:read scope.

Example: Bearer edgaze_sk_live_…

Path parameters

run_idstringpathrequired

UUID returned from POST /runs.

Example: 7c9e6679-7425-40de-944b-e07fc1f90ae7

Response#

Example payloads are in the request/response panel above.

Edge cases#

Cross-tenant isolation404not_found

Runs belong to the API key owner. Requesting another user's run ID returns 404, not 403.

Displayed charge only

displayedChargeUsd is the buyer-facing price. Raw compute cost is never exposed via the API.

Terminal states

Poll until status is completed, failed, cancelled, or timeout. Check outcome for success vs failure semantics.