Get Run
Poll canonical run status, failure reason, buyer-facing charge, and final outputs.
curl --fail-with-body --silent --show-error 'https://api.edgaze.ai/v1/runs/7c9e6679-7425-40de-944b-e07fc1f90ae7' \ -H "Authorization: Bearer $EDGAZE_API_KEY"
Developers polling an asynchronous run.
https://api.edgaze.ai/v1/runs/{run_id}Overview#
Poll this endpoint after POST /runs to track execution. The response includes canonical status, a sanitized reason for failures, buyer-facing charge (displayedChargeUsd), explicit billingStatus, and final outputs once the run completes.
billingStatus is pending while a paid run is not financially final, settled when displayedChargeUsd is final, and not_charged when a terminal run produced no charge. New successful runs publish status: "completed" only after billing settlement commits. The pending terminal combination remains documented so clients can recognize and safely poll older or reconciled runs.
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.
Authorization#
run:readParameters#
Headers
AuthorizationstringheaderrequiredBearer token with run:read scope.
Example: Bearer edgaze_sk_live_…
Path parameters
run_idstringpathrequiredUUID returned from POST /runs.
Example: 7c9e6679-7425-40de-944b-e07fc1f90ae7
Response#
Example payloads are in the request/response panel above.
Edge cases#
not_foundRuns belong to the API key owner. Requesting another user's run ID returns 404, not 403.
displayedChargeUsd is the buyer-facing price. Raw compute cost is never exposed via the API.
billingStatus is pending until settlement, settled when displayedChargeUsd is final, or not_charged for terminal runs without a charge. Poll a terminal pending response until billing is final.
Poll until status is completed, failed, or cancelled. Provider and orchestration timeouts are reported as failed with a safe reason.
Was this useful?
Your response helps us improve the documentation.