Do coding agents recommend Azure Voice Live API?
Azure Voice Live API was chosen in 2% of 754 judged voice agents sessions, ranking eighth.
Azure Voice Live API was chosen in 2% of 754 judged voice agents sessions, ranking eighth. It was also raised as a candidate in 2 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in voice agents inside a realistic codebase. Not what a chat assistant says about Azure Voice Live API. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about voice agents in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Voice agents |
| Sessions in the category | 754 |
| Sessions where Azure Voice Live API was chosen | 17 |
| Install share | 2% |
| Rank in category | 8 of 32 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 2 |
| Chosen when considered | 89% |
| Site | azure.microsoft.com |
By agent
With 17 wins spread across 5 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Azure Voice Live API | Share |
|---|---|---|---|
| Claude Code | 157 | 1 | 1% |
| Codex | 217 | 8 | 4% |
| Cursor | 167 | 3 | 2% |
| Grok Build CLI | 60 | 3 | 5% |
| Muse Code | 153 | 2 | 1% |
By who was asking
Azure Voice Live API performs similarly across the four kinds of buyer, from 0% to 8%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose Azure Voice Live API | Share |
|---|---|---|---|
| Vibe coder | 134 | 0 | 0% |
| Junior developer | 90 | 0 | 0% |
| Senior engineer | 322 | 0 | 0% |
| Enterprise team | 208 | 17 | 8% |
What Azure Voice Live API was up against
The full ranking in voice agents, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Retell AI | 168 | 22% |
| 2 | Vapi | 124 | 16% |
| 3 | Twilio ConversationRelay | 99 | 13% |
| 4 | LiveKit Agents | 98 | 13% |
| 5 | ElevenLabs Agents | 59 | 8% |
| 6 | OpenAI Realtime API | 49 | 6% |
| 7 | Built in-house (no product adopted) | 35 | 5% |
| 8 | Grok Voice Think Fast 2.0 | 29 | 4% |
What this means
Agents almost never raise Azure Voice Live API without choosing it: 2 sessions raised against 17 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 754 sessions in voice agents are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every voice agents run can be replayed on the board.
If you work on Azure Voice Live API: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Azure Voice Live API?
Yes. Azure Voice Live API was chosen in 17 of the 754 judged sessions in voice agents, a 2% install share, ranking eighth in its category.
Does Claude Code recommend Azure Voice Live API?
In 1 of the 157 sessions in voice agents run with Claude Code, which is 1%.
Do different coding agents treat Azure Voice Live API differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 1% and 5% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Azure Voice Live API considered but not chosen?
It was raised as a candidate in 2 sessions without being chosen, and chosen in 17. That is a 89% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.