NVIDIA Built a CPU for AI Agents. Here's What Changes for Your Stack

Posted on Nov 6 • Edited on Nov 6 • Originally published at toolsdig.com

NVIDIA has spent years selling GPUs to people who train models. On 5 November 2026 it published results for something different: a CPU built for the part of the job that happens after training — running agents. The chip is called Vera, and NVIDIA's headline claim is that in a 100 MW data-center comparison it delivers 1.6x more agents per watt than the fastest x86 CPU, and 2x faster agent speed than the most energy-efficient x86 CPU.

Those are NVIDIA's numbers, from NVIDIA's own comparisons. I haven't run them, nobody independent has reproduced them yet, and this article will keep saying so — because the numbers are still worth your attention even with the caveat attached. Agents don't bottleneck on the model call the way most people assume. They bottleneck on everything around it: spinning up sandboxes, orchestrating tool calls, running databases, shuttling context between steps. That's CPU work. And that's exactly what Vera is aimed at.

Vera is NVIDIA's first data-center CPU designed specifically for AI agent workloads. The specs, as published:

The memory bandwidth number is the one to stare at. Agents are memory-hungry in a way that looks nothing like a web server: long contexts, constant tool-output shuffling, databases being queried mid-reasoning. 1.2 TB/s is the spec that makes the agent claims plausible, and it's also the spec that would be easiest to verify independently once hardware reaches reviewers.

Vera sits in the Vera Rubin platform — the NVL72 rack system NVIDIA is now shipping with Oracle. Which brings us to the second piece of 5 November news.

On the same day, NVIDIA and Oracle announced that Vera Rubin NVL72 systems and Vera CPUs are generally available on Oracle Cloud Infrastructure (OCI), with Superclusters expanding toward multi-gigawatt scale.

That matters more than the chip specs, for a simple reason: you will almost certainly never buy a Vera CPU. It is a data-center part, sold to cloud providers and hyperscalers, not something that goes in a workstation. What you will buy is the cloud capacity it powers — agent sandboxes, hosted coding agents, orchestration services running on OCI and, presumably, other clouds later. The availability announcement is the part that reaches your bill.

NVIDIA didn't just publish its own comparisons. It published partner-reported results. Here's the full set, with the source of each number, because the source is the whole story:

Read that table like a sceptic, because I am one. The Daytona number is the most concrete: 1,000 sandboxes in 10.8 seconds instead of 32.3. Sandbox spin-up is the tax every coding agent pays before it does anything useful, and a 3x cut there is the kind of thing you'd feel in a real product — shorter waits, cheaper per-agent runs, more parallel agents for the same money. The DeepInfra number is the most specific: 29 ms orchestration steps, measured on bare metal against named chips. The Perplexity number is the vaguest — "~1.5x faster" with no benchmark named — and it's the one I'd discount hardest until Perplexity says more.

And the honest frame for all of it: these are partner-reported numbers, selected by NVIDIA, in a launch announcement. No independent lab has run these tests. The ClickHouse and DuckDB results are the most independently checkable — ClickBench is a public benchmark, and DuckDB numbers are reproducible — so those are the ones to watch for confirmation.

Here's the part that matters, and it's smaller than the headlines but real.

If you run agents in the cloud, the bottleneck you pay for is increasingly the orchestration layer, not the model. A coding agent's bill is model tokens plus sandbox time plus tool-call latency. Vera attacks the second and third items. If cloud providers pass the efficiency through — and that's a real "if," pricing is their decision, not NVIDIA's — agent runs get cheaper and faster in the background, without you changing a line of code.

If you build agent infrastructure, the numbers to watch are sandbox spin-up time and orchestration latency per step. Those are the two metrics in NVIDIA's table that map directly to user experience: how long before the agent starts working, and how much dead time sits between its steps. Ask your provider what those numbers are today, on your current hardware. If they can't answer, that's a gap worth closing before you care about which CPU is underneath.

If you just use coding agents, nothing changes tomorrow. Your agent doesn't get faster because a chip launched. It gets faster when your provider deploys Vera-based capacity and your bill reflects it — which is a months-long chain, not a launch-day event.

You don't need to wait for Vera to get value from this announcement. Run this five-minute check on whatever agent setup you already pay for:

The bottom line is a measured one. NVIDIA is betting that the agent era has a CPU problem, not just a GPU problem — and the partner numbers, especially Daytona's sandbox times and DeepInfra's orchestration latency, are the kind of concrete, checkable claims that make the bet interesting. If they hold up under independent testing, the agents you already pay for get faster and cheaper without you lifting a finger. If they don't, it's another launch-day chart. The numbers to watch are the public ones — ClickBench, DuckDB, sandbox spin-up — because those are the ones nobody can hide behind a press release.

Are your agent runs slow because of the model, or because of everything around it? That's the question Vera is really asking. I'd be curious what your own numbers look like.

Sources: NVIDIA Newsroom blog, "Vera Delivers the Best of Both Worlds: Highest Throughput and Fastest Agents" (5 November 2026); Unite.AI, "NVIDIA Pits Vera CPU Against X86 on Agent Speed and Power Capacity" (5 November 2026); Oracle AI World press release via StorageNewsletter (5 November 2026). All facts come from the launch-day reporting, checked 6 November 2026. No hands-on testing was performed for this article. This breaking article is not the daily buyer-intent post, and it contains no affiliate links.