refactor: api gateway

[DeJeune]

What this PR does

Before this PR:

• API Server only supported basic Chat Completions (/v1/chat/completions) and Anthropic Messages (/v1/messages) endpoints
• No OpenAI Responses API support
• No model grouping/gateway functionality for routing requests to different providers
• Basic settings UI with limited configuration options

After this PR:

• Full OpenAI Responses API support (/v1/responses endpoint) with streaming
• API Gateway with Model Groups - each group gets a unique URL path (e.g., http://localhost:23333/{groupId}/v1/...) mapped to a specific provider/model
• Enhanced settings UI with endpoint management, model group CRUD, and network exposure options
• Composable validators utility for real-time input validation

Why we need it and why it was done in this way

The following tradeoffs were made:

• Model Groups use createdAt as stable identifier since id can be changed by user for URL customization
• Gateway middleware intercepts /{groupId}/v1/... routes before standard API routes
• Reused existing adapter pattern for Responses API to maintain consistency

The following alternatives were considered:

• Single model endpoint vs Model Groups: Chose Model Groups for flexibility in exposing multiple provider/model combinations
• Separate config vs extended ApiServerConfig: Extended existing config with backwards compatibility via type alias

Breaking changes

• ApiServerConfig type is now deprecated, use ApiGatewayConfig instead (alias provided for backwards compatibility)
• Redux store migration adds new fields (modelGroups, enabledEndpoints, exposeToNetwork) with defaults

Special notes for your reviewer

• OpenAI Responses API implementation follows the official spec: https://platform.openai.com/docs/api-reference/responses-streaming
• Stream adapter emits semantic events (response.created, response.output_text.delta, response.completed, etc.)
• i18n translations added for all 11 supported languages

Checklist

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature.

Release note

feat(api-gateway): Add OpenAI Responses API support and Model Groups

- New `/v1/responses` endpoint with full streaming support
- Model Groups: Create unique API endpoints for different provider/model combinations
- Gateway routing: Access models via `/{groupId}/v1/...` URLs
- Configurable endpoint exposure and network settings
- Enhanced settings UI for gateway management

[kangfenmao]

[DeJeune]

fixed

[0xfullex]

Note

This comment was translated by Claude.

Directory names and variable names have all been changed from apiServer to apiGateway.

---

Original Content

目录名、变量名，都从 apiServer 改为 apiGateway

[vaayne]

[!NOTE]
This comment was translated by Claude.

Directory names and variable names have all been changed from apiServer to apiGateway.

---

Original Content

目录名、变量名，都从 apiServer 改为 apiGateway

Note

This comment was translated by Claude.

Are we planning to only support API Gateway functionality? Do we still plan to expose Cherry's native capabilities in the future?

---

Original Content

我们是打算只支持 API Gateway 的功能吗？今后还准备暴露 Cherry 本身的能力吗？

[0xfullex]

[!NOTE]
This comment was translated by Claude.

Are we planning to only support API Gateway functionality? Do we still plan to expose Cherry's native capabilities in the future?

Note

This comment was translated by Claude.

This was discussed previously, it's just a naming change. apiServer can be confusing internally and externally. The functionality remains the same, still serving the CSaaS responsibility by exposing Cherry's capabilities to the outside.

---

Original Content

这是上次讨论过的，只是一个命名上的更改，apiserver在内外容易混淆。其功能不变，仍是为了CSaaS的职责，对外提供Cherry的能力