Terms of service
The short version: pay for the tokens you use, keep your keys secret, do not use the service to break the law, and we serve you as reliably as we can without promising perfection.
Effective 2026-10-17 · contact [email protected]
The service
engy provides an OpenAI-compatible API for running open-weight language models, billed per token. Requests are served on GPU infrastructure we operate or by independent operators on the engy network; how that affects your data, and how to require zero data retention end to end, is set out under Data below. Using the API or the dashboard means you accept these terms. If you use engy on behalf of an organization, you accept them for that organization.
Accounts and keys
You are responsible for all usage under your API keys. Keep them secret; rotate or revoke a key immediately if you suspect it leaked. We may suspend keys or accounts that violate these terms or generate abusive traffic.
Billing
Service is prepaid: usage draws down your credit balance at the per-token rates published on /pricing. Prices can change; the posted price at request time is what you pay. Purchased credits are refundable on request, minus usage. Promotional and granted credits are not refundable and may expire.
Acceptable use
Do not use the service for unlawful activity, to infringe the rights of others, or to attack, probe, or overload the service itself. You are responsible for complying with the license terms of the models you invoke.
Outputs
You own your prompts and, to the extent we hold any rights in them, we assign model outputs to you. Model outputs are generated by open-weight models and can be wrong; you are responsible for reviewing them before relying on them.
Availability
We aim for high availability but offer no uptime guarantee at this stage. At capacity the API returns early 429 responses rather than queueing. Models may be added, upgraded, or retired; material changes are announced on the site.
Data
Handling of prompts, outputs, and account data is described in the privacy policy. Summary: the gateway keeps no content, metadata only for billing.
The engy gateway retains no content. We do not store your prompts or model outputs, and never train on them, unless you opt out as the privacy policy describes.
Zero data retention (ZDR) end to end requires the ZDR flag. A request can be served by a GPU worker that an independent operator runs on the engy network. Some of those workers run confidential computing, which keeps request content sealed from the operator; others do not, and their operators hold administrative access to their own machines. Operators accept a no-retention policy as a condition of serving traffic, and engy audits their responses for integrity, but without confidential computing non-retention is a policy and contractual commitment rather than something engy can technically guarantee. A request sent with the ZDR flag ("provider": {"zdr": true}, or ZDR required on your API key or account) is served only by ZDR-certified workers, and fails with a 503 rather than being sent to any other worker when none is available. A ZDR-certified worker is either a confidential-computing (CC) worker, or a machine engy operates and controls itself, configured so that no request content is logged or kept. Models with such workers are marked ZDR on /pricing. Without the flag, do not send data you are unwilling to expose to a third-party operator.
Liability
The service is provided as is, without warranties of any kind. To the maximum extent permitted by law, our total liability for any claim arising from the service is limited to the amount you paid us in the three months before the claim. We are not liable for indirect or consequential damages, or for what you build with model outputs.
Termination
You can stop using the service at any time; email us to close your account. We may suspend or terminate service for breach of these terms, with a refund of purchased credits when the termination is not for abuse.
Changes
We may update these terms; material changes are posted here with a new effective date. Continued use after a change means acceptance.