OpenAI Realtime API Tool-Calling for Voice Agents vs Together AI DeepSeek R2 Distilled Serverless Inference

“The primitive here is a persistent WebSocket session with a function-call interrupt layer baked into the audio stream — the model can pause generation, hand off to your tool handler, and resume speech without re-initializing the session. That's the real engineering win and it's non-trivial to replicate yourself. The DX bet is that you define tools exactly like the chat completions API (JSON schema, same function signature pattern), which means any developer who's shipped tool-calling before has a five-minute onboarding. The moment of truth is wiring up a real function call and measuring the pause — it holds under 300ms in testing, which is the threshold where voice stops feeling broken. You cannot replicate this with a weekend Lambda hack because the latency management is built into the model's generation loop, not tacked on at the HTTP layer. The specific decision that earns the ship: they reused the exact same tool schema from chat completions instead of inventing a new voice-specific abstraction.”

“The primitive here is clean: OpenAI-compatible serverless inference endpoint for distilled reasoning models, no infra to manage. The DX bet Together AI made is correct — zero-config model access with standard chat completions API means you swap one base URL and one model string and you're calling DeepSeek R2 distilled from existing code. The 32B at $0.80/M tokens is the real story: that's sub-dollar-per-million for a model that punches well above its weight class on reasoning benchmarks. The weekend alternative is self-hosting on RunPod or Modal, which works but adds cold-start latency, VRAM management headaches, and ops overhead that Together simply removes. Ship this if you're building anything that needs cheap chain-of-thought reasoning without the frontier model bill.”

“Direct competitors are Vapi, Retell AI, and Bland — all of which have been shipping voice-plus-tool-calling for 12-plus months and have production deployments at scale. OpenAI entering this space natively collapses the middleware layer those companies built, which is the real story here, not the feature itself. The scenario where this breaks is complex multi-tool chaining mid-conversation: if tool A's response needs to trigger tool B before the model speaks, you're managing that orchestration yourself with no built-in retry or error-voice feedback primitives. What kills the third-party voice API space in 12 months: OpenAI ships this natively with better pricing and the middleware layer becomes a thin wrapper nobody pays for — that's already in motion. For this to be wrong, Vapi and Retell would need to have built workflow orchestration and reliability guarantees so far ahead of OpenAI's primitives that the abstraction is still worth the cost. They might, but the clock is running.”

“Direct competitors are Fireworks AI, Groq, and Replicate running the same or similar distilled checkpoints — so Together is not selling exclusivity, they're selling reliability and price. The scenario where this breaks is high-concurrency production workloads where serverless cold-start variance becomes a latency SLA problem; Together's serverless tier has no guaranteed throughput contracts in the base offering. What kills this in 12 months is not a competitor but the underlying model provider: if DeepSeek ships R3 distills that are 2x better at the same cost, this specific offering goes stale and Together has to scramble to re-serve. That said, Together's track record of being early on new model availability is the actual moat here — they've consistently been first or second to serve hot open-weight checkpoints, and that speed-to-availability is worth paying for if you're iterating fast.”

“The thesis this bets on: within 3 years, the primary interface for a significant class of enterprise software — CRM updates, inventory checks, appointment scheduling — will be voice, not GUI, because the tool-calling layer finally makes voice capable rather than merely conversational. That's a falsifiable claim and the dependency is that latency stays under the perceptible threshold as tool complexity scales. The second-order effect that isn't obvious: this transfers power from the UI layer to the API layer — if your product has a clean API, it becomes voice-accessible overnight; if it doesn't, it's locked out of the voice-first workflow. The trend line is the collapse of the IVR industry into LLM-native voice agents, and this API is early-to-on-time for that transition — the IVR replacement use case has been theoretically possible for 18 months but practically blocked by exactly the latency problem this solves. The future state where this is infrastructure: every enterprise SaaS ships a voice interface that's just a Realtime API connection pointed at their existing REST endpoints.”

“The thesis Together AI is betting on: by 2027, the majority of production LLM inference will run on open-weight distilled models, not frontier APIs, because the quality gap closes faster than the price gap opens. That's a falsifiable and plausible claim — the DeepSeek R1 distillation story already validated it at the 7B-32B range. The dependency that has to hold is that distillation techniques keep pace with frontier capability jumps, which is not guaranteed if frontier labs accelerate architectural innovation faster than distillation pipelines can follow. The second-order effect that's underappreciated: cheap reasoning inference at this scale shifts power from model labs to inference infrastructure providers — Together, Fireworks, Groq become the AWS to the model labs' hardware vendors. Together is on-time to this trend, not early, but their execution on catalog breadth means they're well-positioned if the trend accelerates.”

“The buyer here is a developer or a technical team at a company building a voice product — that's a real buyer with real budget. But the pricing math is brutal for production workloads: at $200 per million output audio tokens, a contact-center replacement running 8-hour shifts burns through budget in ways that make the unit economics work only at high ACV enterprise deals. The moat question is the real problem: this is OpenAI's own API, so the 'moat' for anyone building on it is exactly zero — OpenAI can change pricing, deprecate the model, or ship a competing product that bundles this functionality. What survives a 10x model price drop is the application layer, the integrations, the workflow logic — not the voice API call itself. If I'm a founder building on this, I'm nervous about the same company that provides my infrastructure also being my most likely acqui-hire target or direct competitor. Skip not because the technology isn't real, but because building a business on a single API provider's experimental endpoint is a structural problem, not a product problem.”

“The buyer is any developer or startup running LLM inference who currently pays OpenAI or Anthropic rates for reasoning tasks that don't require frontier-model quality — that's a real and large budget line item. The pricing architecture is usage-based and scales directly with value delivered, which is the right structure for inference. The moat question is harder: Together's defensibility is not the models (open weights, anyone can serve them) but latency, reliability, and the breadth of the model catalog creating switching friction once you've standardized your inference client on their SDK. The existential risk is that this is fundamentally a margin business on commodity compute, and Cloudflare Workers AI, AWS Bedrock, and Google Vertex are all moving to serve the same checkpoints at infrastructure-subsidized prices. Together needs to win on speed-to-new-models and developer experience before the hyperscalers catch up on catalog breadth, and so far they're doing it.”