anomalyco / anomalyco/models.dev
Message API
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
Can you please also include the messaging api for the respective provider also like
Nvidia: openai_completions api
Anthropic: anthropic_messages
Openai: openai_responses
// Standard naming of the providers supported api endpoint
like that can you please include ig it can simply the routing logic to the respective provider easily and simpler instead of doing custom mapping in the app builders end.
Please include the api property also in the provider.
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 provider definitions and the code that builds or consumes provider metadata. Add the requested api property using the stated standard endpoint names, then verify that each supported provider exposes the value consistently and that consumers can use it for routing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100