The Short Answer
Cloudflare reports that daily requests from AI agents on its network grew by more than 1,700% in a year, and that more than half of Internet traffic in 2026 was not human. When software sends most requests, the layer deciding which agent answers each one is business logic. On ibl.ai you own all the code and the data, including that routing layer, on any model.
The figures come from Cloudflare's September 30, 2026 post "The Internet has a second audience" and its October 20, 2026 press release announcing more than 10 million developers on its platform, up from 7.4 million the prior quarter.
They are Cloudflare's measurements on Cloudflare's network. More than 20% of the web sits behind that network, by Cloudflare's own count, so they are a large sample, not a census of the whole Internet.
What did Cloudflare actually report about AI agent traffic?
Cloudflare's September 30 post makes four claims that matter for anyone building or buying AI agents. Each is a number Cloudflare published, and each measures something different, so they should not be added together.
| Cloudflare figure | Value | What it measures |
|---|---|---|
| Daily AI agent requests | +1,700% | Growth over the past year in requests from AI agents |
| Non-human share of traffic | >50% | First year more than half of Internet traffic was not human |
| Average HTTP requests per second | 63M β 115M | End of 2024 to September 2026, all traffic, peaks above 150M |
| Crawler requests for AI training | 22% β 52% | Spring 2025 to June 2026, by the crawlers' stated purpose |
| Human traffic in heavily crawled categories | down up to 40% | Retail, software, IT services and financial services, in under a year |
The 1,700% is growth in daily AI agent requests. The 63 million to 115 million is total HTTP traffic. The first is a rate of change in one slice; the second is the whole network, so one does not explain the other.
Why does AI agent traffic matter to organizations that are not websites?
Cloudflare's post is written for site owners: a second audience that reads pages, rarely clicks, and may or may not pay. That reading is correct, and it is only half of the shift.
The same kind of agent that reads websites can also file support tickets, query internal systems, book appointments and ask for refunds on a person's behalf.
Any organization that runs agents of its own now receives requests from people and from software, at volumes no help desk was sized for.
Cloudflare's own framing points this way. Its post argues that agents can be customers, and that a site turning an agent away may be turning away the person behind it.
The question for an organization is not whether to answer agents, but which of its own agents answers each request.
What is an AI agent routing layer, and why is it separate from the model?
A routing layer is the step that reads a request, decides what it is about, and hands it to the agent built for that job. It sits in front of the agents, and its decision is usually a small, fast model call rather than a long generation.
It became its own layer in 2026. Between September 15 and October 6, six vendors shipped dedicated decision models for exactly this job, three of them with downloadable Apache 2.0 weights, which we covered in Six Decision Models in Three Weeks. Three You Can Own.
The reason is arithmetic. If request volume rises an order of magnitude, sending every routing call to a frontier model multiplies the bill by the same factor. A routing decision does not need prose; it needs a label and a confidence score.
How does ibl.ai route each request to the right agent?
ibl.ai agent workflows include a Classifier step, shipped in the November 6 to 13, 2026 releases. It sends each message to a decision model, reads back an answer, and follows the path wired to that answer.
There are three answer types. Pick a Category takes 2 to 20 categories, each with its own path to its own agent. Yes or No covers binary decisions. Rate on a Scale takes 2 to 10 levels for triage-style decisions.
Every type has a Fallback path. Below a confidence threshold, 0.6 by default, the request goes to a fallback agent that asks a clarifying question instead of guessing. In the release demo, "I was charged twice for my plan this month" was routed to Billing at 0.94 confidence.
A team can test the decision on a sample message before publishing, and the same test is exposed over the platform's REST API, so real messages can be replayed against a routing rule to see which would fall back before it goes live.
Who should own the routing rules when most requests come from software?
Routing rules decide which customer reaches which agent, with which data, at what confidence. That is business logic in the same sense as a pricing table or an escalation policy, and it changes every time a product or a team changes.
On ibl.ai the workflow editor ships as source in the SDK, the workflow definitions can be read back over the REST API, and the runtime comes under ibl.ai's Full Code License to run on our hosted cloud or on your own servers. You can build it into your own app with Agentic Base.
The decision model comes from the organization's model registry and each agent runs the model chosen for it, so neither the router nor the agents behind it is tied to one vendor's models. When a cheaper or better decision model ships, it is a setting, not a migration.
Why does per-seat AI pricing break when agents send the requests?
Per-seat pricing counts people. Cloudflare's numbers describe a world where requests from AI agents grew more than 1,700% in a year while human traffic fell in some categories.
An agent acting for a customer has no seat, and a router answering every inbound request cannot be licensed to a named few.
A seat-priced platform scales its bill with headcount whether the requests come from those people or not. A usage-based or self-hosted platform scales with the work actually done, which is the only shape that tracks a 1,700% rise in agent requests.
ibl.ai has no per-seat pricing: you pay for the tokens consumed or own the stack and pay for the compute. More than 1.6 million users across 400+ organizations run it this way, including NVIDIA, MIT and Syracuse University, through Agentic OS.
What should a team do about rising AI agent traffic this quarter?
Start with three questions. Which inbound requests already come from agents rather than people? Which of your agents should answer each kind? And what happens when the routing decision is unsure?
The first is a measurement question your edge provider can help with. The second and third are design questions, and they are cheaper to answer with a routing step you can test on real messages than with one large agent that tries to cover everything.
ibl.ai is family-owned and operated from New York, NY. If you want to see a Classifier wired to two or three of your own agents and tried on messages your team actually receives, talk to the ibl.ai team.