DamageBDD Pricing: Execution Estimates and Payment Quotes
Understand step-based execution cost, concurrency, DAMAGE units and Lightning top-up quotes without relying on historic rates.
Price the work before running it
DamageBDD's documented accounting measures execution work in DAMAGE. The cost of a feature depends on the steps implemented by the installed release and how many times they run, including concurrency. A run can consume work while reporting a failure; payment does not buy a passing result.
Obtain the dry-run estimate or quote from the deployment you will use. Confirm its treatment of failed steps, retries and interrupted runs before submitting a paid workload. The documentation does not establish one tariff across all operators or releases.
Separate execution units from the purchase rate
| Quantity | Meaning |
|---|---|
| Execution estimate | DAMAGE required for the selected feature and workload |
| Token units | 1 DAMAGE = 100,000,000 base units |
| Purchase quote | Satoshis requested for the specified DAMAGE credit |
| Other costs | Any separately quoted network, service or integration charges |
For illustration, ten executions of a step priced at one DAMAGE would cost ten DAMAGE before any separately specified charges. This arithmetic example is not a quote for HTTP, Selenium, Appium or another module.
Earlier pages contained conflicting Appium tariffs and a fixed sats-per-token price. Those values are not retained as current prices. A third-party market quote also does not establish the rate or availability of a platform top-up.
Request a Lightning top-up
For a scriptable purchase and first test, follow the
Python quickstart for humans, bots and LLM agents.
It documents POST /invoices with amount_sats, invoice verification and
confirmation that DAMAGE has arrived before execution.
- Open the dashboard and check the account and wallet model.
- Request a quote showing the DAMAGE amount, sats amount, fees and expiry.
- Check the invoice details in your Lightning wallet before paying.
- Confirm invoice settlement and the credited DAMAGE balance separately.
The documented listener transfers credits from a node/admin account; this is not a claim of atomic exchange or automatic refund on an interrupted credit. Use the deployment's support/reconciliation process for an uncertain result. See payment flows and token accounting.
External acquisition and custody
The Coinstore DAMAGE/USDT market is an alternative acquisition route, subject to the provider's current availability and eligibility rules. The Python quickstart explains how to verify the destination and fund the account you intend to execute with.
If acquiring DAMAGE externally, verify the network, contract, destination, fees and actual transfer support. Market availability, withdrawal support and prices require a current check with that provider. No exchange listing, liquidity or buyback guarantee is made by this page.
A hosted Aeternity wallet is custodial even if the Lightning payment originated from a self-custodial wallet. Review account access and the token terms for the chosen arrangement.
Scope a paid integration
For help with acceptance evidence, private knowledge or specialised infrastructure, begin with a bounded evaluation. Agree the deliverable, environment, acceptance criteria, price in sats and payment terms for that engagement through the project contacts.