> For the complete documentation index, see [llms.txt](https://ai-docs.akile.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.akile.ai/api-jie-ru/models-and-channels.md).

# 模型与渠道

AK AI Gateway 会把模型供应商、渠道、分组、价格和可用状态整理到控制台中。用户可以在可用渠道页面查看自己当前能调用的模型。

## 查看可用渠道

入口：<https://aigateway.akile.ai/available-channels>

页面会展示：

* 渠道名称。
* 渠道描述。
* 平台类型，例如 Claude、GPT、Gemini、DeepSeek 等。
* 可用分组，包括公共分组和专属分组。
* 支持模型。
* 模型计费方式和价格信息。

## 分组与倍率

不同用户、订阅或渠道可能属于不同分组。分组会影响：

* 可调用的模型范围。
* 计费倍率。
* 是否能访问专属渠道。
* 是否受到额外限制。

如果同一个模型在不同分组或渠道中都有显示，以控制台展示的实际倍率和可用状态为准。

## 计费方式

可用渠道页面会展示模型的计费模式，常见包括：

* 按 Token 计费：通常区分输入、输出、缓存写入、缓存读取。
* 按请求计费：每次请求固定费用。
* 按图片计费：图片生成或图片输出按请求或数量计费。

Token 价格通常以每百万 Token 展示。

## 查询模型列表

兼容 OpenAI 的客户端通常会请求：

```
GET https://aigateway.akile.ai/v1/models
```

该接口需要携带有效 API Key。未携带密钥时会返回鉴权错误。

## 模型选择建议

* 先用可用渠道页面确认模型名。
* 开发测试使用低成本模型。
* 生产环境给不同业务创建不同 API Key。
* 对稳定性要求高的任务，优先选择可用状态稳定、分组倍率清晰的模型。
* 对成本敏感的任务，关注输入输出 Token 价格和缓存价格。


---

# 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://ai-docs.akile.ai/api-jie-ru/models-and-channels.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.