Billing and credit
zdr.sh is prepaid. You buy credit in crypto, the balance sits in EUR, and a request draws it down token by token. There is no subscription, no monthly fee and no automatic renewal: the balance and the next request are the whole relationship.
Paying#
| Step | What happens |
|---|---|
| Amount | You choose the amount to add, from the smallest the top-up screen offers up to the ceiling it shows |
| Asset | BTC, ETH, XMR or USDT, each on the network the screen names |
| Address | The screen gives an address and, for Monero, the payment id that goes with it |
| Credit | The balance moves once the transfer reaches the confirmations that asset requires |
The amount of credit is fixed when the screen issues the address, and that address belongs to that top-up alone. A transfer below the minimum the asset accepts, or one that omits the Monero payment id, is not credited automatically: write to support with the transaction id and it is matched by hand.
How a request is priced#
A request is counted in three buckets, and the price is the sum of each bucket times its published price per 1M tokens, in EUR:
| Bucket | Priced |
|---|---|
| Uncached input | The input price |
| Cached input | The cached price, the cheapest. These tokens hit the prompt cache |
| Output | The output price. Reasoning tokens are output tokens, never a bucket of their own |
A cache write is free: the written tokens are included in the uncached input price, so there is no fourth price.
Prices are published and fixed per model, so a request is charged the price the list showed when it ran. Models has the current figures.
Every response says what it cost: x-token-cost, in EUR, as a trailer on a stream because the price is known at the end. The dashboard breaks a period down by the same buckets; the usage endpoint gives the day's totals.
Two things change the price of a request:
- The response cache. With the key's response cache on, a repeated request is answered from the cache for ten minutes and billed at 10 percent of its price.
x-token-cache: hitsays so. Optimizations. - The web tools. A search is billed per answered query, and a browse is free. Neither is a model request.
The hold before a request and the settle after it use the same price list, so the price you see is the price you pay. An aborted stream is billed for what the model had produced when the client left.
Invoices#
The dashboard shows the invoice information for each confirmed payment: the amount, the date, the asset, the network and the transaction id. zdr.sh does not issue PDF invoices or receipts. Where the law requires a tax document, write to support.
Withdrawal#
Consumers may withdraw within 14 days of a purchase. The dashboard has a withdrawal button that shows what would be refunded before you confirm: the unused balance of the top-up. The withdrawal page has the full instructions and a form for when you cannot sign in. Purchases made as a business are excluded, as the law provides.
Refunds are paid in crypto, never to a card or a bank account, because no card or bank account was ever charged. You name the address and the asset when you ask, and the operator confirms the amount and the network before sending.