Repository navigation
docs: numberToDigitsCutoff defaults to 2100, not 2025 - #1328
Merged
stephenvapiai merged 2 commits intoOct 14, 2026
Merged
stephenvapiai merged 2 commits into
stephenvapiai merged 2 commits into
Conversation
An unset chunkPlan.formatPlan.numberToDigitsCutoff is filled with 2100 at runtime; the API schema declares no default.
chiranjeet-vapi
force-pushed
the
docs/number-to-digits-cutoff-default
branch
from
October 14, 2026 04:10
7d75366 to
b33722c
Compare
chiranjeet-vapi
marked this pull request as ready for review
October 14, 2026 16:42
Lightsage docs evalsWaiting for the staging docs URL before running evals. Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
stephenvapiai
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
voice-formatting-plan.mdxandemail-address-reading.mdxgive thechunkPlan.formatPlan.numberToDigitsCutoffdefault as2025. An unset cutoff is filled with2100at runtime. Both pages now say2100, and the example uses a12345/1200pair.Evidence
https://api.vapi.ai/api-json, 2026-10-14):FormatPlan.numberToDigitsCutoffdeclares no default (example: 2025only), so the spec does not support 2025 as a default either.2100runtime default: verified against the current API implementation.Reviewer note: please confirm with the voice pipeline owner before merging.
Testing Steps
fern check(pinned 5.151.1) passes locally