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#
Top-ups can be paused. When they are, the dashboard says so, the top-up request answers 403 deposits_closed, and the credit you already have keeps working. Support says whether buying credit is open right now.
While top-ups are open:
| 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. Send nothing to an address from an earlier session: an address is bound to its own top-up, and a top-up can only be started while deposits are open.
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, at or below the input price. These tokens hit the provider's 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. The cached price is not below the input price on every model: where a provider gives no cache discount the two are equal, and the catalog prints the figure for that model.
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.
The published price is the promise, so a request is never silently served for more than that price. When no serving route can answer a request within it, the request is refused with 503 upstream_unavailable and nothing is charged: retry later, or use another model. The refusal is a policy of the price list, not an error in your request. Errors lists the code and the retry rule.
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 at the platform search price, which is zero while the platform runs its own search engine. 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.
The payment record#
Every confirmed payment is in the dashboard with what it was, the amount, the date, the asset, the network, the status and the transaction id. There is no tax document, invoice or downloadable receipt while the operator has no published legal entity: the dashboard record and the payment email are the whole record of a payment.
Withdrawal and refunds#
Consumers may withdraw within 14 days of a purchase by writing to support@rackduck.com with the payment reference. The operator records the request with a reference and acknowledges it by email; section 6 of the terms of service is the legal text, the amount that would be refunded and the model form for a withdrawal by message. 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 confirm the address and the asset with the operator, and the operator confirms the amount and the network before sending.