Supported protocols
OSW accepts three upstream protocols and recognizes them on the same port.
| Protocol | Endpoint | Typical clients |
|---|---|---|
| OpenAI Chat Completions | /v1/chat/completions | The vast majority of OpenAI-compatible tools |
| OpenAI Responses | /v1/responses | Codex and others |
| Anthropic Messages | /v1/messages | Claude Code and others |
How paths are recognized
One port serves all three protocols, and paths are recognized with or without the /v1 prefix:
http://127.0.0.1:9300/v1/chat/completions
http://127.0.0.1:9300/chat/completions
How to fill in the Base URL
| Your client | Base URL |
|---|---|
| OpenAI-compatible | http://127.0.0.1:9300/v1 |
| Anthropic | http://127.0.0.1:9300 |
Anthropic takes no /v1
Anthropic clients append /v1/messages themselves. Adding /v1 makes it /v1/v1/messages, which the proxy does not recognize, and it returns 404.
GET /v1/models
Served locally, returning your configured model names (that is, the logical models), and it never forwards upstream. So curl http://127.0.0.1:9300/v1/models both verifies the service is running and shows the model names you can currently write.
Transport modes
| Mode | Behavior |
|---|---|
| Non-streaming | Handled as-is; the full payload is read before responding. |
| Streaming | SSE frames passed through one by one. Once delivery starts, an interruption aborts it — no reassembly. |
| WebSocket | Handled per connection. |
Protocol conversion
No conversion by default: a request is forwarded as-is in the protocol it arrived in. Only after a channel explicitly enables conversion can it accept requests in another protocol:
- Native requests come first: when a request's protocol matches what the channel supports, the native channel is used directly.
- Converted requests are used only when there is no native candidate.
- Conversion is a compatibility layer: some parameters may be lost, and you should not expect it to be fully equivalent to native.
Enabling conversion affects one protocol endpoint at a time
The conversion toggle lives on the protocol endpoint row in the provider model edit dialog (see Providers & models).
With protocols settled, go to Client configuration to hook up your tools.
'%3e%3cpath%20d='M44.867217,0.0054376148%20C130.715579,1.00591567%20200,70.9091172%20200,156.994562%20L199.986321,155.127494%20C199.384888,180.009127%20179.026368,199.994562%20154,199.994562%20L46,199.994562%20C20.5949015,199.994562%200,179.399661%200,153.994562%20L0,45.9945624%20C0,21.0975659%2019.7793434,0.820282524%2044.4815926,0.0191499894%20Z'%20fill='%2300D492'%3e%3c/path%3e%3cpath%20d='M123.867217,0.0054376148%20C209.715579,1.00591567%20279,70.9091172%20279,156.994562%20L278.986321,155.127494%20C278.384888,180.009127%20258.026368,199.994562%20233,199.994562%20L125,199.994562%20C99.5949015,199.994562%2079,179.399661%2079,153.994562%20L79,45.9945624%20C79,21.0975659%2098.7793434,0.820282524%20123.481593,0.0191499894%20Z'%20id='clarify-right'%20fill-opacity='0.6'%20fill='%2300F6C9'%20transform='translate(179,%20100)%20rotate(-90)%20translate(-179,%20-100)'%3e%3c/path%3e%3cpath%20d='M199.979267,154.416906%20L199.984438,155.157125%20L199.962366,155.872459%20C198.977251,180.406837%20178.776104,199.994562%20154,199.994562%20L124.372438,199.994125%20L124.249053,199.994081%20C99.6939678,199.603921%2079.8122712,179.973634%2079.01915,155.518407%20L79.0054376,155.132783%20C79.5830823,105.566626%20103.129768,61.5221348%20139.498462,33.1463428%20C175.69419,61.3871018%20199.186123,105.143863%20199.979267,154.416906%20Z'%20id='形状结合'%20fill='%2300F692'%3e%3c/path%3e%3c/g%3e%3c/g%3e%3c/svg%3e)