Keyword boosting lets you bias the Pulse speech-to-text model toward specific words or phrases — useful for proper nouns, brand names, technical terms, or domain-specific vocabulary that the model might otherwise misrecognize.
Keywords are passed as a single comma-separated string in the keywords query parameter. Each entry follows the format:
The value is a plain string, not a JSON array. Both of these shapes are wrong and produce garbled transcripts (the API parses the brackets and quotes as keyword characters):
Pass it as one string instead:
In JavaScript: url.searchParams.append("keywords", "I:20,smiling:26") — URLSearchParams URL-encodes the colons and comma for you. In Python: params = {"keywords": "I:20,smiling:26"} then urlencode(params) does the same. Verified against the live API.
Higher values create a stronger bias toward that word in the output. Start low and increase if the word still isn’t recognized correctly.
Add the keywords query parameter to your WebSocket connection URL with a comma-separated list of keywords and optional intensifiers.
Jensen with no intensifier defaults to 1.0.
Very high intensifiers (above 10) heavily bias the transcript and can hallucinate the keyword even when it was not spoken. The example I:20,smiling:26 demonstrates the format, not recommended values. Start at 3-6 and tune from there.
Start with lower intensifier values (1–3) and increase gradually. Very high values (7–10) can over-bias the model and should be used sparingly.