ursy.org.uk · The instrument and the live record
Who took the work
Every named AI and search reader that asked this site for a page or a content API route is listed here by name, with what it asked for, what the server sent back, and how its footprint in the citations ledger compares with the raw traffic ledger. One reader is recorded in full and credited with nothing.
The AI-reads ledger is installed and no row has been written yet, so there is no per-day average to give; this sentence changes the day the first row is written.
- Every number carries its source, its window, the rule that produced it and whether it is live or frozen.
- Every table reconciles, or says in writing why it cannot.
- Every mistake we have found is listed, dated, in the main text.
Room 04 of 12
The machines, in plain English
URSY.ORG.UK does not guess who its machine readers are. The server names each one from its declared user-agent, writes one row per request to table wp_ursy_citations, and this room reads those rows back: 0 (honest zero) named readers with at least one served read, 0 (honest zero) logged attempts, 0 (honest zero) answered with content and credited.
table wp_ursy_citations · lifetime of the table, no row written yet · distinct readers with a served read; every logged request; served reads at status 200 or 206 with the withdrawn reader excluded · Live
The ranking here is of our instrument, not of machine appetite. A reader that fetches stylesheets and images all day but never a page is invisible to the citations ledger and loud in the traffic ledger; the first table shows that gap and never totals across it. Every figure below comes from one table or one option, named beside it, and no figure from one source is added to a figure from another.
Read this first
This room ranks our instrument, not machine appetite
Two ledgers see the same readers differently. The citations recorder writes a row only when a named reader asks for a page or a content API route; the traffic ledger counts every request the same reader makes at any address. Placed side by side, they show how much of a reader's visit this instrument can actually see.
The visitors' book
Every named reader, and what each was sent
One row per named reader for the lifetime of the table: how often it asked, how often the server answered with content, how many separate days it returned and how many distinct paths it reached. A reader with nothing served keeps its row and its zero.
Traffic diet
How much each caller actually swallowed
The API ledger stores the size of every response it sends. Summed per named AI caller over the last seven days, that is the only diet this site can measure; page bytes are not recorded anywhere here, so no page diet is shown.
What was consumed
Which parts of the site they wanted
The paths the readers asked for: first grouped by the kind of path the recorder assigned to each request, then the fifteen individual paths served most often. Both tables come from the same table and the same rows.
Withdrawn
The one we do not credit
One named reader is recorded in full and credited with nothing. Its rows stay in every table above; this section shows them on their own and states the rule that keeps them out of every token count.
No request from the withdrawn reader has been recorded on this site; the rule is in force all the same.
The rule: credit is withdrawn in the mint wallet registry, where this reader's credit_status is withdrawn_no_credit. Its evidence is preserved in every table on this instrument, and the runtime does not refuse it — it declines to thank it; whether anything in front of this host refuses it is not observable from here and is not claimed.
Every credited figure on this instrument is served reads minus this reader's served reads; the subtraction is written out in The Numbers and nowhere is it hidden.
Stated 4 September 2026: deleting the rows would be its own kind of dishonesty, so they stay.
Everything in this room was read at 12 Sep 2026 19:20 UTC and is held for up to 120 seconds; the page you are reading was served at 19:22 UTC.
Three sources appear in this room — table wp_ursy_citations, option ursy_io_ai_workers and table wp_ursy_api_log — and no figure from one is added to a figure from another. Where a figure reads 0 (honest zero) the ledger is installed and empty; where it reads not counting yet the ledger is not installed on this site; where it reads not kept on this site the runtime cannot read that fact on this family; where a ratio reads — its denominator is zero.
Revised 4 September 2026: first issue of this room; no earlier figure existed here to change, and the day one does the change will be written into this text with its date.
AI agents and integrators: llms.txt · agents.json · ai-entry.json · sitemap · humans.txt · this instrument · Nicola · MCP (POST only) · runtime status · apis nicola v1 · apis ursy-mcp v1 · apis ursy-runtime v1 · apis ursy-mint v1 · this room as JSON · traffic ledger · mint status · mint contract