Skip to content

feat: Concentrate.ai dual-protocol support and Responses API client - #91

Merged
Patel230 merged 4 commits into
mainfrom
feat/concentrate-ai-integration
Jul 29, 2026
Merged

feat: Concentrate.ai dual-protocol support and Responses API client#91
Patel230 merged 4 commits into
mainfrom
feat/concentrate-ai-integration

Conversation

@Patel230

Copy link
Copy Markdown
Contributor

Add Concentrate.ai provider integration with dual-protocol routing:

  • Implement ConcentrateClient with ProtocolRouter for dual-protocol routing (Chat Completions for OpenAI models, Messages API for Anthropic models)
  • Add ConcentrateResponsesClient using the production-ready Responses API
  • Add protocol map with UsesMessagesAPI() for per-model protocol selection
  • Add file-based pricing cache with 24-hour TTL (reasoning + tiered pricing)
  • Add context_management capability extraction
  • Make auth optional for /v1/models per official docs
  • Add reasoning and tiered pricing capture with proper units handling
  • Update provider registry to use Responses API client as default
  • Add comprehensive tests for all new functionality

Includes both commits:

  1. Add Concentrate.ai provider integration
  2. Add Concentrate.ai dual-protocol support and Responses API client

Patel230 added 4 commits July 28, 2026 22:40
- Add concentrate provider to defaultProviders() and defaultDeployments()
- Register concentrate in live fetcher registry with native capability extraction
- Add ProviderConcentrate constant and ConcentrateRuntimeProfile
- Add CONCENTRATE_API_KEY and CONCENTRATE_BASE_URL config support
- Add concentrate-direct deployment for OpenAI-compatible endpoint
- Update provider count tests (22→23)
- Add max_input_tokens/max_tokens support to listModelJSON for Concentrate format
- Implement ConcentrateClient with ProtocolRouter for dual-protocol routing
  (Chat Completions for OpenAI models, Messages API for Anthropic models)
- Add ConcentrateResponsesClient using the production-ready Responses API
- Add protocol map with UsesMessagesAPI() for per-model protocol selection
- Add file-based pricing cache with 24-hour TTL (reasoning + tiered pricing)
- Add context_management capability extraction
- Make auth optional for /v1/models per official docs
- Add reasoning and tiered pricing capture with proper units handling
- Update provider registry to use Responses API client as default
- Add comprehensive tests for all new functionality
@Patel230
Patel230 merged commit 011bdc0 into main Jul 29, 2026
16 checks passed
@Patel230
Patel230 deleted the feat/concentrate-ai-integration branch July 29, 2026 01:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant