Skip to content

docs: reconcile cookbook agent files + recipes with the v4 SDK [DRG-490] - #10

Merged
luke-speechify merged 4 commits into
Speechify-AI:mainfrom
luke-speechify:lukeoliff/drg-490-cookbook-fix-stale-v3-sdk-label-in-agentsspeechify-ttsmd
Sep 9, 2026
Merged

luke-speechify merged 4 commits into
Speechify-AI:mainfrom
luke-speechify:lukeoliff/drg-490-cookbook-fix-stale-v3-sdk-label-in-agentsspeechify-ttsmd

Conversation

@luke-speechify

@luke-speechify luke-speechify commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

What

Adversarial review of the cookbook's agents/*.md (and adjacent docs) against the actual v4 SDK type definitions — npm @speechify/api 4.0.1, pypi speechify-api 4.0.0 — plus the server's char-limit constants. Fixes every claim that contradicted reality. Docs-only; no recipe code changed.

Stale version labels / references

  • agents/speechify-tts.md — snippets labelled @speechify/api v3 / speechify-api v3v4
  • agents/monorepo.md — products table said "TypeScript + Python on v2 SDKs" → v4

Wrong SDK field/param casing (v3-era camelCase the v4 migration missed)

  • recipes/audio/typescript/sdk/quickstart/README.md — described params as voiceId, audioFormatvoice_id, audio_format
  • recipes/audio/typescript/sdk/speech-marks/src/index.ts — comment speechMarks.chunksspeech_marks.chunks

Correctness

  • agents/speechify-tts.mdinput was documented as "~20,000 characters per request", but audio.speech caps at 2,000; 20,000 is the stream limit. Split per endpoint and linked api-limits.

Dead references

  • agents/maintenance.md + CONTRIBUTING.md — dropped references to agents/voice-agents.md, which does not exist.

Verified correct (no change)

Method names (audio.speech/stream/streamWithTimestamps, voices.list/create/get/delete/downloadSample), snake_case fields in both SDKs, AsyncSpeechify export, package/import names, base URL https://api.speechify.ai, model defaults, and the const voiceId locals (JS variable names, correctly passing voice_id:). Generated docs examples (Fern / docs.speechify.ai) carry no version pin or v3.

Follow-up to DRG-475. Linear: DRG-490

The agents TTS reference labelled its TypeScript and Python snippets
@speechify/api v3 / speechify-api v3, but the repo is already on v4
(catalog pins @speechify/api 4.0.1; Python recipes pin speechify-api>=4.0.0).
The snippet code already uses the v4 snake_case surface, so this is a
label-only fix. Keeps the ask-speechify knowledge engine from surfacing
v3 as the current SDK.
…DRG-490]

The v3->v4 SDK migration flipped request/response fields to snake_case,
but two references were missed:
- quickstart README described the call params as voiceId/audioFormat
- speech-marks comment referenced speechMarks.chunks

The recipe code was already correct (voice_id, audio_format,
response.speech_marks); only the prose/comment lagged.
@luke-speechify luke-speechify changed the title docs(agents): correct SDK label to v4 in speechify-tts.md [DRG-490] docs: clean up stale v3-era SDK references in cookbook [DRG-490] Sep 9, 2026
Adversarial review of agents/*.md against the v4 SDK type defs:
- speechify-tts.md: input char limit was stated as ~20,000 for all
  requests, but audio.speech caps at 2,000; 20,000 is the stream limit.
  Split the limit per endpoint and link api-limits.
- monorepo.md: products table said 'v2 SDKs'; the repo is on v4.
- maintenance.md + CONTRIBUTING.md: dropped dangling references to
  agents/voice-agents.md, which does not exist.
@luke-speechify luke-speechify changed the title docs: clean up stale v3-era SDK references in cookbook [DRG-490] docs: reconcile cookbook agent files + recipes with the v4 SDK [DRG-490] Sep 9, 2026
@luke-speechify
luke-speechify marked this pull request as ready for review September 9, 2026 22:00
@luke-speechify
luke-speechify merged commit 1b9dbde into Speechify-AI:main Sep 9, 2026
28 checks passed
@luke-speechify
luke-speechify deleted the lukeoliff/drg-490-cookbook-fix-stale-v3-sdk-label-in-agentsspeechify-ttsmd branch September 9, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant