Billing & Spend Caps
API runs bill identically to product UI runs. Keys optionally enforce spend caps before a run starts.
Developers responsible for API spend.
API runs bill identically to product UI runs. Keys optionally enforce spend caps before a run starts: useful for staging keys, partner integrations, and blast-radius control.
For wallet funding details, see API Runs (billing guide).
Funding order#
When a run starts, Edgaze uses available funding in this order:
- Eligible locked bundle for the pinned workflow version.
- Wallet balance for the displayed run price.
Spend caps#
Caps can be daily, monthly, or lifetime. When a request would exceed the key's cap, POST /runs returns 402 spend_cap_reached and does not start a run.
Pricing visibility#
Workflow list and detail responses include displayedRunPriceUsd, the estimated run price shown to the buyer. Prefer GET /workflows/{id} when you need the latest estimate. GET /runs/{id} returns displayedChargeUsd when the final charge is available. For workflows that use your provider credentials, the provider may bill that account separately.
Was this useful?
Your response helps us improve the documentation.