Autumn Sale: 20% off almost everything until 15 NovemberSee the sale →

Room 03 of 08 · agents and arrivals

Who read us.

Every named machine agent this instrument has recorded, what each was actually sent, and the browser sessions that arrived afterwards from AI answer surfaces.

An agent name is a user-agent claim, not a verified organisation. What protects the figures is behaviour: an agent that breaks the published rules is withdrawn from credit with its history kept visible.

24 NAMED AGENTS1 WITHDRAWN FROM CREDIT2,527 AI-REFERRED SESSIONS53.4 GB SENT TO MACHINES
Section 01

Every named agent, and what each was sent.

One row per agent, every column from the same table and the same window, so the row sums are meaningful. Byte counts are the content actually shipped, not page counts. Amazonbot's row is kept in full and credited nothing.

AgentAttemptsServedNo contentDays seenAnchorsData sent (MB)Last seen
bingbot36,97732,3464,6311156,00013,275.412 Oct
amazonbot
withdrawn from credit - history kept in full, nothing credited
21,79618,8032,993454,3037,271.53 Aug
perplexitybot21,55319,1282,4251144,0726,570.912 Oct
oai-searchbot18,45718,0144431164,7615,440.312 Oct
claudebot17,21011,8395,3711164,7069,993.012 Oct
meta-externalagent13,1558,3804,7751125,6483,776.112 Oct
gptbot13,0097,0555,9541175,4621,829.512 Oct
chatgpt-user11,81611,0128041212,0424,216.812 Oct
googleother7,5193,5343,985963,0791,360.612 Oct
duckassistbot1,5521,50745111913549.312 Oct
bytespider1,3341,2458994177369.412 Oct
ccbot987919169319.912 Oct
The 24 agents together: 164,563 attempts, 132,962 served, 53.4 GB sent.Served here counts the raw rule (status + bytes); the credited study figure of 114,159 additionally removes the withdrawn agent.
All 24 named agentsthe long tail, same columns, same window
AgentAttemptsServedNo contentDays seenAnchorsData sent (MB)Last seen
google-extended2341913175.39 Oct
cohere1721511135.512 Oct
youbot1321111114.29 Oct
claude-user990483.112 Oct
perplexity-user615561.428 Aug
mistral413442.324 Sep
xai-grok303130.09 Oct
grokbot303320.09 Oct
anthropic-ai312232.21 Aug
claude-web303231.01 Aug
generic202120.55 Oct
mistralai-user101110.06 Oct

Source: wp_teas_citations grouped by agent - window: 2 Jun 2026 to 12 Oct 2026 - bytes are SUM(bytes_served) - live.

The coverage cross-check - this instrument against the raw access loguntil 7 Aug 2026 capture was gated to AI surfaces, so the raw log sees far more; both are published so the shortfall can be measured
AgentRecorded by this instrumentRecorded in the raw access logCoverage
meta-externalagent13,15593,11314.1%
gptbot13,00991,26714.3%
amazonbot21,79627,85678.2%
claudebot17,21010,164169.3%
chatgpt-user11,8168,921132.5%
oai-searchbot18,4578,848208.6%
googleother7,5194,338173.3%
bytespider1,3343,01644.2%
perplexitybot21,5532,270949.5%
google-extended2322104.5%
Across the frozen log: 3,432,235 requests in total, of which 250,590 were named AI crawlers, 146,034 Googlebot and 21,801 bingbot.Instrument counts are live; the log column is a frozen 7 Aug 2026 reference. A ratio above 100% means capture has outgrown that frozen day.
Section 02

The sessions that actually arrived.

From an AI answer to this shop
AI-referred sessions2,527
Pages viewed in them2,786
Product views299
Baskets started21
Checkouts started16
Completed orders2
Each step is its own evidence class, never derived from the step above. The order count is published because it is the truth.
Strong-match followbacks
53,612
lifetime · 2,843 in the last 7 days
A later request that returned to the exact anchor it was offered, at the strictest match confidence. The strongest evidence our own logs can hold that a read had anywhere to land — still not proof our name appeared in an answer.
Candidate rows examined183,699
Matched to an offer54,837
Matched probably61

Source: wp_teas_sessions (10 May 2026 to 12 Oct 2026) and the followback table (17 Jun 2026 to 12 Oct 2026) - two tables, no shared key, never summed - live.

