Skip to main content

runs get

With --wait, the CLI polls with exponential backoff (1s, then 1.5s, 2.25s and so on, capped at 8s) until the run is COMPLETED, FAILED, STOPPED or TIMED_OUT.
The exit code follows the run, not the HTTP call: COMPLETED exits 0, anything else exits 4.
Polling is free and idempotent. It is also what advances an in-flight run, so polling a slow run is the normal thing to do, not a workaround.

JSON shape

quoted_cost_* is the hold that was taken up front. cost_* is what you were actually charged. Every amount comes as both an integer in micro-USD (one millionth of a dollar, so there is no floating point drift) and a formatted string. output is null here once the rows have been collected, or once the run is more than 24 hours old. Capture them with goro run ... -o file.json.

runs list

Newest first. When there is another page, the CLI prints the exact command to fetch it.

balance

available is what you can spend right now: cash plus any promotional credit, minus anything currently held by a running call. Promotional credit is listed separately when you have some, because it is spent before cash. An empty wallet says so, and points at the top-up page:

Recipes

Piping to jq, retry loops, and batch runs.