Funding Runs
How your wallet and workflow bundles fund runs started in the app or through the API.
Buyers and creators using Edgaze.
Overview#
You fund runs from your wallet or a prepaid workflow bundle. The app and API are ways to start a run; both use the same funding order: matching bundle first, then wallet.
5 or 10 runs on one workflow version. Drawn first.
Top up once, pay per run on any workflow when bundles are empty.
Bundles are locked to one workflow version. They contain 5 or 10 runs, have a $5.00 minimum total, and expire after 2 years.
Wallet#
Top up at least $10.00 through checkout. Wallet balance works across current per-run workflows. The available amount excludes money reserved for runs in progress.
Wallet is the most flexible option if you run many different workflows.
Prepaid bundles#
A bundle prepays 5 or 10 runs for one workflow version. The total equals the displayed per-run price times the pack size and must be at least $5.00.
Bundle runs draw before wallet on every trigger. Failed runs do not consume a bundle run. When your bundle is empty or expired, funding falls through to your wallet.
At trigger#
When you start a run, Edgaze checks for an eligible bundle matching you, the workflow, and the exact version you selected. If one exists with runs remaining and has not expired, that run uses the bundle.
Otherwise the run is funded from your wallet. If your wallet cannot cover the price and no bundle run is available, execution does not start and no charge is made. For the REST API, the run record already exists because funding finalizes after the 202; it later reports failed.
API-triggered runs follow the same order. API keys can also set a spend cap that rejects the request before a run record exists. See the canonical API funding table.
After the run#
A successful bundle-funded run consumes one prepaid run. A successful wallet-funded run charges your balance for the displayed price.
A failed or cancelled run releases any wallet reservation without charging the creator's margin. Bundle runs are not consumed on failure.
Special cases#
- Bundle depleted: Funding falls through to wallet. If wallet is insufficient, the run will not start.
- Wrong version: Bundles only apply to the version they were purchased with. Other versions use wallet at their own price.
- Expired bundle: Excluded from funding. You must use wallet or the run will not start.
- Insufficient wallet: No execution starts and no charge is made. An API request has already received a run id, so that record becomes
failed.
What you see in Edgaze#
- Checkout: wallet top-up, 5-run bundle, and 10-run bundle options with per-run and total prices
- Workflow page: "runs left" counter when you hold a prepaid bundle
- Wallet page: top-ups, bundle purchases, reservations, and charges
- Insufficient funds or spend cap messages when a run cannot start
Related policies#
Was this useful?
Your response helps us improve the documentation.
Related documentation
How workflow runs are priced, funded, settled, and refunded. Step-by-step guides for buyers, creators, and developers.
How to open a workflow, fund a run, and what happens when it completes.
How the per-run price is built, what the creator earns, and what Edgaze keeps.