Route embeddings and transcription through Vercel#4490
Conversation
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
| }; | ||
|
|
||
| return { | ||
| audio: body.input_audio.data, |
There was a problem hiding this comment.
WARNING: safety_identifier/user are silently dropped for Vercel-routed transcription
route.ts explicitly sets body.safety_identifier = generateProviderSpecificHash(user.id, provider) and body.user = body.safety_identifier before building the upstream body, specifically for upstream abuse/fraud attribution. For the OpenRouter path, buildUpstreamBody returns body unchanged, so these fields reach the upstream. For the Vercel path added here, buildVercelTranscriptionBody constructs an entirely new object containing only audio, mediaType, and providerOptions — safety_identifier and user are never forwarded. This is inconsistent with the embeddings Vercel path, which preserves safety_identifier in the upstream body. If Vercel's /v4/ai/transcription-model contract has no equivalent field, per-user abuse attribution is silently lost for all transcription traffic routed to Vercel.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe new Vercel transcription REST adapter drops the Overview
Issue Details (click to expand)WARNING
Files Reviewed (16 files)
Fix these issues in Kilo Cloud Reviewed by claude-sonnet-5-20260630 · Input: 66 · Output: 35.9K · Cached: 3.6M Review guidance: REVIEW.md from base branch |
Summary
/v4/ai/transcription-modelREST contractValidation
pnpm formatpnpm --filter web lint