1. The service
WISPR runs a catalogue of open models on sealed hardware, routes shards of requests to third party frontier models, and keeps prepaid credit for both. Usage is billed at the model's published price, with enclave time included, from your balance. WISPR charges one fee when money comes in, at the rates on the pricing page: 8% by card, 6% in crypto or per request over x402, 0% while $500 of $WISPR is staked for 90 days. There is no per token markup, no subscription and no minimum spend.
2. Accounts
- An email account belongs to whoever can sign in with the email and password or reset it by link. An anonymous account belongs to whoever holds its recovery phrase. We cannot verify who that is, so we treat the holder as the owner.
- We cannot reset or recover an anonymous account. If the phrase is lost, the balance is lost. This is a consequence of not knowing who you are, not an oversight.
- Keys carry budgets you set. Requests within a live key's budget are authorised by you.
- An account with no activity for 24 months may be archived. Its balance is held and restored on the next sign in.
3. Credit, top ups and refunds
- Credit is prepaid, denominated in US dollars, spendable on any model in the catalogue and any frontier shard. It does not expire.
- Crypto top ups are credited after network confirmations, minus the fee. A transfer of the wrong asset or to the wrong network cannot be recovered; take the address from the dashboard or the API.
- Card top ups can be refunded on request within 24 hours if none of the credit has been spent, minus the processor's cost. Crypto top ups, x402 payments and redeemed deposit notes are final.
- If a model charges less than estimated for a request, the difference stays in your balance. If a request fails before any model is called, nothing is charged.
- Credit is not transferable between accounts and cannot be withdrawn to a wallet or a card. Deposit notes credit an account; they are not a mixing service and cannot be redeemed to an address.
4. Acceptable use
The models in the catalogue do not refuse. This section is where the limits live, and we enforce it at the account level. You may not use the service to:
- create, request or distribute sexual content involving minors, or any content that sexualises minors, in any form;
- create intimate or sexual imagery, video or voice of a real, identifiable person without their consent, or content that impersonates a real person in order to deceive;
- plan, incite or provide material support for violence against people, or produce material intended to help carry out an attack;
- build or operate malware, fraud, phishing or harassment aimed at other people or at systems you do not own or have no written permission to test;
- launder funds, evade sanctions or structure deposits; the deposit note pool refuses sanctioned addresses and we cooperate with lawful requests within the limits of what we hold;
- interfere with the enclaves, the exits, other accounts or the service itself.
Within those limits, the service is yours. Fiction of any tone, adult content between adults, security research on your own systems, legal and medical questions, and work that other providers decline are intended uses. An account found breaching this section is closed and its balance forfeited.
5. Models and refusals
- Catalogue models run on hardware we rent. Figures on the catalogue cards are measured on our deployments and may change as models are updated; the live list is at
GET /v1/models. - Frontier models are provided by third parties under their own terms. They receive pseudonymised shards only. If a frontier shard is refused, it is rerouted once to a catalogue model and the receipt records it. If that is refused too, you receive a typed error, never a silently weaker answer.
- Model output is generated by software. We do not review it and are not liable for it. You are responsible for what you do with it.
6. Privacy claims
Our privacy claims are listed in the privacy policy and the docs. They are engineering statements about how the system is built, backed by published enclave measurements. They describe their own limits. They are not a guarantee against every attack. If we find a flaw we say so on the blog and fix it.
7. Availability and liability
The service is provided as is. Providers go down, exits get blocked, enclave capacity runs out, chains congest. We return typed errors instead of silent downgrades, but we do not promise uptime. To the extent the law allows, our total liability to you for any claim is limited to the balance in the affected account at the time of the problem. We are not liable for the output of any model or for actions taken by your software.
8. Changes
We may change these terms. Material changes are posted on the blog and dated here at least 14 days before they apply. Continuing to use the service after that date means you accept them.