{
    "schema": "ursy.press/story/1",
    "generated_at": "2026-10-12T19:25:09+00:00",
    "id": "ursy-press-80",
    "url": "https://ursy.press/stories/teas-sponsorship-in-ursy-api-responses/",
    "story_json": "https://ursy.press/stories/teas-sponsorship-in-ursy-api-responses/story.json",
    "title": "Bringing sponsorship to the agentic web",
    "kind": "Company news",
    "official": true,
    "projects": [
        "URSY.ad",
        "URSY.dev"
    ],
    "byline": "URSY",
    "date_published": "2026-09-13T07:48:37+01:00",
    "date_modified": "2026-09-15T18:57:53+01:00",
    "standfirst": "A useful service can introduce the business supporting it. URSY is testing that familiar idea in a different setting: a clearly labelled TEAS.co.uk sponsor message delivered with a software response.",
    "source": "An example machine response",
    "reading_time_minutes": 2,
    "reading_order": 14,
    "sources": [
        {
            "title": "An example machine response",
            "url": "https://ursy.io/wp-json/nicola/v1/hello",
            "note": ""
        },
        {
            "title": "URSY.AD TEAS study",
            "url": "https://ursy.ad/machine-attention/study/teas/",
            "note": ""
        },
        {
            "title": "TEAS sponsor trail",
            "url": "https://teas.co.uk/under-the-hood/sponsor-trail/",
            "note": "Nine-arrival observation comes from the archived 12 September backup, not the current live total."
        }
    ],
    "made_by": "Written with AI assistance for URSY.press from the sources listed here.",
    "citation": "URSY (13 Sep 2026). \u201cBringing sponsorship to the agentic web.\u201d ursy.press/stories/teas-sponsorship-in-ursy-api-responses/",
    "bibtex": "@misc{ursy2026bringing-sponsorship,\n  author = {URSY},\n  title = {Bringing sponsorship to the agentic web},\n  howpublished = {\\url{https://ursy.press/stories/teas-sponsorship-in-ursy-api-responses/}},\n  year = {2026},\n  month = {sep},\n  note = {URSY.press}\n}",
    "content_text": "A sponsor usually hopes to be noticed by the person reading, watching or listening. URSY is exploring an earlier point in that journey: the moment software receives something useful on a person\u2019s behalf.\nOn 4 September 2026, eligible URSY responses began carrying a separately labelled introduction to TEAS.co.uk. The requested result comes first, with the sponsor message alongside it. The receiving software can read both.\nThe public URSY.io service response provides an example. Its trailing sponsor object names TEAS.co.uk, supplies a link and marks the placement as paid. The disclosure says it does not change the requested data, ranking, rights decision or tool result.\nThe receiving system can then decide what, if anything, to do with the message. A sponsor being delivered is the first step. It is not yet an appearance in an answer a person sees.\nFollowing the introduction\nThe measurement work is intended to follow what happens next. Did the sponsor material leave the service? Did somebody or something arrive at TEAS? Was there a later action that could be linked to it?\nThe first inspected records were mostly tests. Of nine tagged arrivals in the 12 September backup, eight were explicitly test traffic. The remaining browser arrival linked URSY.hosting with a Twinings Lemon and Ginger product page. At that point, the inspected records did not connect those arrivals to a later outcome.\nThat is an early piece of the trail, with the test traffic still labelled. The wider study continues on URSY.AD and TEAS\u2019s sponsor evidence page.\nThe commercial question is worth exploring. Useful services have to be supported somehow, and a relevant business may want to be discovered by the software using them. We want to see whether a clear, disclosed introduction can play a part without changing the answer someone asked for.\nFor a specialist business, the opportunity is an introduction made while another service is already being useful. Whether that introduction reaches a person and leads to trade is what the experiment needs to discover next."
}