chore: 🐝 Update SDK - Generate 0.13.13

[github-actions]

SDK update

Versioning

Version Bump Type: [patch] - 🤖 (automated)

Tip

If updates to your OpenAPI document introduce breaking changes, be sure to update the info.version field to trigger the correct version bump.
Speakeasy supports manual control of SDK versioning through multiple methods.

Typescript SDK Changes:

• openrouter.benchmarks.getBenchmarks(): Added
• openrouter.datasets.getBenchmarksArtificialAnalysis(): Removed (Breaking ⚠️)
• openrouter.datasets.getBenchmarksDesignArena(): Removed (Breaking ⚠️)
• openrouter.chat.send(): response Changed
• openrouter.embeddings.listModels(): response.data[].reasoning Added
• openrouter.models.get(): response.data.reasoning Added
• openrouter.models.list(): response.data[].reasoning Added
• openrouter.models.listForUser(): response.data[].reasoning Added

View full SDK changelog

OpenAPI Change Summary

├─┬Paths
│ ├──[-] path (24149:3)❌ 
│ ├──[-] path (24061:3)❌ 
│ ├──[+] path (22975:3)
│ └─┬/models
│   └─┬GET
│     └─┬Responses
│       └─┬200
│         └─┬application/json
│           └──[🔀] example (28631:17)
├─┬Tags
│ └──[+] Benchmarks (32605:5)
└─┬Components
  ├──[-] schemas (3721:7)❌ 
  ├──[-] schemas (3793:7)❌ 
  ├──[-] schemas (3674:7)❌ 
  ├──[-] schemas (3883:7)❌ 
  ├──[-] schemas (3655:7)❌ 
  ├──[-] schemas (3956:7)❌ 
  ├──[-] schemas (3764:7)❌ 
  ├──[+] schemas (20303:7)
  ├──[+] schemas (12080:7)
  ├──[+] schemas (20354:7)
  ├──[+] schemas (20134:7)
  ├──[+] schemas (20207:7)
  ├──[+] schemas (20153:7)
  ├─┬ChatUsage
  │ ├──[🔀] example (5392:9)
  │ ├──[+] properties (5463:9)
  │ └─┬total_tokens
  │   ├──[🔀] type (5481:17)❌ 
  │   ├──[🔀] description (5464:24)
  │   ├──[+] nullable (5465:21)❌ 
  │   ├──[+] properties (5467:13)
  │   ├──[+] properties (5471:13)
  │   └──[+] properties (5476:13)
  └─┬Model
    ├──[🔀] example (11817:9)
    ├──[+] properties (11913:9)
    ├─┬supported_parameters
    │ └──[🔀] $ref (12080:20)❌ 
    ├─┬top_provider
    │ └──[🔀] $ref (11921:11)❌ 
    └─┬supported_voices
      ├──[🔀] description (11916:24)
      ├──[-] nullable (12235:21)❌ 
      ├──[-] example (12232:20)
      └─┬Schema
        └──[🔀] $ref (16415:9)❌ 

Document Element	Total Changes	Breaking Changes
paths	4	2
tags	1	0
components	29	13

View full report

Linting Report

0 errors, 1 warnings, 0 hints

View full report

TYPESCRIPT CHANGELOG

No relevant generator changes

Based on Speakeasy CLI 1.763.2

Last updated by Speakeasy workflow

[perry-the-pr-reviewer]

Perry's Review

Incremental re-review of the Speakeasy 0.13.13 regen. Since my last review the SDK source tree is byte-identical — the only changes are the version stamp, a no-op reordering of the package.json scripts block, a RELEASES.md append, and regenerated lockfiles.

Verdict: 💬 Comments / questions

Details

Scope: incremental — source unchanged since prior review at 62ae18f; deltas this push are version bump 0.13.12 → 0.13.13, a semantically-identical package.json scripts reorder, RELEASES.md append, and lockfile regen (validated by sorting the scripts map: identical key/value pairs).

Risk: 🟡 Medium

CI: all passing ✅ (validate)

Findings: none new. The unified benchmark surface (legacy datasets Artificial-Analysis / Design-Arena methods removed, replaced by a single benchmarks.getBenchmarks with a required source discriminator) is byte-identical to what I reviewed last round and remains internally consistent — no dangling references to the removed symbols, new SDK class wired into the root client, version consistent across package.json / jsr.json / config SDK_METADATA.

Standing heads-up (unchanged, not a blocker): this regen still removes two public SDK methods under a patch-level version bump. For a pre-1.0 SemVer this is permitted, and Speakeasy derives the bump from the spec info.version rather than by analyzing removed operations — so the bump is expected behavior, not a generator bug. The only real consumer risk is that a caret npm range (^0.13.12) auto-upgrades into the removal; callers pinning an exact version are unaffected.

Codex (HEAVY_SECONDARY_MODEL): 3 findings surfaced, all on code unchanged since the prior review — (1) the breaking patch-bump removal noted above, (2) the source/display_name field rename in the unified shape, and (3) the model docs page linking to an un-generated reasoning doc (a pre-existing repo-wide quirk: the docs directory is gitignored and only partially force-committed, not introduced by this regen). No net-new action.

Research: Speakeasy versioning derives the release number from spec info.version + config checksums; pre-1.0 SemVer §4 permits breaking changes in any release. No change to that analysis since the prior review.

Security: no concerns — generated client SDK; no credential handling, auth, or streaming-path changes in the delta.

Test coverage: generated SDK; CI validate job green.

Unresolved threads: none.

Scope: incremental — 0 source lines changed since prior review
Review: tier=large · model=claude-opus-latest · score=30.7