Legal & privacy

API Terms

The additional terms for using the DeepAny API, API keys and API credits in your own products and services.

Last updated

1. Scope

These API Terms apply when you create an API key or send requests to api.deepany.ai. They are part of the Terms of Use of DeepAny LLC ("DeepAny", "we", "us") and add to them; where the two differ for API use, these API Terms apply. The Privacy Policy and the Guidelines also apply.

If you use the API for a company, you confirm that you may bind that company to these terms. "You" then means the company.

2. API keys and security

API keys are created on your Profile page and belong to your account. You are responsible for every request made with your keys, including requests made by your software, your staff and anyone who obtains a key from you.

  • Keep keys secret. Send them only in request headers, never in URLs, client-side code, public repositories or logs.
  • Rotate a key at once if you suspect it leaked; revoke keys you no longer use. Revoking returns the key's unused API credits to your account.
  • Webhook secrets sign the callbacks we send you. Verify the signature before trusting a callback.
  • Do not share one key across unrelated products or customers. Create a key per integration so usage, limits and revocation stay separable.

3. API credits and charges

API requests are paid with API credits, a prepaid balance separate from Studio credits, daily credits, reward credits and subscriptions. API credits cannot be used in DeepAny Studio and Studio balances cannot be used through the API. API credits have no cash value, are not transferable to another account and are non-refundable except where the law or the purchase terms require otherwise.

  • The credits a job costs depend on the service and its settings. The current list is published on the API page and in the API's own price endpoint, and it can change. The price in force when a job is created is the price you pay for that job.
  • Credits are reserved when a job is created and are returned automatically when the job fails on our side, is cancelled before it finishes, or expires without a result. A job that completes is charged even if you do not download the result.
  • A job we refuse for content or safety reasons is not charged. Repeated refusals may lead to review of the account.
  • Purchases are made on the Pricing page under the payment terms shown at checkout. We do not store card details; payment providers process payments under their own terms.

4. Acceptable use and your end users

You may only send media and prompts that you have the right to use and that comply with the Guidelines. When your product lets other people submit content or receive results, you are responsible for them: you must obtain the consents the law requires, keep the Guidelines enforceable in your own terms, and stop users who abuse the service.

  • Do not use the API to create content that depicts a real person without their authorization, that sexualizes minors, that harasses, defames or deceives, or that breaks any law where you or your users are.
  • Do not use the API to build or train a competing generation model, to scrape or redistribute our models, workflows or weights, or to probe our systems beyond documented use.
  • Do not circumvent rate limits, authentication, billing or safety checks, and do not hide the origin of requests.
  • Automated use is expected, but you must respect published rate limits and back off when you receive a 429 or 503 response.

We may ask you to describe how your product uses the API, and we may suspend keys while we review a report of misuse.

5. Resale and attribution

You may use API results in your own products and services, including paid ones, and you may set your own prices for your users. API results carry no DeepAny watermark. You may not present yourself as DeepAny, use our names or logos without written permission, or state or imply that we endorse your product or review its content.

Rights in the results you create are governed by the Terms of Use. You remain responsible for the rights in the inputs you provide and for how results are used downstream.

6. Availability, limits and changes

The API is provided on an "as available" basis. We run API jobs on a dedicated pool of workers and do not cap how many jobs a key can run at once, but capacity is finite: jobs queue in order and the queue position is reported. We may change rate limits, prices, services, parameters, output formats and the API itself. We announce breaking changes on the API page in advance when we reasonably can; security fixes and legal requirements may need immediate changes.

There is no service-level agreement unless you have a separate written agreement with us. Scheduled maintenance and outages are shown on the status page.

7. Data and privacy

Inputs and results are processed to run your jobs and are deleted from the workers after a short retention window described in the API documentation; download your results promptly. We keep job records (service, settings without media, timing, cost, status, error) and security logs for billing, abuse prevention and support. We do not use your API inputs or outputs to train models.

Where your users' personal data passes through the API, you are the controller of that data and we process it on your behalf to deliver the service, as described in the Privacy Policy. You must have a lawful basis for sending it to us and must not send data you are prohibited from transferring.

8. Liability and termination

To the extent the law allows, our liability for API use is limited to the amount you paid for API credits in the three months before the event giving rise to the claim. We are not liable for indirect losses, lost profits, or losses caused by your product, your users or third-party services. Mandatory consumer rights are not affected.

You may stop using the API at any time by revoking your keys. We may suspend or revoke keys, or terminate API access, for breach of these terms, for unpaid or disputed charges, for legal reasons, or on reasonable notice if we discontinue the API. On termination, unused API credits are handled as described in the purchase terms and the Terms of Use.

Questions about these terms: contact us.