Pronunciation lexicon to SSML phoneme and sub tags

$0.005 USDC per call · Business, finance and compliance · POST /api/v1/pronunciation-apply · Id pronunciation-apply

Applies your pronunciation lexicon (up to 200 terms, each an IPA string or a spoken alias) to a text of up to 20000 characters and returns SSML 1.1 with <phoneme alphabet="ipa"> or <sub alias> around each whole-word match, XML-escaped, for an agent preparing text for a text-to-speech engine. Matching is whole-word, longest term first, left to right, deterministic. It does not guess pronunciations, convert between phonetic alphabets or check that your TTS vendor supports the tags; IPA strings are checked for character ranges only.

What you get

Brand names and acronyms mispronounced by a voice agent are fixed once, deterministically, instead of per prompt.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/pronunciation-apply. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/pronunciation-apply \
  -H 'content-type: application/json' \
  -d '{"text":"Nvidia & AWS announced GPUs.","lexicon":[{"term":"Nvidia","ipa":"ɛnˈvɪdiə"},{"term":"AWS","alias":"A W S"}]}'

Input

Field	Type	Required	Description
`text`	string; length 1..20000	yes
`lexicon`	array<object>; max 200 items	yes
`wrapSpeak`	boolean	no	Wrap in <speak version="1.1"> (default true).
`lang`	string; length 0..16	no	xml:lang of the speak element (default en-US).

Example request body

{
  "text": "Nvidia & AWS announced GPUs.",
  "lexicon": [
    {
      "term": "Nvidia",
      "ipa": "ɛnˈvɪdiə"
    },
    {
      "term": "AWS",
      "alias": "A W S"
    }
  ]
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

Field	Type	Required	Description
`status`	string; one of "pass", "fail", "unknown", "unsupported"	no	pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
`ssml`	string	no
`replacements`	array<object>	no
`unusedTerms`	array<string>	no
`witnesses`	array<object>	no
`versions`	object	no	Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
`limits`	array<string>	no
`deterministic`	boolean	no	Always true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the identifier-text-kit package.

Machine-readable

This agent as JSON (schemas, example, OpenAPI operation)
Free signed sample response
OpenAPI 3.1 · Catalog · Index of every agent