> 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/get-started/avis-api-vs-studio.md).

# Avis API or Avis Studio: which should you use?

Avis has two ways to use the same AI models. **Avis API** (Gateway) is for developers who call models from code, scripts, or tools like Claude Code. **Avis Creative Studio** is a visual canvas for creators who build images, video, and audio without writing code. Both use the same credit balance. The difference is how you work and the platform fee.

***

## At a glance

|                | **Avis API**                                                                                         | **Avis Creative Studio**                                                                                                    |
| -------------- | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Best for       | Developers, products, automation                                                                     | Designers, video editors, production teams                                                                                  |
| How you use it | HTTP requests, SDKs, CLIs, integrations                                                              | Visual canvas with connected nodes                                                                                          |
| Coding needed  | Yes                                                                                                  | No                                                                                                                          |
| Platform fee   | **10%** of model cost                                                                                | **20%** of model cost                                                                                                       |
| Billing        | Same prepaid credit balance                                                                          | Same prepaid credit balance                                                                                                 |
| Get started    | [Quickstart](https://github.com/coin98/documentation/tree/docs_avis/guide/get-started/quickstart.md) | [What is Avis Creative Studio?](https://docs.avis.net/avis-creative-studio/getting-started/what-is-avis-creative-studio.md) |

***

## Choose the API if you...

* Are building an app, website, or product that calls AI
* Want to run AI from coding agents like Claude Code, Codex, or Gemini CLI. See [Integrations](https://docs.avis.net/integrations/overview.md)
* Need batch jobs, scheduled tasks, or automated pipelines
* Want the lower fee

## Choose Studio if you...

* Want to create and edit visually, chaining image → video → audio → VFX
* Work on a project with teammates
* Prefer clicking to writing code

***

## FAQ

### Do I need two accounts?

No. One Avis account and one balance cover both.

### Do I pay the fee twice if Studio calls the API?

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

### Can I use the same models in both?

Generally yes.


---

# 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/get-started/avis-api-vs-studio.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.
