Repository navigation
fix(bazaarlink): register in APIKEY_PROVIDERS to allow connection creation - #4497
adivekar-utexas wants to merge 1 commit into
Conversation
…ation BazaarLink was defined in the PROVIDERS display constant (UI listing) and in the execution registry (open-sse config), but absent from APIKEY_PROVIDERS in src/shared/constants/providers.ts. This meant the provider appeared as selectable in the UI but connection creation was rejected because isManagedProviderConnectionId() — which checks the static catalog resolved from APIKEY_PROVIDERS — returned false. Add a bazaarlink entry to APIKEY_PROVIDERS with alias `bzl`, API-key auth hints, and free-tier annotation consistent with its existing registry definition. Bulk-add supports are inherited via the default path (not in BULK_API_KEY_EXCLUDED). Co-authored-by: Cursor <cursoragent@cursor.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new bazaarlink provider configuration to the APIKEY_PROVIDERS constant in src/shared/constants/providers.ts. However, the reviewer noted that bazaarlink is already defined earlier in the file. Adding it again creates a duplicate key, which can trigger ESLint errors and cause the first definition to be silently overwritten. The reviewer suggests updating the existing definition with the new properties instead of adding a duplicate block.
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.
| bazaarlink: { | ||
| id: "bazaarlink", | ||
| alias: "bzl", | ||
| name: "BazaarLink", | ||
| icon: "storefront", | ||
| color: "#6366F1", | ||
| textIcon: "BZ", | ||
| website: "https://bazaarlink.ai", | ||
| hasFree: true, | ||
| freeNote: "Free tier with auto:free routing — zero-cost inference, no credit card required. 4M tokens/day per account for most models.", | ||
| authHint: | ||
| "Use your BazaarLink API key (starts with sk-bl-) in Authorization: Bearer <key>. Fully OpenAI-compatible — OpenAI SDK works with base URL https://bazaarlink.ai/api/v1.", | ||
| apiHint: | ||
| "Get a free API key at https://bazaarlink.ai — supports auto:free for zero-cost routing. Models use provider/model format e.g. xiaomi/mimo-v2.5-pro.", | ||
| }, |
There was a problem hiding this comment.
The bazaarlink provider is already defined in APIKEY_PROVIDERS at line 993. Adding it again here introduces a duplicate key in the APIKEY_PROVIDERS object, which can trigger ESLint errors (such as no-dupe-keys) and results in the first definition being silently overwritten.
Instead of adding a duplicate entry, you should update the existing bazaarlink definition at line 993 with the new properties (freeNote, authHint, apiHint). Please remove this duplicate block and update the definition at line 993 directly.
|
Superseded by #___ (new branch with correct fix, no duplicate key) |
) Adds authHint + enriched freeNote/apiHint on the existing bazaarlink entry (distinct from the closed-redundant #4497). Integrity test included. Integrated into release/v3.8.33.
…eaper-inference#4522) Adds authHint + enriched freeNote/apiHint on the existing bazaarlink entry (distinct from the closed-redundant cheaper-inference#4497). Integrity test included. Integrated into release/v3.8.33.
Summary
BazaarLink was registered in the execution registry and the PROVIDERS display constant, but was missing from APIKEY_PROVIDERS. This caused isManagedProviderConnectionId to return false, blocking connection creation with an "Invalid provider" error.
Fix
Added a bazaarlink entry to APIKEY_PROVIDERS with:
Bulk-add works automatically (not in BULK_API_KEY_EXCLUDED).
Test plan
Made with Cursor