Run Outcomes Reference

Quick reference for who pays and who earns across common run scenarios.

Audience

Buyers and creators using Edgaze.

Overview#

This table summarizes billing outcomes for hosted runs, API runs, bundles, BYOK, failover, and payouts. Use it to find your scenario and see what happens to the buyer, the creator, and Edgaze.

For narrative detail, follow the doc link in each row.

Reference table#

Scenario	You pay	Creator earns	Edgaze absorbs	What you see	Learn more
Hosted run success (wallet)	Yes: full displayed price	Yes: 80% of margin	Compute variance within envelope	Run completes; wallet balance drops	Run a Workflow
Hosted run success (bundle)	One prepaid run consumed	Yes: 80% of margin	Compute used	Runs remaining count updates	Funding Runs
Hosted run failure	No margin charge	No	Yes: compute used	Failure reason; no margin charge	When Runs Fail
Cancel before start	No	No	No	Cancelled before start	When Runs Fail
Cancel mid-run	No margin	No	Yes: compute used	Run cancelled	When Runs Fail
Insufficient wallet	No run started	No	No	Insufficient funds message	Funding Runs
Bundle available	Bundle used first	On success only	Infra	Bundle draw indicator	Funding Runs
Bundle depleted	Wallet or blocked	On success only	If wallet fails, N/A	Prompt to top up wallet	Funding Runs
Wallet after bundle	Wallet on success	On success only	Variance	Same as wallet success	Funding Runs
API wallet run	Same as wallet success	On success only	Variance	API success response	API Runs
API spend cap reached	No run	No	No	Spend cap error	API Runs
BYOK run success	Margin plus $0.002 orchestration	Yes: 80% of margin	Provider tokens on your key	BYOK pricing note	BYOK
BYOK failure	No margin	No	Orchestration per failure policy	BYOK note plus error	BYOK
Failover enabled, success	Pinned displayed price only	Yes: 80% of margin	Failover cost delta	No visible price change	Failover
Failover disabled, failure	No margin	No	Compute used	Standard failure message	Failover
Failover cost increase	Pinned price only	Yes on success	Delta	Hidden from buyer	Failover
Creator changes price (new version)	Old pin pays old price	On successful runs	N/A	Per-version prices in selector	Version Pinning
Buyer owns pinned version	Pinned price per run	On successful runs	N/A	Version dropdown	Version Pinning
Version unpublished	Pinned purchase still runs if graph exists	On success	N/A	Error if graph unavailable	Version Pinning
Nested or remixed workflow	Sum of child prices on root quote	Each creator earns own margin	Child compute in root run	Sealed node price badges	Remix and Nested Workflows
Wallet top-up refund request	If approved: minus Stripe fees	N/A	N/A	Refund acknowledgment	Refunds
Refund outside policy	Denied at support discretion	N/A	N/A	Support response	Refunds
Bundle expiry (2 years)	Cannot draw expired bundle	N/A	N/A	Expired bundle message	Bundles Expiry and Refunds
Creator payout pending	None	Earnings waiting in pending	None	Pending on dashboard	Creator Earnings Guide
Creator payout available	N/A	Cleared after 7 days	N/A	Available balance	Creator Earnings Guide
Creator payout paid	N/A	Transferred via Stripe Connect	N/A	Payout history	Payout System
Demo or sandbox run	No	No	Compute used	Demo badge	Run a Workflow
Builder test run	No	No	Compute used	Builder preview	Workflow Studio
Stopped at the compute limit	Consumed compute may be retained	No	Remainder	Compute-limit stop message	When Runs Fail
Legacy unlock listing	Legacy unlock purchase	Legacy purchase split	N/A	Unlock versus per-run copy	Legacy Unlock

Notable exceptions#

Stopped at the compute limit: Already-consumed compute may be retained. Margin is released. This is separate from an ordinary failure.
Demo and builder test: Never billed.
Bundle expiry: Unused prepaid runs expire after two years. Creators do not earn on runs that were never used.

Was this useful?

Your response helps us improve the documentation.

Run Outcomes Reference

Quick reference for who pays and who earns across common run scenarios.

Audience

Buyers and creators using Edgaze.

Overview#

