ursy.markets · TODAY (UTC)
Machine attention.
Evidence at every step.
Runtime 1.0.0 · Operational · Updated
These figures come from the same store as the public JSON report. Machine requests, emitted sponsorship and centrally verified exposures are distinct measurements.
Sponsor eligible
334Sponsor selected
286Injection attempted
286Sponsor emitted locally
199Local VME candidates
0Verified machine exposures
0Awaiting verification
0Public origin activity: exact rolling periods
New measurement began 2026-09-12T03:27:51Z. Unknown callers stay separate from classified machines. Earlier mixed-origin counters below retain their legacy definition.
| Period | Classified requests | Unknown | Emitted locally | Previous classified | Coverage |
|---|---|---|---|---|---|
24hUTC bounds2026-09-12T22:53:00Z ≤ time < 2026-09-13T22:53:00Z | 22 | 280 | 211 | 38 | partial |
14dUTC bounds2026-08-30T22:53:00Z ≤ time < 2026-09-13T22:53:00Z | 60 | 519 | 409 | Unavailable | partial |
30dUTC bounds2026-08-14T22:53:00Z ≤ time < 2026-09-13T22:53:00Z | 60 | 519 | 409 | Unavailable | partial |
No conversion rate or percentage change is inferred from partial coverage. Exact windows as JSON ↗
AD campaign reconciliation
teas-ursy-2026-09-v1 · Cutoff 2026-09-13T22:44:00Z. Current cached report. Accepted emissions are separate from local candidates and from TEAS arrivals.
| Period | Qualifying accepted | Previous accepted | Original ledger | Audit exclusions | Coverage |
|---|---|---|---|---|---|
| 24h | 0 | 0 | 0 | 0 | continuity_unverified |
| 14d | 0 | 0 | 0 | 0 | partial |
| 30d | 0 | 0 | 0 | 0 | partial |
Verification and delivery
Central collector: connected. A local candidate becomes a verified machine exposure only after URSY.AD accepts it. Missing central totals remain unavailable.
- Pending outbox events
- 0
- Dead-letter events
- 0
- Oldest pending event, seconds
- Unavailable
- Last central reconciliation
- 2026-09-13T22:55:53Z
History
7-day machine requests: 1,793 · 30-day: 1,793. Measurement began 2026-09-12T00:01:52Z. Earlier estate traffic is not relabelled as VME.
| Date (UTC) | Machine requests | Local emission | Candidates |
|---|---|---|---|
| 2026-09-12 | 807 | 216 | 0 |
| 2026-09-13 | 986 | 199 | 0 |
Observed machine families and surfaces
Classification describes caller claims and request characteristics. It does not verify a company identity or establish that an AI read or recommended anything.
Machine families
- unknown
- 831
- generic
- 64
- openai
- 24
- anthropic
- 67
Response surfaces
- agents json
- 97
- rest json
- 127
- machine html
- 208
- machine manifest
- 141
- openapi
- 100
- mcp tool
- 262
- nicola
- 1
- llms txt
- 50
Active sponsorship
teas.co.uk · Campaign teas-ursy-2026-09-v1 · Creative teas-ursy-2026-09-v1:default
Paid placement. Sponsorship does not alter the requested data, ranking, rights decision or tool result.
What these measurements mean
- Machine families reflect User-Agent claims, not verified provider identity.
- Cached responses bypassing this application have no application VME proof.
- VME proves centrally accepted sponsor emission, not reading, recommendation, citation, click or sale.
- Pre-runtime request counts are not retroactively relabelled as VME.
- Human audience analytics remain with the consent-based estate runtime. This module does not count human visits.
- Production GET emission is withheld from VME until the original client method can be proved through the CDN. Older GET candidates are quarantined; local emission counts remain historical facts. All accepted VME is non-billable.
Each response is measured once. Payment records, signed evidence, account pages, health checks, dashboard polling and synthetic tests are excluded. No prompt, request body, account identity, cookie, raw IP or full user-agent is stored by this measurement module.