<!-- library-gap-audit: portkey-ai-gateway-sdk -->
Summary
Portkey AI's official Node.js SDK (portkey-ai) is a drop-in, OpenAI-SDK-shaped client (portkey.chat.completions.create(...)) that routes generation calls through Portkey's gateway to 250+ LLMs, with its own prompt-management and completion-execution surface distinct from the underlying provider SDKs. This execution surface is not instrumented anywhere in this repository.
What's missing
new Portkey({...}) client construction and portkey.chat.completions.create(...) (and streaming variants) — the SDK's primary generation-execution API — has no auto-instrumentation config, wrapper, or e2e scenario in this repo.- None of
portkey-ai, Portkey, or PORTKEY_GATEWAY_URL appear anywhere in js/src/, js/src/auto-instrumentations/configs/all.ts, or any e2e/scenarios/* directory. (This is distinct from the already-instrumented openrouter/ai-sdk gateway-style configs, which target different packages.)
Weekly downloads
Weekly downloads: 140,424 (as of 2026-09-14; window 2026-09-05–2026-09-11; source https://api.npmjs.org/downloads/point/last-week/portkey-ai).
Braintrust docs status
unclear — Braintrust publishes a comparison article, "Braintrust vs Portkey" (https://www.braintrust.dev/articles/braintrust-vs-portkey), describing a pattern where Portkey stays in the request path for routing/guardrails while traces are sent to Braintrust "through its SDK or OpenTelemetry integration" — but this describes manual OTel/generic tracing, not a dedicated auto-instrumentation wrapper for the portkey-ai package. Portkey does not appear in Braintrust's main integrations catalog at https://www.braintrust.dev/docs/integrations (full grid enumerated in the companion E2B gap issue).
Upstream sources
Local repo files inspected
js/src/auto-instrumentations/configs/all.ts (full instrumentation registry — no Portkey entry)- Repo-wide case-insensitive search for
portkey across the working tree (no matches)
e2e/scenarios/ directory listing (no portkey-named scenario)
<!-- library-gap-audit: portkey-ai-gateway-sdk -->
Summary
Portkey AI's official Node.js SDK (
portkey-ai) is a drop-in, OpenAI-SDK-shaped client (portkey.chat.completions.create(...)) that routes generation calls through Portkey's gateway to 250+ LLMs, with its own prompt-management and completion-execution surface distinct from the underlying provider SDKs. This execution surface is not instrumented anywhere in this repository.What's missing
new Portkey({...})client construction andportkey.chat.completions.create(...)(and streaming variants) — the SDK's primary generation-execution API — has no auto-instrumentation config, wrapper, or e2e scenario in this repo.portkey-ai,Portkey, orPORTKEY_GATEWAY_URLappear anywhere injs/src/,js/src/auto-instrumentations/configs/all.ts, or anye2e/scenarios/*directory. (This is distinct from the already-instrumentedopenrouter/ai-sdkgateway-style configs, which target different packages.)Weekly downloads
Weekly downloads: 140,424 (as of 2026-09-14; window 2026-09-05–2026-09-11; source https://api.npmjs.org/downloads/point/last-week/portkey-ai).
Braintrust docs status
unclear— Braintrust publishes a comparison article, "Braintrust vs Portkey" (https://www.braintrust.dev/articles/braintrust-vs-portkey), describing a pattern where Portkey stays in the request path for routing/guardrails while traces are sent to Braintrust "through its SDK or OpenTelemetry integration" — but this describes manual OTel/generic tracing, not a dedicated auto-instrumentation wrapper for theportkey-aipackage. Portkey does not appear in Braintrust's main integrations catalog at https://www.braintrust.dev/docs/integrations (full grid enumerated in the companion E2B gap issue).Upstream sources
Local repo files inspected
js/src/auto-instrumentations/configs/all.ts(full instrumentation registry — no Portkey entry)portkeyacross the working tree (no matches)e2e/scenarios/directory listing (noportkey-named scenario)