> For the complete documentation index, see [llms.txt](https://docs.avis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avis.net/guide/faq.md).

# FAQ

## AVIS General

**Is there a limit on the number of requests?** Yes. Each account has a limit on the number of concurrent requests processed through the AVIS Gateway. This limit increases as you use the service more or add more credit. If you require higher limits for large-scale needs, please contact the Enterprise team.

**Am I charged for failed requests?** If the error stems from the model's infrastructure (system error), you will not be charged. If the error is due to invalid input data and the model has processed a portion of it before detecting the error, that request may still be charged accordingly.

**Does my credit expire?** The validity period of credit follows the terms of the API Service Package at the time of purchase. If the package does not specify a validity period, topped-up credit remains valid until it is used up. Promotional credit or voucher codes may have their own validity periods, depending on the program. You can check your balance details in your account management page.

**Am I charged for the model's start-up time (cold start)?** No. You are only charged for the actual processing time (inference), not the time taken to load or start the model.

**What happens if my account runs out of credit?** When the balance drops below the minimum level, the account will be temporarily locked, and requests through the Gateway will be rejected until you add more credit. Enterprise customers using invoice-based payment methods are not automatically locked.

**How long are files (images/video/audio) generated by the model stored?** Output files are stored temporarily on AVIS infrastructure for a specific period. You should download and store them separately if you need to keep them long-term.

**Can I use AI-generated content for commercial purposes?** It depends on each model in the AVIS Gateway catalogue — each model has its own terms of use from the provider. You should check the licensing information for each specific model before using it for commercial purposes.

**Can I publish my application to the AVIS App Store?** Yes. You can build applications using AVIS Gateway and then publish them to the App Store to reach real users through the AVIS distribution network.

**How does the 10% Platform Fee (Enterprise) apply?** AVIS only charges a transparent 10% platform fee, with no hidden surcharges or setup fees. AVIS only benefits when your product grows.

**Does AVIS support invoice-based payment or volume-based discounts?** Yes, for customers with large usage needs. Please contact the Enterprise/Ecosystem team to discuss a suitable package.

**Why was my request rejected due to content policy violations?** Some models in the Gateway apply automatic content filters. If a request is flagged for violation, the system will refuse to process it, and you cannot retry with the same content.

**What should I do if I have trouble logging in?** If you log in via email/Google and do not receive the verification code or encounter an error, please check the email linked to that account or contact <hi@avis.net> for support.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avis.net/guide/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.