希望能增加供应商包月以及供应商聚合设置

[srcheng17]

两个场景：

1. 供应商A 倍率高但是包月，供应商B 倍率低但是按量，最终会按照倍率低的走按量
2. 供应商C同时提供codex和claude code接口，设置供应商总消费上限时不能算在一起

[github-actions]

Thank you for this feature suggestion.

Feasibility assessment:

Based on my analysis of the codebase, I can address both scenarios:

Scenario 1: Provider flat-rate monthly (供应商包月)

Currently, the system tracks provider costs individually via Redis keys (provider:{id}:cost_monthly, etc.) and applies limits (limitMonthlyUsd). However, there is no concept of "flat-rate" billing that would:

• Allow marking a provider as flat-rate (no per-request cost tracking)
• Intelligently route between flat-rate (high multiplier) and pay-per-use (low multiplier) providers

Scenario 2: Provider aggregation for combined consumption limits (供应商聚合)

Currently, each provider tracks consumption independently. The providerVendors table groups providers by domain for management purposes, but does not aggregate consumption tracking. There is no mechanism to:

• Group multiple providers (e.g., codex + claude code endpoints from same vendor)
• Apply a single combined consumption limit across the group

Related existing code:

• src/drizzle/schema.ts (lines 159-345) - Provider table with limitMonthlyUsd, limitDailyUsd per-provider limits
• src/lib/rate-limit/service.ts (lines 652-834) - Per-provider cost tracking via Redis keys
• src/app/v1/_lib/proxy/provider-selector.ts (lines 1210-1227) - Provider selection sorts by costMultiplier but does not consider flat-rate vs pay-per-use
• src/drizzle/schema.ts (lines 142-157) - providerVendors table for domain-based grouping (not consumption aggregation)

Implementation considerations:

1. Flat-rate billing mode would require:

   • New field on providers table (e.g., billingMode: 'pay_per_use' | 'flat_rate')
   • Modified provider selector to prefer flat-rate providers when available
   • Cost tracking exemption for flat-rate providers

2. Provider aggregation would require:

   • New table for provider groups (or repurpose groupTag for consumption aggregation)
   • Modified rate-limit service to aggregate costs across group members
   • UI changes to configure grouped consumption limits

Dependencies:

• Rate limiting service (src/lib/rate-limit/service.ts)
• Provider selector (src/app/v1/_lib/proxy/provider-selector.ts)
• Provider repository and schema
• Dashboard UI for configuration

---

Automated response from Claude AI