Render a failed short again, without paying twice

POST with the failed run's claim ticket. With no body the run resumes: steps that succeeded are reused and only what failed re-renders (a writer whose script a later step could not use is re-run, with everything after it), and the wallet balance must cover what will re-run, never more than the full price. With {"topic": "..."} it starts over, at the full price, from the wallet balance. Each failed run can be retried once.

post/api/x402/short/retry

Request

  • Base URL: https://www.trezalabs.com
  • URL: https://www.trezalabs.com/api/x402/short/retry
  • Auth: HTTP bearer

Query parameters

runIdstring required

The failed run, from its status response.

tokenstring required

Signed claim ticket from the paid POST. The retryUrl in the status response carries both.

Headers

Preferstring

Optional. respond-async answers at once (200, status running) with a statusUrl; wait=N waits up to N seconds (at most 720) before ending with status running and the statusUrl. Without it, the call waits about as long as that style usually takes: about four and a half minutes for stills, five for motion. A client with a fixed timeout, such as the 60 seconds MCP tool calls allow, should send wait=N under it or respond-async.

Request body

topicstring
asyncboolean

Response

The retry started and the response waited for it, streamed like the paid POST.

Changes

No recorded changes to this operation across all 1 revision of this API.