Why Niu? A Token Management Platform for Developers and Teams

Performance, reliability and economy for people using model APIs. Access models, manage token spending and understand every request.

Developers and teams use model APIs to build applications, work with coding tools, and explore ideas in Chat and Video. As usage grows, they need more than another API key: they need to understand which models they can use, what happened to a request, and where their token budget went.

Niu is a token management platform for those users. Its focus is performance, reliability and economy: access models efficiently, understand failures, and keep spending visible and controlled.

Performance: keep model access efficient

Use documented OpenAI-compatible and Anthropic-compatible endpoints to connect applications and coding tools through a workspace API key. Check the model’s supported capabilities before switching an application.

The Rust gateway supports streaming and has a published gateway benchmark. Those measurements describe historical versions against a deterministic mock upstream. They do not promise the same end-to-end latency or throughput for every model and workload.

Reliability: understand each request

Request history brings status, recorded attempts, reported token usage, timing and charges together. You can distinguish a request rejected before dispatch from an upstream error or an interrupted response.

Configured model routes support bounded failover. An uncertain request must not be blindly replayed: doing so could repeat work or incur another charge. Missing usage evidence remains explicit. See the request evidence guide for supported behavior and limits.

Economy: make token spending visible

Review listed model prices, actual token usage and request charges. Set workspace and API-key budgets for applications and team usage. In-flight reservations count toward applicable spending limits before requests finish.

Economy means making informed choices and keeping spending under control. It is not a claim that every model is cheaper. Model prices and availability depend on configured offers, and unresolved billing evidence must remain distinguishable from a confirmed charge.

One workspace for API, Chat and Video

Call APIs from your applications, compare models in Chat, and revisit saved conversations. Supported video workflows expose saved job state and authorized result access. Availability depends on model configuration and permissions.

Niu’s open-source gateway, dashboard, catalog and Docs can also be self-hosted with PostgreSQL. See the deployment guide and release acceptance matrix for setup and qualification boundaries.

Browse models or follow the quickstart to get started.

为什么选择牛元?面向开发者与团队的词元管理平台

为模型 API 使用者提供性能、可靠性与经济性:接入模型、管理词元开支,并了解每一次请求。

开发者和团队通过模型 API 构建应用、使用编程工具,并在 Chat 和 Video 中探索想法。随着用量增长,他们需要的不只是另一个 API 密钥,还需要知道可以使用哪些模型、请求发生了什么,以及词元预算花在了哪里。

牛元是面向这些用户的词元管理平台,聚焦性能、可靠性与经济性:高效接入模型、理解失败原因,让开支清晰可见、可以控制。

性能:高效接入模型

通过工作空间 API 密钥,使用文档中列出的 OpenAI 兼容与 Anthropic 兼容接口接入应用和编程工具。切换应用使用的模型前,请先检查模型支持的能力。

Rust 网关支持流式响应,并公开了网关基准测试。这些数据来自历史版本与确定性的模拟上游,不代表每个模型、每种工作负载都能达到相同的端到端延迟或吞吐量。

可靠性:理解每一次请求

请求历史集中展示状态、已记录的尝试、上报的词元用量、耗时和费用。你可以区分请求在发送前被拒绝、上游返回错误,以及响应中途断开等情况。

配置的模型路由支持有边界的故障转移。结果不确定的请求不能被盲目重放,否则可能重复执行或再次计费。缺失的用量证据会明确标示。支持的行为与限制见请求证据指南。

经济性:让词元开支清晰可见

查看模型标价、实际词元用量与请求费用,为应用和团队设置工作空间及 API 密钥预算。进行中的请求会先预留额度,并计入相应的开支限制。

经济性意味着做出有依据的选择、控制开支,并不意味着每个模型都更便宜。模型价格和可用性取决于已配置的报价;尚未解决的计费证据必须与已确认费用保持区分。

在同一工作空间使用 API、Chat 和 Video

从应用调用 API,在 Chat 中比较模型,并重新打开已保存的对话。支持的视频工作流提供持久化的任务状态和经授权的结果访问。具体可用性取决于模型配置和权限。

牛元的开源网关、控制台、模型目录和文档也可配合 PostgreSQL 自托管。部署与能力验收边界见部署指南和发布验收矩阵。

浏览模型或按照快速入门开始使用。

Make your first model request

Connect an application, explore models and understand your token usage.

Get startedView on GitHub