UniAPI started as something modest: a handful of common capabilities exposed as public endpoints for my own projects, callable without registration. That version ran for two years. Then I replaced it entirely.
The reason was straightforward. What is scarce now is not an endpoint — it is that the official subscriptions to the best models cannot be reached from a project as an API. A subscription is built for a person to use; a project needs an interface. There is a layer missing in between.
What it is now
UniAPI is that layer: a gateway that collapses several accounts into one OpenAI-compatible surface.
- Upstream are my own official subscriptions and each vendor's API; downstream exposes only standard paths like
/v1/chat/completions.
- Switching model or vendor means changing a model name, not the calling code.
- Keys, quota, request logs and usage all live in the console, so a failure can be traced to a specific call.
- It runs on my own machine — accounts and data never pass through a third party.
Underneath it is the open-source New API, with CLIProxyAPI bridging the subscription side. I wrote up how that goes together separately.
Why it is still called UniAPI
The domain did not change and neither did the name, because the problem did not change: make "calling a capability" a simple thing again. What changed is that the sentence pointed at something else in 2023 than it does now.
The difference is that I am clearer about its edges this time. It is my own infrastructure, not a public service for everyone else.
UniAPI started as something modest: a handful of common capabilities exposed as public endpoints for my own projects, callable without registration. That version ran for two years. Then I replaced it entirely.
The reason was straightforward. What is scarce now is not an endpoint — it is that the official subscriptions to the best models cannot be reached from a project as an API. A subscription is built for a person to use; a project needs an interface. There is a layer missing in between.
What it is now
UniAPI is that layer: a gateway that collapses several accounts into one OpenAI-compatible surface.
/v1/chat/completions.Underneath it is the open-source New API, with CLIProxyAPI bridging the subscription side. I wrote up how that goes together separately.
Why it is still called UniAPI
The domain did not change and neither did the name, because the problem did not change: make "calling a capability" a simple thing again. What changed is that the sentence pointed at something else in 2023 than it does now.
The difference is that I am clearer about its edges this time. It is my own infrastructure, not a public service for everyone else.