ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

Open Weights Took 62% of the Tokens and Under 9% of the Spend

ibl.aiAugust 28, 2026
Premium

Vercel's AI Gateway put open-weight models at 62% of token volume in late August, up from 11% in April — while closed models still took roughly two-thirds of the spend. That split is not a contradiction, it is what a correctly routed AI estate looks like, and it is only available if switching models is a config change.

The Short Answer

Open-weight models reached roughly 62% of token volume on Vercel's AI Gateway on 22 August 2026, up from 28.4% in late June and 11% in April — while capturing under 9% of the spend, with closed models holding around two-thirds of it. That split is a routing strategy, not a contradiction. On ibl.ai you own all the code and the data and run it model-agnostic across any LLM, which is what makes acting on it a configuration change.

Volume and spend answer different questions. Reading only one of them produces the two most common wrong takes about this dataset.

What does the Vercel AI Gateway data actually say?

The gateway data says open-weight models won the volume and closed models kept the revenue, over a remarkably short period.

Vercel reports open-weight share of tokens moving from 11% in April to 29% in June to about 62% on 22 August. The June figure was 28.4% on the 24th, so the rise across two months is roughly a doubling.

Vercel publishes this as a recurring AI Gateway production index, which is what makes it unusually useful: it is measured production routing across many customers, not a survey of intentions.

One correction, because it is being repeated. The 62% figure is open-weight models overall, not Chinese models specifically. Chinese-built open models were around 29% of tokens in June 2026, at roughly one-tenth the average token price of US frontier systems on the platform. Both facts are interesting; conflating them overstates one and erases the other.

Why do open models dominate volume while closed models keep the spend?

Open models dominate volume and closed models keep spend because the two categories are being pointed at different classes of work.

At 62% of tokens, open-weight models captured under 9% of spend, while Anthropic's closed models held roughly 61–65% of it.

The explanation is unglamorous.

High-volume production work is classification, extraction, summarization, routing, reformatting, and tool-calling — tasks where a competent open model produces output a reviewer cannot distinguish from a frontier model's, at a fraction of the price.

That work generates enormous token counts and small invoices.

The spend concentrates in the narrow band where frontier reasoning genuinely changes the outcome: long multi-step agentic runs, hard synthesis, ambiguous judgment. Fewer calls, much higher value per call.

So the barbell is not a market fragmenting. It is cost engineering, executed at scale, in production — and it is roughly what a well-run AI estate should look like.

Is this evidence that open models have "won"?

No, and the framing is the problem. This data shows open models winning a specific argument — the one about routine work — rather than winning outright.

The maximalist read ("open weights have taken over") ignores that two-thirds of the money still goes to closed models for the hardest tasks.

The dismissive read ("they only have 9% of spend, so it's hype") ignores that 62% of production traffic now runs on models anyone can download and self-host.

Both readings share a mistaken assumption: that this is a contest with one winner. The organizations in this dataset are not choosing sides. They are routing.

The practical implication is that "which model should we standardize on" is the wrong question, and increasingly an expensive one.

The right question is what fraction of your workload is currently over-served by an expensive model, which is a measurable number rather than a philosophical position.

What does it take to act on this?

Acting on it requires that moving a workload between models is a configuration change rather than a migration.

That is the whole difference between this chart being an opportunity and being news.

If your application code, prompts, tool definitions, retrieval layer, and evaluation harness are bound to one vendor's API, then re-routing a workload to a cheaper open model is a project — and by the time it ships, the prices have moved again.

Three things make routing cheap:

A model-agnostic platform boundary. The application asks for a capability; the platform decides which model serves it. Swapping the answer does not touch application code.

Your own evaluation set. You cannot route by cost without knowing where quality actually degrades. Public benchmarks will not tell you; a few hundred examples of your real traffic will.

Somewhere to run the open models. The 62% is only fully available to you if you can host, which is a serving-stack question. We cover the runtime layer in the self-hosted LLM serving stack, and the architectural reason the newest open models are cheaper to serve in GLM-5.3-Flash and the KV cache.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

Why is model lock-in a form of technical debt?

Model lock-in behaves like technical debt because it accrues silently and the interest is paid in foregone savings rather than in visible failures.

Nothing breaks when you are locked in. The system works. What happens instead is that every price move, every capable open release, and every capability shift arrives as an opportunity you cannot take — and the gap compounds quarterly.

This dataset makes the cost legible. An organization that can route moved a majority of its tokens onto models costing roughly a tenth as much within four months. An organization that cannot route did not, and paid the difference.

That is also why the ownership question sits underneath the routing question. Being able to run any model is only half of it; the other half is owning the layer that decides which one runs, so the decision stays yours as the field moves.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

Frequently asked questions

Is the 62% figure about Chinese models?

No. It is open-weight models overall on Vercel's AI Gateway as of 22 August 2026. Chinese-built open models were a subset — about 29% of tokens in June — and the two numbers are frequently conflated.

Does low spend mean open models are low value?

No, it means they are cheap. The same dataset shows them carrying the majority of production tokens, which is a statement about how much work they are doing, not how little they are worth.

Should an organization move everything to open weights?

No. The pattern worth copying is routing, not switching. Move the high-volume, low-ambiguity work where quality is indistinguishable, keep frontier models for the tasks that genuinely need them, and re-measure as prices change.

The bottom line

Two numbers from the same dataset, and you need both: 62% of the tokens, under 9% of the spend.

Read together they describe an industry that has stopped asking which model is best and started asking which model is sufficient for each task. That question only pays if switching is cheap — which is a property of your architecture, not of the model market.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.

  • Model-agnostic

    Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

Related Articles

Model-Agnostic AI: Why Single-Vendor Lock-In Is the Real Risk

Betting your AI stack on one vendor's models is the quiet risk most enterprises overlook. A model-agnostic platform turns model choice into a switch you control.

Miguel AmigotMay 19, 2026

NVIDIA's Open Routing Layer: Why the Model Stopped Being the Moat

NVIDIA shipped an efficient open model and an open routing library on the same day. Together they commoditize the model layer and move the durable advantage to the routing layer — which is the one piece you should refuse to rent. What routing saves, what open weights do not buy you, and the three layers worth owning.

ibl.ai EngineeringAugust 12, 2026

AI's Price Spread Has to Rationalize. Hedge Both Ways.

A million tokens costs about $26 from one frontier lab and about $0.50 from a Chinese provider — a 52x spread for capability now 3–6 months apart. Spreads that wide close, and buyers cannot know which direction. The only position that survives either outcome is one where the model is a component you can swap.

ibl.ai EngineeringAugust 5, 2026

The Open-Weight Tipping Point: Two 2-Trillion-Parameter Models

Two models above 2 trillion parameters became available as open weights in a single week: Moonshot's Kimi K3 at 2.8T with a 1M-token context, and Alibaba's Qwen 3.8-Max at 2.4T with 95B active per token. This post does the memory arithmetic on what it actually takes to serve models that size, prices the alternatives, and explains why the durable advantage is model-agnostic infrastructure rather than any single model.

ibl.ai EngineeringAugust 3, 2026

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work — so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope · fixed timeline

A time-boxed proof of value on your real data — not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time · not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data · run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Six figures

perpetual license · you own the stack

We transfer the full source code. You own and self-host the entire platform — outright.

Best for: Government, defense, and enterprises that require perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable · zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM — Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY