API Terms

1.Keys

• Keys come from the Developers page. A key is shown once. Store it like a password.
• Don’t put a key in code that ships to browsers, apps or public repositories. If one leaks, revoke it at once. Charges made with your key before you revoke it are yours.
• Each person may hold a limited number of keys. A key can’t make, change or revoke keys.
• Don’t share a key between companies, or resell or white-label access to diffusr, without our written OK.

2.Prices, credits and budgets

• The price of each call is quoted free with dry_run. A started call is charged at most that price. Failed, canceled or undelivered work is not charged.
• The API prices on the docs’ Prices page are the model prices; tools that shape a result for you are priced higher and quoted per call. We may change prices. A change applies to calls started after it; a quote already given holds until it expires (one hour).
• Credits are one pot shared with the app (yours or your team’s). The refund rules in the Terms apply.
• You can set daily and monthly budgets on keys and on your account. A call that would pass a budget is refused. Budgets are a safety tool, not a promise: you pay for what your keys spend.
• Test keys return real prices and fake results and charge nothing. Test results are not for publication.

3.Limits and fair use

• Requests and jobs at once are limited (docs: Limits). A request over a limit is refused with Retry-After; it is never queued and never charged.
• Don’t work around limits with extra accounts or keys. Don’t send traffic meant to test our systems’ breaking points without asking. Found a security problem? Tell us at hello@diffusr.ai and don’t use it.
• If you need more, ask us. We may raise limits for an account.

4.What you send and what you get

• What you upload and what you make is yours, as in the Terms. We use it only to run diffusr for you and don’t train AI models on it.
• Files uploaded through the API are kept for a set time after you last used them, then deleted. Today that is 7 days for live keys and 24 hours for test keys; if we change it, we update this page.
• Requests are logged with the tool, model, price and charge, for billing and support. Keys are stored only as a hash.
• Only send files and links you have the right to use. Get consent from every real person whose face or voice you use.
• Callback URLs must be public https addresses you control. We send results there, signed. You are responsible for what your endpoint does with them.

5.AI agents

If an AI agent uses your key or your login, you are responsible for what it does, including what it spends. Keep budgets on. Agents must follow the Terms and these API terms.

6.Changes, pausing and ending

• We may pause new API starts for everyone, for one model, or for one supplier (for example in an outage). Work already started finishes where it can.
• We may block a key or an account that breaks the Terms or these API terms.
• We may change the API. We try to keep existing calls working. Before we remove a documented call or field, we say so in the docs at least 30 days ahead, unless security or the law makes us move faster.

7.No warranty, limits of liability

The Disclaimers (section 13) and Limits of liability (section 14) in the Terms of Service apply to the API, the MCP server and the SDKs too.

8.Contact

Questions about these terms: hello@diffusr.ai.