fix(nebius): refresh Token Factory integration - #5770
Draft
demianarc wants to merge 1 commit into
Draft
Conversation
|
@demianarc is attempting to deploy a commit to the Helicone Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket
N/A — this refreshes the existing Nebius Token Factory integration; it does not add a new provider.
Component/Service
Type of Change
Deployment Notes
Screenshots / Demos
Not applicable (docs and provider behavior only).
Extra Notes
llama-3.3-70b-instruct:nebiusmodel ID and $0.13/$0.40 per-million-token pricing were re-verified against the public Token Factory catalog on 2026-08-13, so this PR adds regression coverage instead of changing correct registry data.Context
The existing integration page used retired model examples, omitted the required
Helicone-Authheader from both runnable requests, and did not distinguish the transparent legacy proxy from the chat-only AI Gateway provider mapping. The Nebius provider also ignored standard OpenAI-compatible{ "error": { "message": ... } }error bodies.This change:
meta-llama/Llama-3.3-70B-Instructmodel;detailerrors and OpenAI-compatible nested errors;Tests
yarn jest --config packages/jest.config.ts --runInBand packages/__tests__/cost/providers/nebius.test.ts(5 passed)yarn workspace helicone-worker test:run --config test/gateway/vitest.config.mts test/gateway/nebius-routes.spec.ts(3 passed)yarn workspace helicone-worker lint(passed; existing warnings only)yarn prettier --check docs/getting-started/integration-method/nebius.mdx packages/cost/models/providers/nebius.ts packages/__tests__/cost/providers/nebius.test.ts worker/test/gateway/nebius-routes.spec.ts worker/test/gateway/vitest.config.mts worker/vitest.config.mts