chore(gen)!: render BYOK/TTS/STT as initialisms in generated symbols

[christineschen]

Summary

The OpenAPI tags are already BYOK / TTS / STT, but Speakeasy re-cases single all-caps tokens, so generated symbols came out as Byok, Tts, Stt. The fix is generator config, not a hand edit: customCasings declares terms whose PascalCase form must stay all-caps.

 typescript:
   version: 1.2.0
+  customCasings:
+    byok:
+      initialism: true
+    stt:
+      initialism: true
+    tts:
+      initialism: true

Regenerated with the pinned speakeasyVersion (1.787.0), which renames the sub-SDK classes (class Byok → class BYOK, Tts → TTS, Stt → STT, modules stay src/sdk/byok.ts etc.) and the ApiType enum keys.

Unchanged: accessors (openrouter.byok, .tts, .stt), camelCase properties (isByok, includeByokInLimit), and every wire value/JSON name — only pascal casing feeds generated symbol names.

Breaking for source consumers

ApiType is re-exported from @openrouter/sdk/models, and two of its keys change (the values don't):

 export const ApiType = {
-  Tts: "tts",
-  Stt: "stt",
+  TTS: "tts",
+  STT: "stt",
 } as const;

So ApiType.Tts / ApiType.Stt and direct imports of the Byok/Tts/Stt classes stop compiling; ApiType.TTS / ApiType.STT replace them. Worth calling out in release notes.

Also included

tests/e2e/embeddings.test.ts asserted that input: '' succeeds, but openrouter-web#30855 tightened the embeddings schema to z.string().min(1), so the live API now returns 400 and the validate job failed on every typescript-sdk PR (including Speakeasy's own regen branches). The test now asserts the current contract:

it('should reject an empty string input', async () => {
  await expect(client.embeddings.generate({ requestBody: { input: '', model: 'openai/text-embedding-3-small' } }))
    .rejects.toThrow(BadRequestResponseError);
});

This supersedes #723.

Scope note: Api → API was deliberately left alone (APIKeys already renders correctly since the tag is API Keys; renaming ApiType and friends would be a much wider change). Matching python-sdk PR (merged): OpenRouterTeam/python-sdk#561 · go-sdk (merged): OpenRouterTeam/go-sdk#480

Version is hand-set to 1.2.0 in gen.yaml (Speakeasy honours a custom version: versioning: custom SDK version detected), since the generator would otherwise have shipped this source break as a patch. Local pnpm run typecheck, eslint, and the unit suite pass.

BREAKING CHANGE: ApiType.Tts and ApiType.Stt are renamed to ApiType.TTS and ApiType.STT (enum values "tts"/"stt" unchanged), and the deep-importable sub-SDK classes Byok/Tts/Stt are renamed to BYOK/TTS/STT. Runtime behaviour, JSON field names, and the openrouter.byok/.tts/.stt accessors are unchanged.

Link to Devin session: https://openrouter.devinenterprise.com/sessions/236b5466ec42476c8645101ef5bcd17f
Requested by: @christineschen

[devin-ai-integration]

Original prompt from christine.chen

SYSTEM:
=== BEGIN THREAD HISTORY ===
<most_recent_message>
Christine Chen (U0B8QM7RKLL): create a pr to fix this

[Slack unfurl — this is an automatic link preview, not a user message]
Quote of conversation (https://openrouter.slack.com/archives/C0BCDN7RHJM/p1785278350731749?thread_ts=1785278350.731749&amp;cid=C0BCDN7RHJM):
> From David Bai
> <@U0B8QM7RKLL> non urgent nit but would it be a problem to update our client sdks to use initialism for BYOK, TTS, STT etc? At first I thought it was just a docs change but looks like need to update speakeasy configs and not sure if theres any implications there
> Posted on July 28, 2026 at 10:39 PM

</most_recent_message>
=== END THREAD HISTORY ===

Thread URL: https://openrouter.slack.com/archives/D0B9SPV4LV9/p1785338154566759?thread_ts=1785338154.566759&amp;cid=D0B9SPV4LV9

The latest message is the one right above that tagged you. The <most_recent_message> is the message that you should use to guide your goals + task for this session, and you should use the rest of the slack thread as context.

[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

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
openrouter-production	🟡 Building	–	Jul 29, 2026, 3:22 PM

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
openrouter-staging	🟡 Building	–	Jul 29, 2026, 3:22 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[perry-the-pr-reviewer]

Perry's Review

Verdict: 💬 Comments / questions

Risk: 🟡 Medium

Details

Summary

This PR adds customCasings to the Speakeasy generator config (gen.yaml) to render BYOK/TTS/STT as initialisms in generated TypeScript symbols. The regenerated code is clean and consistent — all class names (Byok→BYOK, Tts→TTS, Stt→STT), imports, type annotations, and enum keys are updated with zero dangling references to the old names. Public accessor properties (openrouter.byok, .tts, .stt) and enum string values ("tts", "stt") are correctly preserved.

Breaking change: ApiType enum keys (see inline)

ApiType.Tts → ApiType.TTS and ApiType.Stt → ApiType.STT is a source-level breaking change. ApiType is publicly exported through the SDK's models entry point. The PR body says "one enum member key" changed — it's actually two.

CI failure (pre-existing, unrelated to this PR)

The validate check fails on the e2e embeddings test — the "should handle empty string input gracefully" test sends input: '' to the live OpenRouter embeddings API, which now rejects it with a Zod validation error ("Too small: expected string to have >=1 characters"). This test is not modified by this PR and the failure is entirely unrelated to the BYOK/TTS/STT rename. It should be fixed separately (update the test to expect the 400 error, or skip it).

Stale PR body

The PR body states the version bump as "1.1.19 → 1.1.20", but the actual diff shows "1.1.21 → 1.1.22" — the PR was rebased/merged with main multiple times, picking up intermediate SDK regenerations. Consider updating the body to match the current state.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
openrouter-production	🟡 Building	–	Jul 30, 2026, 3:07 PM

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
openrouter-staging	🟡 Building	–	Jul 30, 2026, 3:07 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[kimblekabrain607-wq]

Kimblekabrain607@gmail.com