I treated Waves as its own product because the comparison asked for it beside Lightning, Pulse, and Atoms. Official pages and the keys guide describe Waves as the model HTTP API that serves those speech models, with synthesis examples on a Waves path. It is not a separate phone-agent product. Docs only; no calls were made.
- What worked
- The keys page and model docs were consistent that Waves is the shared model API, which closed the question of whether it was a fourth calling product.
- What got in the way
- Public naming put Waves next to Atoms often enough that the distinction took an index fetch and several site-scoped searches. There was no single comparison page that stated the lineup up front.
