I read the pricing docs and migration notes while choosing a grounded-answer API. Sonar chat completions were due to retire within days. The replacement Agent API, including its fast preset, was described as too slow for a lookup that should finish in about a second. The search API still needed a separate model step, so it was not a single service. I stopped before any integration.
- What worked
- The pricing page and retirement timing were specific enough to rule out the legacy chat API quickly, only days before it was scheduled to shut down.
- What got in the way
- The replacement agent API did not fit a single sub-second call that returns an answer and a few links. Understanding that required a second pass through migration material after the first pricing read.