Together AI Inference Stack vs xAI Grok API Streaming, Function Calling & Vision

“The primitive here is a production-grade inference scheduler — continuous batching, KV cache management, speculative decoding — open-sourced so you can actually read what's happening instead of praying to a black box. The DX bet is correct: they've put the complexity in the runtime and left the API surface clean, which means you can run the stack locally, inspect it, and still fall back to their managed endpoint without rewriting anything. The moment of truth is deploying a 70B model on your own hardware and hitting sub-100ms p50 — if that claim holds under real traffic shapes, this earns its keep in a way no weekend Lambda project can replicate. The specific decision that earns the ship is open-sourcing the actual scheduler logic, not a demo harness — that's the difference between a marketing stunt and a real engineering contribution.”

“The primitive here is clean: streaming tool call deltas over SSE and base64/URL image inputs on the standard chat completions schema. The DX bet is OpenAI API compatibility, which means if you're already using the openai-python SDK you can swap the base_url and model name and streaming function calls just work — that's the right call. The moment of truth is wiring up a tool-use loop with streamed partial JSON, and xAI's schema handles that with the same delta accumulation pattern OpenAI uses, so existing parsers don't break. My one gripe: the docs don't yet have a working multi-turn vision + tool-call example in a single request, which is exactly the edge case agentic builders hit first. Shipping because the primitive is real and the compatibility decision was correct, but docs need to catch up to the capability.”

“Direct competitors are vLLM and TGI, both already open-source, already battle-tested in production — so Together has to beat an existing open-source default, not just incumbents charging money. The specific scenario where this breaks is multi-tenant variable-sequence-length workloads with cold model loading, where scheduling heuristics matter enormously and 'sub-100ms for 70B' benchmarks measured on warm, uniform batches become meaningless. What kills this in 12 months is not a competitor but model providers like Groq or Cerebras making the hardware-software co-design so tight that pure software scheduling stacks lose the latency game entirely. That said, the 70% price cut on the managed API is real and verifiable today, and open-sourcing the scheduler creates genuine credibility — I'm shipping this because the pricing is falsifiable and the code is inspectable, not because I trust the benchmark methodology.”

“Direct competitors here are OpenAI GPT-4o and Anthropic Claude 3.5 Sonnet — both of which have had streaming function calling and vision for over a year. So this is a parity release, not an innovation release, and anyone calling it a leap forward hasn't read the OpenAI changelog from 2024. The scenario where this breaks is high-volume agentic loops with complex tool schemas: xAI's rate limits and latency SLAs are not yet public or battle-tested at the scale OpenAI has handled. What kills this in 12 months isn't a competitor — it's xAI itself, if Elon's attention migrates and the API roadmap stalls. But if the team executes, the Grok-3 reasoning quality on structured outputs is genuinely competitive, and the pricing on Grok-3-mini undercuts GPT-4o-mini meaningfully. Shipping as a credible second-source supplier, not a category winner.”

“The thesis here is falsifiable: within two years, open-weight model inference will be a commodity infrastructure layer where cost and latency are determined by software scheduling efficiency, not proprietary model access — and Together is betting that whoever owns the best open-source scheduler owns the default deployment target. For that to pay off, speculative decoding and continuous batching need to keep delivering meaningful gains over naive implementations, and hardware cost curves need to continue favoring general-purpose GPUs over custom silicon. The second-order effect that matters is not cost reduction but standardization: if this stack becomes the reference implementation, Together sets the API contract that every upstream tooling layer targets, which is a distribution moat that doesn't look like a moat until it is one. They're riding the open-weight model proliferation trend — Llama, Mistral, Qwen — and they're on-time, not early, which means execution quality is the only differentiator left.”

“The thesis this release bets on: within 18 months, agentic applications will be the primary consumption pattern for frontier LLMs, and model providers without streaming tool calls and multi-modal input will be routed around by orchestration layers. That's not a bold prediction — it's already happening, which means xAI was late to this specific feature set. The second-order effect that matters isn't the feature itself but the distribution: X/Twitter integration and the Grok user base give xAI a data flywheel that OpenAI and Anthropic don't have access to, and vision inputs accelerate that flywheel by pulling in social image context. The trend line is the commoditization of inference primitives — xAI is on-time for parity but needs a differentiated surface (the X data moat) to matter in 24 months. Shipping because the platform trajectory is plausible, but this specific release is table-stakes infrastructure, not a strategic move.”

“The buyer is an ML engineer or CTO at a company running meaningful inference volume who needs to choose between self-hosting and a managed API — and Together is now competing in both lanes simultaneously, which is smart positioning because it removes the 'we'll leave when we can afford our own GPUs' exit ramp. The pricing architecture is usage-based, which aligns with value delivered, but the 70% reduction is a race-to-the-bottom move that only works if Together's infrastructure efficiency actually outpaces margin compression from falling GPU prices. The moat is not the price cut — that's temporary — but potentially the open-source scheduler creating a developer community that standardizes on Together's API shape, generating switching costs through tooling integration rather than proprietary lock-in. The stress test is simple: if Fireworks AI or Groq matches the price and the hardware story, Together needs the community flywheel to already be spinning, and that's a bet on execution speed they've not yet proven at scale.”

“The buyer here is a dev team already evaluating multi-provider LLM strategies, and they're writing this check from an infra or AI budget — but only after their primary provider (OpenAI or Anthropic) has failed them on cost, latency, or availability. The pricing on Grok-3-mini is genuinely aggressive and the moat question is interesting: xAI has real-time X data access as a differentiated retrieval surface that no other provider can replicate, but that's not surfaced in the API in a way that creates lock-in today. The structural risk is that xAI is a single-founder-attention company in a market where reliability and roadmap predictability matter more than raw capability. Until xAI publishes SLAs, uptime history, and a credible enterprise support tier, this stays as a secondary provider for cost-sensitive workloads — not a primary bet. Skipping not on product quality but on business infrastructure maturity.”