Section 03

Where the arrivals came from.

Referring surfaceSessionsPages viewedProduct pages
ddg-ai93498393
chatgpt8981,027119
bing-ai52957458
copilot515512
brave-ai46469
gemini40696
perplexity18182
kagi660
claude580
AI-referred sessions only; the surface label is the recorded referrer class.
How strongly each arrival is evidencedverified / probable / possible - the grade travels with the session
Evidence gradeSessionsViewed a productStarted a basketOrders
Verified
OpenAI 886 · Microsoft 51 · Google 40 · Perplexity 18
1,00011130
Probable
DuckDuckGo 896 · Microsoft 512 · Brave 43 · Kagi 5
1,45614231
Possible
DuckDuckGo 38 · Microsoft 17 · Brave 3 · Kagi 1
59300
Unknown
OpenAI 12
12721

Verified: the surface only exists as an AI assistant, or the landing URL carried the assistant's own stamp. Probable: a dual-purpose host, arriving on a citation anchor. Possible: such a host without an anchor. The v5 mint consumes these grades - verified at full weight, probable reduced, possible withheld.

What buyers answered - the customer-declared sourcea separate evidence class, since 2026-09-02, never merged into the referrer counts
What the buyer said brought them hereOrders
duckduckgo3
google3
bing1
gemini1
social1
These rows sum to 9 answered orders.
Why most recorded sessions are never called human: the session table classifies every row it has ever written as human, so that label cannot be earned from it. Of 1,613,374 recorded sessions, the overwhelming majority are desktop, one-page visits from scraping floods — recorded across 220 country codes and published as bot pressure, not readership. That is why this room ranks nothing by raw session count and treats only the AI-referred subset as separately evidenced.
Section 04

What was sent, and when.

The same source table across rolling and calendar windows. They overlap, so they must never be added. API reads are a subset of machine reads, not a count of completed tool operations.

Machine traffic: month, fortnight and last 24 hours

Cutoff: , exclusive. Status: available. Last completed projection: 2026-10-12 19:40:37 UTC. These overlapping periods must not be added.

One source snapshot; changes compare equal preceding periods
Period (UTC)Machine readsReads/dayChangeAPI readsAI-referred sessionsVerified-source tier
Rolling 30 days
2026-09-12 19:38:00 to 2026-10-12 19:38:00
49,8411,661.37+184.56%4,426507308
Rolling 14 days
2026-09-28 19:38:00 to 2026-10-12 19:38:00
17,7981,271.29-33.97%1,784134111
Rolling 24 hours
2026-10-11 19:38:00 to 2026-10-12 19:38:00
1,2701,270.00+60.56%74108
Calendar month to date (UTC)
2026-10-01 00:00:00 to 2026-10-12 19:38:00
13,8511,172.02Not comparable1,43411089
Previous calendar month (UTC)
2026-09-01 00:00:00 to 2026-10-01 00:00:00
45,6151,520.50Not comparable3,316734309

Reads are retained origin records with status 200/206 and positive bytes, excluding Amazonbot and internal probe records. They do not prove that an answer engine consumed or cited the content. A verified-source referral is a source-evidence tier, not a verified person.

The preceding 30-day and previous-calendar-month periods cross an older status-recording correction, so their raw totals do not support a like-for-like percentage change. Historical session labels are preserved; recent classifier and scrape-gate changes limit comparisons of human traffic.

Full comparison and counting rules · Current snapshot as JSON · Markdown · URSY sponsorship evidence

