Claude 4 API: Tool Use Streaming & Prompt Caching vs SAM 3 (Segment Anything Model 3)

“The primitive here is clean: incremental tool-call deltas over SSE, and a cache-control header you attach to prompt segments to pin them server-side. The DX bet is that complexity lives in the HTTP layer, not in a new SDK abstraction — you opt in per-request, no new mental model required. The moment of truth is calling `stream=true` on a tool-use request and watching partial JSON arguments arrive before the model finishes thinking, which actually matters for agent loops where you want to dispatch work early. This is not a weekend-script replacement — implementing correct incremental JSON parsing for partial tool arguments plus a reliable distributed cache with 2M token capacity is a real engineering problem Anthropic has solved for you. The specific decision that earns the ship: cache invalidation is explicit and cache hits are reflected in the usage object, so you can actually measure what you're saving instead of guessing.”

“The primitive is clean: a promptable segmentation model that takes a point, box, or mask hint and returns a high-quality mask — now at 30fps on video without frame-by-frame re-prompting. The DX bet Meta made is weights-first: you get the model, the inference code, and a reasonably documented API surface without being forced into a proprietary serving layer. The moment of truth is plugging this into a video pipeline, and SAM 2 already proved that story works — SAM 3's real-time throughput removes the one blocker that kept it out of production-adjacent workflows. The non-commercial license is the only thing that stops this from being an unconditional ship for anyone building a product, but for research and internal tooling it's a rare case of a large lab releasing something you actually can't replicate over a weekend.”

“Direct competitors are OpenAI's cached completions and Google's context caching in Gemini 1.5 — both shipping for months — so Anthropic is catching up, not leading. The specific scenario where this breaks: cache hit rates depend entirely on prompt structure, and developers who dynamically compose system prompts (inserting user-specific context at the top) will see near-zero cache utilization and pay full price while assuming they're saving money. The prediction: this feature doesn't get killed — it becomes table stakes infrastructure and Anthropic wins by having the largest cache window (2M vs. competitors' current limits). What would have to be true for me to be wrong: OpenAI ships a 10M token cache window before Anthropic's ecosystem matures, commoditizing the advantage. Still a ship because the streaming tool-use delta is genuinely differentiated — no competitor has clean partial-argument streaming for tool calls yet, and that changes agent loop architecture in ways that matter.”

“Direct competitors are SAM 2 (which this replaces), Grounded-SAM pipelines, and anything EfficientSAM-derived — so the question is whether the 30fps claim holds outside Meta's benchmark hardware, because every vision model ships 'real-time' until you run it on the V100 your university gave you in 2021. The scenario where this breaks is dense, occluded multi-object video with fast motion — the point-prompt paradigm degrades hard when targets disappear and re-appear, and SAM 3 hasn't shown evidence it solves that. What kills it in 12 months: not a competitor, but the non-commercial license — the moment a team wants to ship this in a product they hit a wall, and a permissively licensed distillation from a startup will eat the production use case. Still, as a research primitive it genuinely ships.”

“The thesis this bets on: by 2027, the dominant AI application architecture is a persistent agent with a large, stable context (tools, memory, instructions) that gets reused across thousands of user interactions — making context I/O cost the primary unit economics lever, not generation cost. The dependency that has to hold: agents don't collapse back to stateless chatbots, and context windows keep growing faster than per-token prices fall. The second-order effect nobody's talking about: prompt caching at 2M tokens makes it economically viable to give every enterprise user a fully-loaded, role-specific agent context at request time — which shifts competitive differentiation from 'who has the best model' to 'who has the best cached context corpus,' effectively making knowledge curation the new moat. This tool is riding the trend of context-window expansion-as-infrastructure, and it's on-time, not early — but the streaming tool-use primitive is ahead of the curve on agent loop efficiency. The future state where this is infrastructure: every production agentic system has a cache manifest the same way it has a CDN config.”

“The thesis SAM 3 is betting on: by 2027, perception — not reasoning — becomes the bottleneck in embodied and spatial AI systems, and whoever owns the best open segmentation primitive owns the scaffolding layer every robotics, AR, and autonomous system is built on. The dependency that has to hold is that point-cloud and video segmentation remain distinct hard problems from what foundation model vision encoders solve natively — if GPT-5 level models segment adequately as a side effect of scene understanding, this primitive commoditizes. The second-order effect nobody is talking about: SAM 3 with 3D point cloud support quietly hands robotics researchers a perception backbone they don't have to build, which accelerates the gap between labs with and without ML infrastructure. Meta is riding the spatial computing and embodied AI trend line, and they are early — the consumer AR market that actually needs real-time 3D segmentation doesn't exist at scale yet, but the research infrastructure bet is the right one to make now.”

“The buyer is the engineering team at any company running Claude in production with long system prompts or multi-step agents — this comes out of the AI infrastructure budget, not a new budget line, which means no procurement friction. The pricing architecture is sound: cache reads at ~90% discount means the savings are real and measurable in the first billing cycle, which creates immediate retention — developers who restructure prompts to maximize cache hits are now architecturally coupled to Anthropic's caching implementation. The moat question is the honest one: this is infrastructure that OpenAI and Google will match, so the defensible position isn't the feature itself but the ecosystem of developers who've restructured their codebases around it. What survives a 10x model price drop: the streaming tool-use architecture, because that's about latency, not cost. The specific business decision that makes this viable is pricing cache reads as a separate SKU — it lets Anthropic capture value from high-volume production workloads without losing price-sensitive experimenters.”

“There is no buyer here — the non-commercial research license means no one writes a check, which makes this a research artifact, not a product. The moat question is irrelevant when there's no revenue model: Meta is using this as a talent signal and ecosystem play, not a business, and any startup that tries to build on top of it faces an immediate licensing conversation the moment they seek funding or revenue. What would need to change for this to be a ship from a business perspective: Apache 2.0 or a clear commercial licensing path with predictable pricing — right now the 'free' cost hides a legal liability that kills it as a foundation for anything you want to sell. Respect the research contribution, but there's no business here.”