9router/open-sse/services/usage/codebuddy-cn.js

147 lines
5.8 KiB
JavaScript
Raw Permalink Normal View History

feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
/**
* CodeBuddy CN usage handler
*
* Scoped to the "codebuddy-cn" provider specifically — a future "codebuddy-intl"
* variant would get its own handler/endpoint, so keep this CN-only.
*
* Quota lives behind a Tencent billing endpoint (POST, payload wrapped twice
* under data.Response.Data). It mixes two credit types that must NOT be merged:
*
* - Refill / base ("基础体验包"): a recurring allowance whose cycle resets long
* before the resource itself expires (CycleEndTime << DeductionEndTime). The
* live numbers live in the *Cycle* fields (e.g. CycleCapacityUsed 6.54 / 500)
* and resetAt is the next monthly refresh.
* - Bonus ("活动赠送包"): one-shot credits that run a single cycle and then
* expire for good (CycleEndTime == DeductionEndTime). Numbers live in the
* plain Capacity fields.
*
* We surface one quota row per package — a cadence label (Monthly/Weekly/Daily)
* for refill packs, "Bonus Pack N" for bonus packs (soonest-expiring first).
*/
import { proxyAwareFetch } from "../../utils/proxyFetch.js";
import { PROVIDERS } from "../../providers/index.js";
import { U, parseResetTime } from "./shared.js";
const PROVIDER_ID = "codebuddy-cn";
// Prefer the *Precise string fields (exact), fall back to the numeric ones.
function num(precise, plain) {
const n = Number(precise ?? plain);
return Number.isFinite(n) ? n : 0;
}
// Label a refill pack by its cycle length (Monthly is the common CodeBuddy case).
function refillCadence(acc) {
const start = parseResetTime(acc.CycleStartTime);
const end = parseResetTime(acc.CycleEndTime);
if (start && end) {
const days = (new Date(end).getTime() - new Date(start).getTime()) / 86400000;
if (days <= 1.5) return "Daily";
if (days <= 10) return "Weekly";
}
return "Monthly";
}
async function getCodeBuddyUsage(providerId, accessToken, apiKey, providerSpecificData, proxyOptions = null) {
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
const token = accessToken || apiKey;
if (!token) {
return { message: `CodeBuddy (${providerId}) credential not available.` };
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
}
try {
const response = await proxyAwareFetch(U(providerId).url, {
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
method: "POST",
headers: {
...(PROVIDERS[providerId]?.headers || {}),
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
Authorization: `Bearer ${token}`,
"Content-Type": "application/json",
Accept: "application/json",
},
body: "{}",
}, proxyOptions);
if (response.status === 401 || response.status === 403) {
return { message: "CodeBuddy CN credential invalid or expired." };
}
if (!response.ok) {
return { message: `CodeBuddy CN quota API error (${response.status}).` };
}
const json = await response.json();
if (json?.code !== 0) {
return { message: `CodeBuddy CN quota error: ${json?.msg || "unknown"}` };
}
const data = json?.data?.Response?.Data || {};
const accounts = Array.isArray(data.Accounts) ? data.Accounts : [];
if (accounts.length === 0) {
return { message: "CodeBuddy CN connected. No credit package found." };
}
const cycleEndMs = (acc) => {
const r = parseResetTime(acc.CycleEndTime);
return r ? new Date(r).getTime() : Number.POSITIVE_INFINITY;
};
// Refill packs roll into a new cycle before the resource expires; bonus packs
// end exactly at expiry. >2d gap between cycle end and validity end = refill.
const REFILL_GAP_MS = 2 * 24 * 60 * 60 * 1000;
const isRefill = (acc) => {
const ce = cycleEndMs(acc);
const de = Number(acc.DeductionEndTime);
return Number.isFinite(ce) && Number.isFinite(de) && de - ce > REFILL_GAP_MS;
};
const byExpiry = (a, b) => cycleEndMs(a) - cycleEndMs(b);
const refills = accounts.filter(isRefill).sort(byExpiry);
const bonuses = accounts.filter((a) => !isRefill(a)).sort(byExpiry);
const quotas = {};
// Refill packs first: cadence-labelled, using the *Cycle* balance and
// resetting at the next refresh.
const seenRefill = {};
refills.forEach((acc) => {
const base = refillCadence(acc);
seenRefill[base] = (seenRefill[base] || 0) + 1;
const name = seenRefill[base] > 1 ? `${base} ${seenRefill[base]}` : base;
quotas[name] = {
used: num(acc.CycleCapacityUsedPrecise, acc.CycleCapacityUsed),
total: num(acc.CycleCapacitySizePrecise, acc.CycleCapacitySize),
resetAt: parseResetTime(acc.CycleEndTime),
unlimited: false,
// Recurring allowance: the CycleEndTime is the next refresh, not the
// final expiry. The UI must show "Resets in", not "Expires in".
recurring: true,
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
};
});
// Bonus packs: use the lifetime Capacity balance; resetAt is the expiry.
// These are one-shot credits (CycleEndTime == DeductionEndTime), so they
// never replenish — mark recurring:false so the UI shows "Expires in"
// instead of implying a monthly refill.
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
bonuses.forEach((acc, i) => {
quotas[`Bonus Pack ${i + 1}`] = {
used: num(acc.CapacityUsedPrecise, acc.CapacityUsed),
total: num(acc.CapacitySizePrecise, acc.CapacitySize),
resetAt: parseResetTime(acc.CycleEndTime),
unlimited: false,
recurring: false,
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
};
});
const basePkg = refills[0] || accounts[0] || {};
const plan = basePkg.PackageName || basePkg.SubProductName || "CodeBuddy";
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
return { plan, quotas };
} catch (error) {
return { message: `CodeBuddy (${providerId}) error: ${error.message}` };
feat(codebuddy-cn): add API key auth + credit quota tracker Two additions on top of the merged CodeBuddy CN OAuth provider: 1. API key auth — connect with a direct API key (sent as Authorization: Bearer), not only via OAuth device-code flow. - registry: add authModes ["oauth","apikey"] + hasOAuth; combined Bearer auth already forwards the key, token-refresh skips key connections. - providers POST: accept dual-auth providers (authModes includes "apikey") that live under category "oauth" — previously rejected as "Invalid provider". Also fixes the same latent gap for xai. 2. Quota tracker — surface CodeBuddy CN credit balance on the usage dashboard for both OAuth and API-key connections. - registry: add transport.usage.url (Tencent billing endpoint) + features.usage/usageApikey so the connection is quota-eligible. - new CN-scoped handler services/usage/codebuddy-cn.js: POST the billing meter endpoint, unwrap data.Response.Data.Accounts[]. The payload mixes two credit types that must not be merged: * refill/base ("基础体验包") — recurring allowance; cycle resets well before the resource expires (CycleEndTime << DeductionEndTime). Reads the *Cycle* balance, resetAt = next refresh. Cadence-labelled. * bonus ("活动赠送包") — one-shot credits that expire at CycleEndTime. Reads the plain Capacity balance. Labelled "Bonus Pack N". One quota row per package, soonest-expiring first. - register handler under "codebuddy-cn" in USAGE_HANDLERS. Frontend needs no change — USAGE_SUPPORTED_PROVIDERS/USAGE_APIKEY_PROVIDERS and the generic parseQuotaData branch already cover this shape. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-21 05:11:20 -04:00
}
}
export async function getCodeBuddyCnUsage(accessToken, apiKey, providerSpecificData, proxyOptions = null) {
return getCodeBuddyUsage(PROVIDER_ID, accessToken, apiKey, providerSpecificData, proxyOptions);
}
export async function getCodeBuddyIntlUsage(accessToken, apiKey, providerSpecificData, proxyOptions = null) {
return getCodeBuddyUsage("codebuddy-intl", accessToken, apiKey, providerSpecificData, proxyOptions);
}