Feature Request - Add OneProvider API Endpoint Support

Hello TypingMind Team,

I would like to submit a feature request to add support for the OneProvider API endpoint in TypingMind Proxy.

Current Issue

When attempting to use OneProvider (https://api.oneprovider.dev/v1/messages ) as a custom model endpoint, TypingMind Proxy displays the following error:

"Sorry, TypingMind Proxy does not support the endpoint 'https://api.oneprovider.dev/v1/messages' yet. Please contact support if you think we should add it."

This prevents users from accessing Claude models through OneProvider, which is a viable alternative to the official Anthropic API.

About OneProvider

OneProvider is an Anthropic-compatible API gateway that provides access to Claude models with the following characteristics:

•Website: https://oneprovider.dev

•API Endpoint: https://api.oneprovider.dev/v1/messages

•Supported Models: Claude Opus 4.8, Claude Sonnet 4.6, Claude Haiku 4.5

•API Compatibility: Fully compatible with Anthropic Messages API

•Authentication: API key via HTTP header (x-api-key )

•Payment Method: Cryptocurrency-based (no credit card required)

•Key Features:

•No account signup required (key-based authentication)

•Pay-as-you-go pricing

•No prompt logging or training on user data

•EU-based infrastructure (Frankfurt)

Why This Matters

Adding OneProvider support would provide TypingMind users with:

1.Alternative Payment Options: Users who prefer or can only use cryptocurrency payments now have a viable option

2.No Account Requirement: Users who don't want to create an Anthropic account can still access Claude models

3.Increased Flexibility: More provider options give users greater control over their AI infrastructure

4.Competitive Advantage: TypingMind would be one of the few frontends supporting multiple Claude API providers

Technical Details

OneProvider's endpoint is fully compatible with the Anthropic Messages API specification. The required headers are:

Plain Text

x-api-key: <oneprovider-api-key> anthropic-version: 2023-06-01 content-type: application/json

The request/response format is identical to the official Anthropic API, making integration straightforward.

Reference Documentation

•OneProvider Official Docs: https://oneprovider.dev/docs

•OneProvider Status Page: https://oneprovider.dev/status

•OneProvider API Overview: https://oneprovider.dev/docs#overview

•Anthropic API Documentation: https://docs.anthropic.com/

Additional Context

I currently use OpenRouter with TypingMind without issues, which shows that TypingMind's infrastructure can support multiple third-party API providers. Adding OneProvider would be a natural extension of this capability.

Suggested Implementation

Since OneProvider uses the Anthropic Messages API format, the implementation could potentially be as simple as adding the endpoint URL to the TypingMind Proxy's supported endpoints list, similar to how other Anthropic-compatible providers might be supported.

Thank you for considering this feature request. I believe this would be a valuable addition to TypingMind's ecosystem.

Best regards,

Anton

abusalm09@gmail.com