docs(openrouter-stt): sync with openrouter-web changes

[devin-ai-integration]

Summary

openrouter-web #27332 added a capability-gated verbose_json response_format (plus timestamp_granularities) to POST /api/v1/audio/transcriptions. The skill didn't mention either field.

• Added response_format and timestamp_granularities rows to the Parameters table
• New "Timestamps with verbose_json" section: example request, the extra response fields (task, language, duration, segments, words), segment/word field shapes, and the provider gating (OpenAI-compatible providers only; gpt-4o transcribe models rejected)

Note: overlaps with open PR #72 (multipart docs) on the same file — may need a rebase depending on merge order.

Link to Devin session: https://openrouter.devinenterprise.com/sessions/a07b68fd118d4ef09bc088001c9bbde3

[devin-ai-integration]

Original prompt from Automation

You are the public skills sync pipeline. Your job is to scan PRs merged to main on OpenRouterTeam/openrouter-web in the last 24 hours, determine if any changes warrant updating the public agent skills in OpenRouterTeam/skills, and open PRs to the skills repo when updates are needed.

#``# Step 1: Identify relevant merged PRs

Clone both repos:

cd /home/ubuntu/repos/openrouter-web
git fetch origin main
git log --since='24 hours ago' --merges --first-parent origin/main --pretty=format:'%H|%s' --name-only

For each merged PR, collect the list of changed files. Only PRs that touch the paths in the mapping below are relevant. Skip bot commits (devin-ai-integration[bot], Devin AI, GitHub Actions Bot, openrouter[bot], opencode-agent[bot], OpenRouter SDK Bot, Claude, detail-app[bot], forge-the-devex-intern[bot], dependabot[bot]).

If no relevant PRs were merged, post a short message to the #devrel Slack channel (C08LQFVSC7Q) saying no skill-relevant changes were detected today, and exit.

#``# Step 2: Map changed files to affected skills

Use this mapping to determine which public skills are potentially affected:

openrouter-web paths	Affected skill(s) in OpenRouterTeam/skills
sdks/typescript/, packages/llm-interfaces/	openrouter-typescript-sdk, openrouter-agent-migration
services/cfw-*/src/routes/*analytics*, analytics query/response schemas	openrouter-analytics, openrouter-analytics-query, openrouter-analytics-schema
Generation routes, /api/v1/generation	openrouter-generations
Image generation adapters, packages/image-generation/	openrouter-images
supabase/seeds/, model schemas, /api/v1/models route	openrouter-models
OAuth/auth routes, PKCE flow code	openrouter-oauth
STT adapters, services/cfw-stt-api/, /api/v1/audio/transcriptions	openrouter-stt
TTS routes, /api/v1/audio/speech	openrouter-tts
Video adapters, /api/v1/videos	openrouter-video
``@`openr... (3383 chars truncated...)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[perry-the-pr-maintainer]

Perry's Review

Documents the response_format=verbose_json and timestamp_granularities params for STT transcription, added in openrouter-web #27332.

Verdict: ✅ LGTM

Details

Risk: 🟢 Low

CI: no other checks configured on this repo — only perry/review runs

Findings: none — verified every documented claim against the openrouter-web source (STT request/response schemas, STT provider adapters, and the transcribe route): the json/verbose_json enum, timestamp_granularities shape, response field additions (task, language, duration, segments, words), segment/word field shapes, and the OpenAI/Groq/Together-only provider gating (incl. the gpt-4o transcribe carve-out) all match the implementation exactly.

Research: cross-checked against the local openrouter-web checkout (source of truth for this documented behavior) rather than an external spec, since this documents an internal API extension, not a public standard.

Security: no concerns — docs-only change, no code touched, no secrets in the diff

Test coverage: n/a — documentation change

Unresolved threads: none

---

Scope: first review (full)
Review: tier=trivial · model=claude-sonnet-latest · score=0.2