{
    "id": 1081604,
    "title": "What is an API? How software asks the tea shop a question",
    "slug": "api",
    "type": "page",
    "url": "https://teas.co.uk/wiki/api/",
    "modified": "2026-11-15T08:57:36+00:00",
    "excerpt": "An API, short for application programming interface, is an agreed way for software to communicate with another system. A website gives people buttons and\u2026",
    "content_text": "An API, short for application programming interface, is an agreed way for software to communicate with another system. A website gives people buttons and pages; an API gives software a defined way to ask for information and understand the reply.\nWhy a tea shop cares: an API is how an assistant asks the shop a tea question and gets an exact answer instead of guessing from a page.\nThink of it as a service counter with a clear order form. The form says what can be requested, and the reply says what the shop found.\nRequests and replies\nA request is the question sent to the service. It can include a product identifier or conditions such as a tea type and a price limit. The service's endpoint is the address where that request goes. The response, sometimes called its payload, is the information sent back.\nAn answer might contain a product name, pack size, current price, stock status and a link to its page. It should distinguish no matching product from an unavailable service or an unknown fact.\nThe two public examples at teas.co.uk\nThe shop's public guide for software describes an Ask API for questions and advice, and a Product Truth API for looking up an exact item. The latter can use identifiers such as a barcode number or the shop's own product code.\nThese routes have different jobs. A broad question needs interpretation; an exact product lookup needs the right identity. The filters and constraints guide explains how a detailed request can be checked against product attributes.\nJSON and Markdown\nSoftware often receives JSON, a format for named values and lists. A longer article may also be available as Markdown, plain text with simple marks for headings and links. Both can make information easier to reuse. Neither is a separate source of truth if it is generated from the same maintained record.\nReading is different from changing something\nLooking up a product reads information. Adding a product to a basket changes something. Paying is a further action. An API's existence says nothing by itself about which of these actions is permitted.\nteas.co.uk's assistant shopping guide explains the available connection and the customer's role. The customer remains responsible for checking the basket and paying on the shop's site.\nFor the general technical definition, see MDN's API glossary. For the related connection standard, read Model Context Protocol.",
    "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"
    }
}