Visaible/Trial

Classification stream

Every page view on the demonstration hotel site, classified at the edge and published with the evidence it rests on. Click a record for the checks that ran. Showing an assistant acting for a person; the toggle reveals crawlers, forged claims and human traffic. The design behind it is in the Part 1 report.

connecting · ably
0
Agent fetches
Measured. An assistant read the page for someone. Exposure, not a visit.
0
In-app sessions
A person tapped through from inside an assistant's app.
0
Referred sessions
Estimated. Arrived carrying an assistant's parameter. A floor.
0
Booking intents
Clicks through to the engine. Intent, not bookings.

Showing AI acting on behalf of a person. Crawlers, unverified claims and human traffic are behind the toggle. Not summed, and deliberately no total — these are different units measured different ways.

Nothing yet. There is no database behind this — the feed is live only, so a visitor arriving after an interesting event has passed sees exactly this.

Ask an assistant to open a room page. The prompt is already written:

ChatGPT — opens in a new tabClaude — opens in a new tabPerplexity — opens in a new tabGrok — opens in a new tab

Gemini and Le Chat take no prompt in a link, so those copy it and open the app — paste, then press Enter. Only Perplexity sends by itself; the rest wait for you. Grok and Le Chat will not appear in this default view — no catalogued agent and no published range respectively. Each URL carries a vsb_test tag so you can find your own fetch.


Or just load a page on the hotel site yourself. Only page views are published — assets, /api/* and robots.txt are deliberately not records.
Transport: ably · channel vsb:classifications · Part 1 report · things to try