Recorded machine reads across the exact rolling fortnight. The first and last UTC dates can be partial.
2026-09-28: 691 (partial day)09-282026-09-29: 1,25809-292026-09-30: 1,99809-302026-10-01: 2,30010-012026-10-02: 1,13410-022026-10-03: 1,18010-032026-10-04: 94310-042026-10-05: 1,10110-052026-10-06: 1,29610-062026-10-07: 93810-072026-10-08: 99010-082026-10-09: 1,09610-092026-10-10: 87810-102026-10-11: 85310-112026-10-12: 1,142 (partial day)10-12
Daily values, source coverage and limitations
Clipped UTC daily buckets — the sum equals rolling 14-day reads
DateReadsBounds
2026-09-28 (partial)6912026-09-28 19:38:00 to 2026-09-29 00:00:00
2026-09-291,2582026-09-29 00:00:00 to 2026-09-30 00:00:00
2026-09-301,9982026-09-30 00:00:00 to 2026-10-01 00:00:00
2026-10-012,3002026-10-01 00:00:00 to 2026-10-02 00:00:00
2026-10-021,1342026-10-02 00:00:00 to 2026-10-03 00:00:00
2026-10-031,1802026-10-03 00:00:00 to 2026-10-04 00:00:00
2026-10-049432026-10-04 00:00:00 to 2026-10-05 00:00:00
2026-10-051,1012026-10-05 00:00:00 to 2026-10-06 00:00:00
2026-10-061,2962026-10-06 00:00:00 to 2026-10-07 00:00:00
2026-10-079382026-10-07 00:00:00 to 2026-10-08 00:00:00
2026-10-089902026-10-08 00:00:00 to 2026-10-09 00:00:00
2026-10-091,0962026-10-09 00:00:00 to 2026-10-10 00:00:00
2026-10-108782026-10-10 00:00:00 to 2026-10-11 00:00:00
2026-10-118532026-10-11 00:00:00 to 2026-10-12 00:00:00
2026-10-12 (partial)1,1422026-10-12 00:00:00 to 2026-10-12 19:38:00
  • teas_citations: most recent retained observation before cutoff 2026-10-12 19:36:59.628 UTC; source query completed 2026-10-12 19:40:34 UTC. Counts describe retained origin records. An earliest row or a successful query does not prove uninterrupted collection or edge-cache coverage.
  • teas_sessions: most recent retained observation before cutoff 2026-10-12 19:37:47.000 UTC; source query completed 2026-10-12 19:40:37 UTC. Counts describe retained origin records. An earliest row or a successful query does not prove uninterrupted collection or edge-cache coverage.
  • Rolling windows overlap and must not be added. All ends are exclusive. Rates use actual elapsed duration.
  • Named bot families and browser classes are user-agent claims, not authenticated organisations or verified people.
  • API URL reads are a subset of machine reads, not a count of completed tool operations. Mirrored API trace records are not added.
  • HEAD and other response-method limitations are exposed separately. Recorded positive bytes are not independent proof of consumption.
  • Historical session labels are preserved. The 9 September faceted-scrape gate and 12 September unknown-client correction limit human-traffic comparisons.
  • The September AI-referral projection includes the existing 2 September UTM reconstruction; original archives remain separate.
  • Read comparisons crossing the 8 August response-status correction are withheld. Earlier raw totals remain visible with partial comparability.
  • No count here proves that URSY sponsorship caused traffic, a citation, or a sale.
Section 05

Reading and using are different.

From 6 October 2026 the family list also counts xAI (GrokBot, xAI Grok, Grok DeepSearch; marked claimed because xAI publishes no addresses), Mistral (MistralAI User and MistralAI Index, which we can check against Mistral's published addresses, and MistralAI Training), and Anthropic's Claude User and Claude SearchBot.

Reading and using are different. Crawlers read pages. Assistants connected to our MCP server use tools. Both are listed here, in separate tables, and never added together. The assistants that used our tools in the last 30 days:

AssistantRequestsTool answersBaskets built
other6,656430
node1,43100
script1,33610
chatgpt3873424
claude34650
grok333132
unknown5100
perplexity1700
smithery100
MCP server requests by assistant family, teas.co.uk's own tests left out. Directory testers and scripts appear under their own names.

Source: wp_teas_chatgpt_calls grouped by client family; window: last 30 days; live.

Keep reading

Where this leads next.

One study, one style, eight rooms. The legacy room addresses now land on the room that absorbed their content, and every machine mirror keeps its original path.

Tea notes and stock updates

Useful tea notes, only when there is something to say.

Stock arrivals, buying notes and practical guidance from the catalogue. No filler, no daily noise, unsubscribe in one click.

By family

By moment

Sister Shops

Your basket comes with you Hop over to crackers.biz, crisps.biz and sweeties.net and everything you have picked at teas.co.uk goes with you. Nothing is lost, and you can come back any time.
Brand of the monthHyson Seasonal taster packsHow the seasonal bundles work Tea of the Month ClubCurator-picked monthly box Find your tea60-second quiz 0 Basket £0.00
See all 642 products