This table summarizes billing outcomes for hosted runs, API runs, bundles, BYOK, failover, and payouts. Use it to find your scenario and see what happens to the buyer, the creator, and Edgaze.

For narrative detail, follow the doc link in each row.

Reference table#

Scenario	You pay	Creator earns	Edgaze absorbs	What you see	Learn more
Hosted run success (wallet)	Yes: full displayed price	Yes: 80% of margin	Compute variance within envelope	Run completes; wallet balance drops	Run a Workflow
Hosted run success (bundle)	One prepaid run consumed	Yes: 80% of margin	Compute used	Runs remaining count updates	Funding Runs
Hosted run failure	No margin charge	No	Yes: compute used	Failure reason; no margin charge	When Runs Fail
Cancel before start	No	No	No	Cancelled before start	When Runs Fail
Cancel mid-run	No margin	No	Yes: compute used	Run cancelled	When Runs Fail
Insufficient wallet	No run started	No	No	Insufficient funds message	Funding Runs
Bundle available	Bundle used first	On success only	Infra	Bundle draw indicator	Funding Runs
Bundle depleted	Wallet or blocked	On success only	If wallet fails, N/A	Prompt to top up wallet	Funding Runs
Wallet after bundle	Wallet on success	On success only	Variance	Same as wallet success	Funding Runs
API wallet run	Same as wallet success	On success only	Variance	API success response	API Runs
API spend cap reached	No run	No	No	Spend cap error	API Runs
BYOK run success	Margin plus $0.002 orchestration	Yes: 80% of margin	Provider tokens on your key	BYOK pricing note	BYOK
BYOK failure	No margin	No	Orchestration per failure policy	BYOK note plus error	BYOK
Failover enabled, success	Pinned displayed price only	Yes: 80% of margin	Failover cost delta	No visible price change	Failover
Failover disabled, failure	No margin	No	Compute used	Standard failure message	Failover
Failover cost increase	Pinned price only	Yes on success	Delta	Hidden from buyer	Failover
Creator changes price (new version)	Old pin pays old price	On successful runs	N/A	Per-version prices in selector	Version Pinning
Buyer owns pinned version	Pinned price per run	On successful runs	N/A	Version dropdown	Version Pinning
Version unpublished	Pinned purchase still runs if graph exists	On success	N/A	Error if graph unavailable	Version Pinning
Nested or remixed workflow	Sum of child prices on root quote	Each creator earns own margin	Child compute in root run	Sealed node price badges	Remix and Nested Workflows
Wallet top-up refund request	If approved: minus Stripe fees	N/A	N/A	Refund acknowledgment	Refunds
Refund outside policy	Denied at support discretion	N/A	N/A	Support response	Refunds
Bundle expiry (2 years)	Cannot draw expired bundle	N/A	N/A	Expired bundle message	Bundles Expiry and Refunds
Creator payout pending	None	Earnings waiting in pending	None	Pending on dashboard	Creator Earnings Guide
Creator payout available	N/A	Cleared after 7 days	N/A	Available balance	Creator Earnings Guide
Creator payout paid	N/A	Transferred via Stripe Connect	N/A	Payout history	Payout System
Demo or sandbox run	No	No	Compute used	Demo badge	Run a Workflow
Builder test run	No	No	Compute used	Builder preview	Workflow Studio
Stopped at the compute limit	Consumed compute may be retained	No	Remainder	Compute-limit stop message	When Runs Fail
Legacy unlock listing	Legacy unlock purchase	Legacy purchase split	N/A	Unlock versus per-run copy	Legacy Unlock

Notable exceptions#

Stopped at the compute limit: Already-consumed compute may be retained. Margin is released. This is separate from an ordinary failure.
Demo and builder test: Never billed.
Bundle expiry: Unused prepaid runs expire after two years. Creators do not earn on runs that were never used.

Was this useful?

Your response helps us improve the documentation.

Run Outcomes Reference

Overview#

Reference table#

Notable exceptions#

Related documentation

Run Outcomes Reference

Overview#

Reference table#

Notable exceptions#

Related documentation

Overview#

Reference table#

Notable exceptions#

Related policies#

Related documentation

Overview#

Reference table#

Notable exceptions#

Related policies#

Related documentation