Refactor Route
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 314
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Could you consider refactoring the project’s routing? For example, move features like billing under the /mgmt admin endpoint and mount the OpenAI-related interfaces directly under /v1.
```
Mgmt Api
/v1/mgmt/api-keys
/v1/mgmt/auth/**
/v1/mgmt/billing
/v1/mgmt/models
/v1/mgmt/providers
/v1/mgmt/session
OpenAI API
/v1/chat/completions — Chat Completions
/v1/images/generations — Image generation
/v1/images/edits — Image editing
/v1/embeddings — Embeddings
/v1/responses — Responses
/v1/audio/speech — Audio speech
/v1/audio/transcriptions — Audio transcriptions
/v1/audio/translations — Audio translations
/v1/models — List available models
Rerank API
/v1/rerank - Rerank
Anthropic API
/anthropic/v1/messages — Messages
/anthropic/v1/models — List available models
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current route definitions and comparing them with the endpoint grouping listed in the issue. Done means the management, OpenAI, Rerank, and Anthropic interfaces are mounted at the specified paths, with existing behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100