{
    "id": 1083395,
    "title": "Multimodal and agentic commerce: how you ask, and what an assistant may do",
    "slug": "multimodal-and-agentic-commerce",
    "type": "page",
    "url": "https://teas.co.uk/wiki/multimodal-and-agentic-commerce/",
    "modified": "2026-11-15T08:57:43+00:00",
    "excerpt": "The two words often appear together in articles about AI shopping, which makes them sound like one thing. They are two different axes, and keeping them\u2026",
    "content_text": "In short: Multimodal describes how a request comes in: typed, spoken or as a photograph. Agentic describes software taking an action it has been allowed to take. They are separate questions. At teas.co.uk an assistant can, with the customer's approval, search, compare and fill a basket; the customer always checks the basket and pays on teas.co.uk.\nWhy a tea shop cares: people may ask for tea by voice or with a photograph and let an assistant fill the basket, so the shop has to be ready for both.\nThe two words often appear together in articles about AI shopping, which makes them sound like one thing. They are two different axes, and keeping them apart makes it much easier to see what an assistant can and cannot do.\nMultimodal: the way the request arrives\nA request can be typed, spoken or shown. Someone might type \"decaf green tea, fruity\", say the same thing to a speaker, or hold up a photograph of a box they have run out of. The way it arrives changes nothing about what is true of the tea.\nA photograph needs particular care. An assistant may recognise a box from a picture, but brands sell the same name in several sizes and versions. Pack-specific facts, such as the number of bags, the price per cup or the caffeine status, should come only after the exact product is confirmed, by its barcode or by the name and size printed on the pack. Until then, the honest answer is \"this looks like X; can you confirm the size?\"\nAgentic: what the software is allowed to do\nAn agentic assistant does something rather than only answering: searches a catalogue, adds an item to a basket, or, in some systems, completes a purchase. What matters is permission, not the way the request arrived. A spoken request and a typed one carry the same limits.\nWhat is live at teas.co.uk\n\nStepStatus\nAn assistant reads the shop's product factsBuilt\nAn assistant searches and compares teas through the shop's MCP serverBuilt, since 6 October 2026\nAn assistant fills a basket, with the customer's approvalBuilt, since 6 October 2026\nThe customer checks the basket and paysAlways on teas.co.uk; the assistant never sees card details and cannot place the order\nAn assistant acting for a customer within limits the customer setsPlanned (version five), not built\nBooking across several businesses in one planProposed, not built\n\nHow the basket hand-over works is set out in Shop teas.co.uk from your AI assistant.\nA tea example\nSomeone photographs an empty box of fruity green tea and says, \"Get me another, but decaf this time.\" The input is a photo and a voice. The assistant should first confirm which box it is, then notice the condition: the original contains caffeine, so the same box is not the answer. It can then suggest a decaffeinated green tea, explain the trade-off, and, if the person agrees, fill a basket. The person checks it and pays. Nothing in that sequence needs the assistant to hold their money.\nWhat it is not\n\nNot certainty from a picture. Recognising a box is a guess until the exact product is confirmed.\nNot autonomous payment. At teas.co.uk payment always stays with the customer.\nNot a claim that every assistant connects in the same way. The teas.co.uk in AI assistants page lists the current routes.\n\nQuick reference\n\nDetailInformation\nMultimodalHow a request arrives: text, voice, image\nAgenticSoftware taking an action it has permission to take\nLive at teas.co.ukSearch, compare and fill a basket with the customer's approval; customer pays on teas.co.uk\nPlannedBounded action within customer-set limits (version five)\nProposedCross-business booking\n\nRelated\n\nModel Context Protocol\nBuilt versus planned\nProduct identifiers\nPremium Intent\nLee Samuel Tucker's builder vocabulary",
    "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"
    }
}