SpaceXAI emailed out a link to its Voice Agent Builder on Monday. The page promises a working phone agent in under two minutes and quotes five cents a minute.
Six days before that email went out, the default model behind that number moved to eight cents.
So, the verdict, up front: the Builder is a genuinely good product, and you should test it. But if you deploy on it this week and leave the model setting on default, your audio line item is 60% higher than the page you clicked from. That is not a scandal. It is a documented, announced change that the marketing page has not caught up to, and it will show up on your invoice whether or not you noticed. Below is what the thing actually is, what it actually costs once you count every meter, where the published numbers disagree with each other, and the one console setting worth checking tonight.
The relay race and the standing order
Two ideas make the rest of this make sense, and both are simple.
First, how a phone agent normally works. Your voice becomes text. The text goes to a language model. The model’s answer becomes sound again. Three runners, two baton handoffs, and each handoff costs you time and a little accuracy. That is why so many AI phone agents have that beat of dead air where you wonder if it hung up on you. Grok Voice runs one runner instead. Audio in, audio out, one model, no batons. That is the actual engineering claim, and it is why the latency numbers are as good as they are.
Second, the standing order. When you point your code at a model name ending in “latest,” you are not choosing a model. You are leaving a note at the deli that says send me whatever’s new. Convenient. Right up until whatever’s new costs more than the old thing, and nobody calls to ask if that’s alright.
That second idea is the whole story this week.
What actually shipped
Voice Agent Builder launched in beta on July 1, 2026. It is a browser console, not a code library. You write a plain-language description of how a call should go, upload documents for the agent to draw on, connect tools, pick a voice, and attach a phone number. Every account gets a free number, and you can connect an existing one over SIP from any major provider.
The parts that matter for real deployments are the unglamorous ones. Calls are recorded and transcribed, and you can see which tools the agent used on each one. Guardrails let you define things the agent will refuse, like reading a card number back to a caller. It connects to Gmail, Google Calendar, Outlook, Linear, Notion, and OneDrive, and it takes custom MCP servers for anything internal. Compliance posture is SOC 2 Type II, HIPAA eligible with a BAA available, and GDPR.
The voice roster in the docs lists 26 built-in voices, and you can clone one from about two minutes of audio. Worth flagging: some coverage of the launch reported 80 or more built-in voices. The published documentation lists 26. Use the docs.
Where the published numbers disagree
This is the part no recycled launch article will give you, so it gets its own section.
The price. SpaceXAI’s own launch post quotes five cents a minute, hedged with the word “currently,” plus a penny a minute for telephony on a provisioned number. Then Grok Voice Think Fast 2.0 shipped on July 29 at eight cents a minute. On August 5, the grok-voice-latest alias stopped pointing at the five-cent model and started pointing at the eight-cent one. The marketing page still said five cents when the campaign email went out on August 11. What is genuinely unconfirmed is whether the Builder’s bundled platform rate followed the API alias. Nobody has published that. Which means the only reliable source for what you are being charged is your own console billing page, not any page with a “Try It Free” button on it.
The benchmark. The landing page shows Grok Voice Think Fast 1.0 at 67.3% on τ-voice Bench, against Gemini 3.1 Flash Live at 43.8% and GPT Realtime 1.5 at 35.3%. Two things about that. The good news first: τ-voice is not a vendor benchmark. It is run by Sierra, published with a paper and an open GitHub repo, and that is a meaningfully stronger footing than a self-scored chart. The catch is that the chart on the page is a snapshot from the 1.0 launch in April. On Sierra’s live leaderboard today, third place belongs to a Qwen Realtime model at 53.7%, well above both competitors shown on the page.
And then the genuinely strange one. On Sierra’s own live board, Think Fast 2.0 sits at 62.5%, below Think Fast 1.0 at 67.3%. The newer, pricier model scores lower than the one it replaced. Artificial Analysis, running its own τ-voice measurement, reports the opposite order: 2.0 ahead of 1.0, 56.5% against 52.1%. Both are third-party. Neither is lying. Different harnesses produce different absolute numbers, which is exactly why “number one on the leaderboard” is a marketing sentence and not an engineering one. The practical read is that 2.0 is clearly faster, with time to first audio dropping from 1.25 seconds to 0.70 seconds, and that its task-completion advantage over 1.0 depends entirely on who ran the test.
The concurrency cap. The launch post describes the product as being for people who want high-volume production voice agents. The speech-to-speech documentation lists a default limit of 10 concurrent sessions per team, with a maximum session length of 120 minutes. Ten simultaneous calls is a dentist’s office, not a call center. The limit is raisable on request, but plan around it rather than discovering it during a Monday morning rush. Note that at least one secondary write-up lists 100 concurrent sessions and a 30-minute cap. That contradicts the primary documentation, which was last updated July 27, 2026. Trust the docs.
The region. The voice overview page advertises multi-region infrastructure and EU data residency options. The speech-to-speech model page lists exactly one cluster, us-east-1. If data residency is a live requirement for your compliance team, get that answered in writing before you build.
What it actually costs
Proprietary and commercial. No open-source component, no free tier, no published volume discount. Every account gets one free phone number, and browser testing costs nothing, which is a real on-ramp but not a free plan.
The meters, as published on August 12, 2026:
Audio on Think Fast 2.0: $0.08 per minute, billed on audio sent and received
Audio on Think Fast 1.0, if you pin it: $0.05 per minute
Text input events: $0.004 each
Telephony on a provisioned number: $0.01 per minute
Your knowledge base lookups: $2.50 per 1,000 searches
Web or X search during a call: $5.00 per 1,000 calls
Attachment search: $10.00 per 1,000 calls
Run a real call through that. Five minutes, on a provisioned number, where the agent checks your uploaded policy docs three times and searches the web once. On the default model that is roughly 46 cents. Priced at the number on the landing page, the same call is about 31 cents. Call it a 48% gap between the advertised call and the actual one.
Scale it and the shape gets clearer. A support line running 3,000 minutes a month pays $240 in audio on the default model against $150 on the pinned older one. Ninety dollars a month, appearing with no deploy, no changelog entry in your repo, and nothing in anyone’s sprint.
One more line worth knowing about: requests blocked for usage-policy violations still bill at five cents each.
Re-verify all of these before your next billing cycle. This product is in beta and the pricing has already moved once in six weeks.
So what
Do this. Open your console and look at what model your voice agents are actually pointed at. If it says latest, you moved to the eight-cent model on August 5. Decide on purpose: pin grok-voice-think-fast-1.0 and keep the cheaper rate or stay on 2.0 because 0.70-second response time is worth the money to you. Both are defensible. Finding out in September is not.
Skip this. The leaderboard screenshot on the landing page. It is four months old, its competitive set has changed, and the two independent measurements of 1.0 versus 2.0 disagree on which one is better. Test on your own call recordings instead.
Wait on this. Anything that needs more than 10 simultaneous calls, or EU data residency. Both are answerable, neither is answered on the marketing page, and both are the kind of thing you want in writing before you build a support line on top of it.
Steal this line. Any model name ending in “latest” is a standing order to accept whatever the vendor ships next, including its price.