You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,7 +159,8 @@ The gateway continues running when the panel is hidden. Quitting ReRouted stops
159
159
|`GET /`| Same unauthenticated local health response as `/health`|
160
160
|`GET /health`| Local gateway health and listening port |
161
161
|`GET /v1/models`| Enabled direct models and named routes |
162
-
|`POST /v1/chat/completions`| Streaming or non-streaming routed completions |
162
+
|`POST /v1/chat/completions`| Streaming or non-streaming routed chat completions |
163
+
|`POST /v1/responses`| Streaming or non-streaming routed Responses API requests |
163
164
164
165
Requests require a generated bearer key except for `/` and `/health`. OpenAI-style image inputs inside chat-completion messages are supported when the selected upstream model accepts them. The separate `/v1/images` generation API, embeddings, audio, and the rest of the OpenAI platform API are outside ReRouted's scope.
|`POST /v1/responses`| Bearer key | Responses requests adapted through the chat-completions router |
53
54
54
55
The default bind is `127.0.0.1:4949`. Settings can switch the host to `0.0.0.0` for LAN or Tailscale access. CORS is currently `*`, so the bearer key is the gateway's access boundary when network binding is enabled.
0 commit comments