How runs are priced and paid for

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.

Wallet, prepaid bundles, and API funding. How Edgaze chooses what to charge when you run a workflow.

What you pay when a run fails, is cancelled, or is stopped for exceeding its compute limit.

How to request a wallet refund and what is not refundable.

How creators set margin, how compute is estimated, and what buyers see at checkout.

How creator earnings accrue, clear, and pay out.

Plus plan runs with your own API key: what you pay Edgaze and what you pay your provider.

When Edgaze switches to a backup model, your price stays the same.

Billing for workflow runs triggered through the REST API, including spend caps.

How prices lock to a workflow version and what happens when creators publish new versions.

How composed workflows price nested workflows and how each creator earns.

When prepaid bundles expire, what happens to unused runs, and refund options.

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

One-time purchase listings from before per-run pricing existed.