[artickc]

Problem

The Limits page shows nothing for Vertex AI. Unlike Kiro/Antigravity/etc., Vertex exposes no usage or quota API for an API key or Service Account — credit/billing balance lives behind the Google Cloud Billing API, which the proxy credential can't reach. So a Vertex connection had no entry to display.

What this adds

A self-tracked "$X used since this account was added" figure for Vertex — the USD that OmniRoute itself has spent through the connection, summed from usage_history and priced with the backend pricing table.

• getConnectionSpendUsdSinceAdded(provider, connectionId) (src/lib/usage/usageStats.ts): sums per-model tokens (input/output/cache/reasoning) from usage_history for the connection across all time — rows only exist from first use onward, i.e. "since the account was added" — and prices each model via calculateCost. Returns { costUsd, requests }. Only reflects traffic routed through OmniRoute (not the provider's own dashboard).
• getVertexUsage(connectionId, provider) (open-sse/services/usage.ts): returns { plan: "Vertex AI", message: "$X.XX used since this account was added · N requests", quotas: { spend } }. The spend quota carries quotaSource: "localUsageHistory" and is included so the provider-limits cache persists the entry (a message-only result is treated as a transient error and not cached).
• Registered Vertex (vertex, vertex-partner) in USAGE_FETCHER_PROVIDERS, USAGE_SUPPORTED_PROVIDERS, and PROVIDER_LIMITS_APIKEY_PROVIDERS so the limits sync picks up the (API-key) connections.

This is "used" only — no quota cap and no remaining/free-credit figure (those aren't retrievable for Vertex without the Cloud Billing API). The pattern mirrors the existing xiaomi-mimo self-tracked usage handler.

Tests

tests/unit/vertex-spend-usage.test.ts (5 tests, all pass) with a real temp DB:

• counts only the target connection's requests; no bleed from other connections;
• getVertexUsage returns a spend quota (localUsageHistory) + a $/request-count message for a used connection;
• clean no-usage message when nothing was routed;
• message-only (no quota) when the connection id is missing.

node --import tsx --test tests/unit/vertex-spend-usage.test.ts
# pass 5, fail 0

Existing usage tests (usage-service-hardening, kiro) remain green (31 pass).

[gemini-code-assist]

Code Review

This pull request adds self-tracked spend tracking for Vertex AI and Vertex Partner providers, as they lack a native usage API. It calculates USD spend by querying local usage history and pricing the tokens. Feedback on the implementation suggests refining the database query in getConnectionSpendUsdSinceAdded to filter by both provider and success = 1 to prevent potential cross-provider collisions and avoid counting failed requests.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The current implementation of getConnectionSpendUsdSinceAdded queries usage_history filtering only by connection_id. To prevent potential cross-provider collisions or incorrect calculations, it should also filter by the provider parameter. Additionally, it should filter by success = 1 to ensure only successful requests are counted towards the spend total.

  const rows = db
    .prepare(
      "SELECT model, COALESCE(SUM(tokens_input), 0) AS input, COALESCE(SUM(tokens_output), 0) AS output, COALESCE(SUM(tokens_cache_read), 0) AS cacheRead, COALESCE(SUM(tokens_cache_creation), 0) AS cacheCreation, COALESCE(SUM(tokens_reasoning), 0) AS reasoning, COUNT(*) AS requests FROM usage_history WHERE provider = ? AND connection_id = ? AND success = 1 GROUP BY model"
    )
    .all(provider, connectionId) as Array<{

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (5 files)

• open-sse/services/usage.ts — getVertexUsage added with self-tracked spend; correctly omits unused accessToken/apiKey params
• src/lib/usage/usageStats.ts — getConnectionSpendUsdSinceAdded correctly filters by provider and success = 1 (regression from the earlier version without these filters is avoided)
• src/lib/usage/providerLimits.ts — additions in APIKEY providers set
• src/shared/constants/providers.ts — additions in USAGE_SUPPORTED_PROVIDERS
• tests/unit/vertex-spend-usage.test.ts — covers cross-provider bleed, failed-request exclusion, empty connection, and missing connection id

Fix these issues in Kilo Cloud

---

_{Reviewed by step-3.7-flash-20260528 · 482,346 tokens}

[diegosouzapw]

Thanks @artickc — the trilogy is complete: #3690 (auth) → #3712 (dynamic catalog) → now real spend visibility on the Limits page. 📊 Self-tracking via usage_history × the pricing table is the right call given Vertex exposes no usage API to the credential, and labeling it quotaSource: "localUsageHistory" keeps it honest. The temp-DB test suite (scoping out failed/cross-provider/cross-connection rows) is exactly the regression guard this needed. Validated on top of release/v3.8.23: 5/5 tests + clean typecheck. Merging — ships in v3.8.23. 🚀