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

# API Pricing & Fees

Avis doesn't sell subscriptions or seats, you pay for what you generate. Every request is billed at the model's own price plus a transparent Avis platform fee, deducted from your prepaid credit balance. There are no setup fees, minimum commitments, or hidden surcharges.

This guide explains the two fee rates, how a charge is calculated, and where to see what you were billed.

***

## How you're charged

Every billable request has two parts:

* **Model cost:** the underlying price of the model you called, set by the model provider and passed through unchanged.
* **Platform fee**: a percentage of that model cost, charged by Avis for running the gateway.

```
Total charge = model cost + (model cost × platform fee)
```

The fee rate depends on *how* you run the model, not which model you pick:

| How you run it                                                           | Platform fee |
| ------------------------------------------------------------------------ | ------------ |
| **API** - direct calls, SDKs, CLIs, and any integration using an API key | **10%**      |
| **Studio** - Running AI on Avis Studio                                   | **20%**      |

***

## A worked example

Say a generation costs **$0.10** in model usage:

| Route             | Model cost | Platform fee | Deducted from balance |
| ----------------- | ---------- | ------------ | --------------------- |
| API (10%)         | $0.10      | $0.01        | **$0.11**             |
| Avis Studio (20%) | $0.10      | $0.02        | **$0.12**             |

The fee scales with your usage, it's never a flat charge, so a request that costs nothing to run costs nothing in fees.

***

## Where to see what you paid

The platform fee is already included in every amount Avis reports back to you. You never get a separate fee line to reconcile.

* **Per request:** `GET /api/compat/v1/usage` returns a `usdCost` on each generation row — the final amount deducted for that request, fee included. See [Usage](/api-reference/introduction/use.md).
* **Before you spend:** the image, video, and audio `estimate` endpoints return `estimatedUserCost` for a request body before you submit it. No credit is deducted and nothing is persisted.
* **Your balance:** `GET /api/compat/v1/balance` returns your current credit balance, or check the [Credits & Billing](https://www.avis.xyz/profile/credits) page in your profile.

**Tip:** Set spend limits on each API key — daily, weekly, monthly, or lifetime, so a runaway loop or a leaked key can't drain your balance. See [How to get API Key](/guide/get-started/avis-api-key.md).

***

## What isn't charged

* **Failed requests caused by our side.** If a request fails because of the model's infrastructure or invalid input, you aren't charged.
* **Cold starts.** You pay for actual inference time, not the time a model takes to load or start.
* **Estimates.** Calling an `estimate` endpoint is free and deducts nothing.

***

## VAT and top-ups

The platform fee is separate from tax. A **10% VAT** applies when you **top up**, and is included directly in your purchase total, it isn't charged again on each request. If you need an invoice, enter your invoice details during top-up. See [How to top up your balance](/guide/get-started/avis-topup.md).

***

## What's Next

* Add credits to your balance, see [How to top up your balance](/guide/get-started/avis-topup.md).
* Create a key and set spend limits, see [How to get API Key](/guide/get-started/avis-api-key.md).
* Track your spend per request, see [Usage](/api-reference/introduction/use.md).

***

## FAQ

### Is the platform fee charged on top of the model price, or taken out of it?

On top. You pay the model's price plus the fee. 10% via the API, 20% for usage on Avis Studio.

### Do I pay the fee twice if a workflow calls the API?

No. Each request is billed once, at the rate for the route it ran through.

### Does `usdCost` already include the fee?

Yes. `usdCost` in your usage records is the final amount deducted for that request, with the platform fee already applied.

### Are there setup fees, monthly minimums, or seat charges?

No. The platform fee is the only charge Avis adds, and it only applies when you actually generate something.

### Am I charged for failed requests?

Not for system-side failures. If the error comes from the model's infrastructure, you aren't charged. If your input was invalid and the model had already processed part of the request before detecting it, that request may still be billed.

### Can I get volume discounts or invoice-based billing?

Yes, for large usage. Contact the Enterprise/Ecosystem team at <hi@avis.xyz> to discuss a package.

### Where do I check my current balance?

At the top of the [Credits & Billing](https://www.avis.xyz/profile/credits) page, or via `GET /api/compat/v1/balance`.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avis.xyz/guide/get-started/api-pricing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
