{
    "id": 1079458,
    "title": "The complete payload: everything a tea shop hands an AI assistant in one answer",
    "slug": "complete-payload",
    "type": "page",
    "url": "https://teas.co.uk/ai/complete-payload/",
    "modified": "2026-11-20T13:08:18+00:00",
    "excerpt": "The complete payload is Lee Samuel Tucker's name for the full, structured answer a business hands an AI assistant in a single trip: what the product is, what it costs, whether it is in stock, the proof behind each claim, its limits, and the route to buy it.",
    "content_text": "The complete payload is my name for the full, structured answer a business hands an AI assistant in a single trip: what the product is, what it costs, whether it is in stock, the proof behind each claim, its limits, and the route to buy it. I group it into four parts: product truth, claim boundaries, a citation graph and an action layer.\nWhen an assistant asks about a tea, the shop that answers in one go, with the price, the stock, the proof and the route to buy, is the easiest one to recommend.\nOrdinary pages make an assistant take many separate trips, and every trip is a chance for the facts to disagree. The complete payload turns those dozen trips into one answer: what the tea is, what it costs, whether it is in stock, the proof, its limits and the way to buy it.\nThe complete payload is the practical side of a truth entity. I use the term to describe the difference between an assistant having to piece together an answer from a page made for human eyes and an assistant being handed a prepared, checkable answer by the business itself. At teas.co.uk, the independent tea shop I run from Tunbridge Wells, it is the reason products carry structured data behind their ordinary pages.\nFirst, what is a payload?\nA payload is the useful information carried in a software response. For a tea-shop question, it might include the matching products, their pack sizes, prices, caffeine status and links. It is the contents of the reply, rather than the envelope used to deliver it.\nMy phrase \u201cthe complete payload\u201d describes the aim of returning the information needed for a decision together. It does not mean every product record contains every possible fact, or that every question can always be answered in one request.\nFour parts in ordinary language\n\nTerm\nWhat it means for a shopper\n\nProduct truth\nThe recorded facts about the exact item: which tea, which pack, price and availability.\n\nClaim boundaries\nWhat can honestly be said about it, including limitations and unknowns.\n\nCitation graph\nThe links between statements and the evidence supporting them.\n\nAction layer\nThe permitted next steps, such as opening the product page or building a basket when asked.\n\nAn API can return this information as JSON, text organised into named values and lists. A longer explanation can also be supplied as Markdown, a plain-text format with headings and links. The formats should preserve the relevant facts and limits from their authoritative source.\nA tea example: fewer trips, one agreed record\nImagine someone asks an assistant for a strong loose-leaf breakfast tea, no bags, under ten pounds. Working from ordinary web pages, the assistant has to make many separate trips: one for the page, one for the price, one for the picture, another to find a checkout link, with every trip a chance for one fact to disagree with another. It may end up with a low-confidence guess and no source.\nAs I put it: \u201cThe complete payload turns those dozen trips into one.\u201d Where the question allows, the assistant can ask once and get the product, its price and stock, the facts it needs to judge the request, the sources behind those facts and a link to buy, all drawn from the same record the shop\u2019s own page uses.\nThe more a customer says, the more this matters. A full request of the kind I call Premium Intent, with its context, constraints and budget, can only be met if every fact it depends on comes back together and agrees.\nThe scenario is illustrative. The structure behind it is what the shop is built around.\nThe four parts\n\nProduct truth. Exact names, values with their units, the price and the stock position.\nClaim boundaries. What a product is, what it is based on, and what it should not be bought for.\nCitation graph. Each claim linked to the supplier document or other source behind it, so a reader can check it.\nAction layer. The checkout link and the rules that say where everything resolves, ready for an assistant to act on with the customer\u2019s permission.\n\nMy longer description adds context around those four: the brand, relevant Tea Wiki and recipe pages, the main product image and its records, related products, and a short way for the assistant to report whether the route worked.\nWhat is built today\nBuilt and live: every product on teas.co.uk has structured data behind its page, including identifiers, prices, availability, source links and price per cup, all read from one checked set of product facts introduced with version two on 10 May 2026. Source links and other details appear where the record holds them, and missing ones are marked as gaps. Since 6 October 2026, an assistant can, with the customer\u2019s approval, search, compare and fill a basket through the teas.co.uk MCP server, the shop\u2019s connection for assistants built on the open Model Context Protocol. The customer checks the basket and pays on teas.co.uk, and the assistant never sees their card details.\nThe extra fields in my longer description are the full design. Not every one is returned for every product on the live site yet, so the list above describes the aim rather than a promise about any single product.\nA useful answer can still have gaps\nA dated check of the Tetley Decaf Pure Green record on 15 November 2026 returned its identity, decaffeinated status and related resources, while marking the response as usable with known gaps. Some attributes were unclaimed or needed a pack check. The honest answer includes those limits instead of pretending \u201ccomplete\u201d means flawless.\nFetching several pages is not inherently wrong, and a normal product page can already include several facts. Bringing relevant facts together can reduce extra requests; the exact number depends on the question and the available service. Checkout and stock should still be checked at the point of purchase.\nWhat the complete payload is not\nIt is not a scrape of a web page, and it is not marketing copy in a different format. It does not hand over payment: the customer pays on the shop\u2019s own checkout. It does not oblige an assistant to use it or to cite the shop.\nI am open about a risk here. The companies running assistants could take a clean answer and serve it inside their own walls, without ever sending the customer or the credit back. My answer is that live stock, the checkout and the shop\u2019s accountability for its own claims stay with the shop, and that clean outside sources are cheaper for an assistant than building everything itself, so it still has reasons to route the customer there. That is an argument, not a result. The shop\u2019s Under the Hood pages publish what it can and cannot see of that journey.\nWhere the term comes from\nThe idea came from my work rebuilding teas.co.uk in 2026. I started calling it the complete payload in June 2026 to describe what the rebuilt shop should hand an assistant when it asks about a product, and to name the gap between an answer pieced together from pages and an answer the business prepares itself. I don\u2019t know whether anyone has used the name before, but it suits what I have built.\nQuick reference\n\nDetail\nInformation\n\nTerm\nThe complete payload\n\nMeaning\nA full, structured, sourced answer about a product, brought together so an assistant needs as few trips as possible\n\nUsed by\nLee Samuel Tucker, founder of teas.co.uk\n\nUsed at teas.co.uk since\nJune 2026\n\nOpposite or contrast\nAn assistant scraping a page made for human eyes and guessing\n\nRelated\nTruth entity, claim boundaries, Premium Intent, built versus planned\n\nWhat others have found\nOutside research and reporting on the wider subject. It is background: it does not test or prove my own terms.\nGoogle\u2019s guide to product structured data and the schema.org Product type describe the machine-readable facts, such as price and availability.",
    "contentSignals": "ai-train=yes, search=yes, ai-input=yes",
    "links": {
        "apiCatalog": "https://teas.co.uk/.well-known/api-catalog",
        "llmsTxt": "https://teas.co.uk/llms.txt",
        "mcp": "https://teas.co.uk/mcp",
        "mcpSetupGuides": "https://teas.co.uk/ai/",
        "mcpCard": "https://teas.co.uk/.well-known/mcp/server-card.json",
        "primaryAgenticRouteAuthority": "https://teas.co.uk/.well-known/teas-primary-agentic-route-authority.json"
    }
}