{
  "entries": [
    {
      "slug": "headless-economy",
      "title": "The Headless Economy",
      "description": "Definition and thesis of the headless economy — the emerging market where agents discover, evaluate, access, pay for, and consume digital goods and services through machine-native interfaces.",
      "section": "foundations",
      "order": 1,
      "url": "/knowledge-base/headless-economy/",
      "content": "## What is the headless economy?\n\nThe headless economy is the emerging market in which agents discover, evaluate, access, pay for, and consume digital goods and services through machine-native interfaces.\n\nIt is the shift from human-interface-first software and commerce toward machine-native products, services, and markets. In this economy, the primary path to usage does not run through screens, clicks, and dashboards. It runs through APIs, CLIs, SDKs, MCP servers, structured feeds, machine-readable documents, agent protocols, and other programmable surfaces.\n\n## What does \"headless\" mean?\n\nHeadless describes a product, service, or business whose primary operating surface is machine-native rather than human-interface-native.\n\nA headless product can be:\n\n- **Discovered** by software\n- **Evaluated** by software\n- **Accessed** by software\n- **Consumed** by software\n- **Monitored** by software\n- **Paid for or provisioned** by software\n\nHeadless does not mean \"no GUI\" in an absolute sense. Headless means \"the GUI is not the primary consumption layer.\"\n\n## Core claims\n\n1. A growing share of software usage will originate from agents rather than directly from humans.\n2. Products designed for machine consumption will require different interfaces, economics, and distribution models than products designed primarily for human navigation.\n3. New businesses will be built specifically for agent demand.\n4. Existing GUI-first businesses will increasingly reconfigure themselves to work as headless businesses in parallel.\n5. The most important market shifts will occur in discovery, selection, access, pricing, trust, retention, and interoperability.\n\n## Central market question\n\nWhat kinds of products, businesses, and market structures emerge when agents become meaningful customers and consumers of digital goods and services?"
    },
    {
      "slug": "taxonomy-of-consumption",
      "title": "Taxonomy of Agent Consumption",
      "description": "Three models of how agents consume goods and services: as principal consumers, as procurement layers, and in hybrid consumption patterns.",
      "section": "foundations",
      "order": 2,
      "url": "/knowledge-base/taxonomy-of-consumption/",
      "content": "## How agents consume\n\nNot all agent consumption looks the same. There are three distinct patterns through which agents participate in the headless economy.\n\n## 1. Agent as principal consumer\n\nThe agent directly consumes the capability or output as part of its own workflow.\n\n**Examples:**\n- An agent calls an OCR API\n- An agent invokes a ranking model\n- An agent uses a CLI tool or MCP server\n- An agent reads structured documentation\n- An agent queries a proprietary dataset\n- An agent consumes a free or paid search endpoint\n\nThis is the clearest and most direct form of headless consumption.\n\n## 2. Agent as procurement layer\n\nThe agent acquires a good or service on behalf of a human or organization, but is not the ultimate consumer of that good.\n\n**Examples:**\n- An agent purchases software seats for a company\n- An agent buys physical goods for a household\n- An agent handles delegated spending for a human principal\n\nThis includes much of agentic commerce. It is part of the headless economy, but not its entire scope.\n\n## 3. Hybrid consumption\n\nThe agent consumes intermediate goods or capabilities in order to generate an output for a human or another system.\n\n**Examples:**\n- An agent accesses filings, articles, and data to produce a briefing\n- An agent combines free and paid tools to complete a research workflow\n- An agent consumes compute, models, and documents to produce a work product\n\nThis is likely the most common real-world pattern. It connects direct machine consumption with human benefit."
    },
    {
      "slug": "headless-customer-funnel",
      "title": "The Headless Customer Funnel",
      "description": "A framework for analyzing headless businesses through the machine-consumption funnel: discovery, selection, access, ongoing consumption, and LTV.",
      "section": "frameworks",
      "order": 3,
      "url": "/knowledge-base/headless-customer-funnel/",
      "content": "## The machine-consumption funnel\n\nA useful framework for analyzing headless businesses is the machine-consumption funnel. Each stage describes how agent-driven usage differs from human-driven usage.\n\n## Discovery\n\nHow an agent becomes aware of a capability.\n\n- Registries\n- Search\n- Marketplaces\n- Embeddings\n- Recommendations\n- Protocol directories\n- Documentation hubs\n\n## Selection\n\nHow an agent determines whether a capability is fit for purpose.\n\nDecision variables may include:\n- Task fit\n- Price\n- Latency\n- Quality\n- Trust\n- Authorization requirements\n- Output format\n- Rate limits\n- Uptime\n- Policy constraints\n\n## Access and purchase\n\nHow the agent obtains the right to use the capability.\n\n- Open access\n- Token-based auth\n- Delegated auth\n- Enterprise provisioning\n- Subscription\n- Metered payment\n- On-demand settlement\n\n## Ongoing consumption\n\nHow repeated use happens over time.\n\n- Reliability\n- Quality consistency\n- Integration depth\n- Observability\n- Billing clarity\n- Memory and state retention\n- Ecosystem compatibility\n- Workflow dependence\n\n## LTV in the age of agents\n\nFor headless businesses, long-term value may be shaped by:\n\n- Repeated invocation\n- Incorporation into automated workflows\n- Low failure rates\n- Structured outputs\n- Strong documentation\n- Predictable billing\n- Accumulated context\n- Switching friction at the workflow level rather than the interface level"
    },
    {
      "slug": "machine-native-goods",
      "title": "Machine-Native Goods",
      "description": "The types of digital goods and services that agents consume in the headless economy, and the access models through which they are provisioned.",
      "section": "foundations",
      "order": 4,
      "url": "/knowledge-base/machine-native-goods/",
      "content": "## What agents consume\n\nThe headless economy includes a wide range of goods consumed by software rather than navigated by humans.\n\n### Capabilities and tools\n- APIs\n- CLI tools\n- SDKs\n- MCP-accessible capabilities\n- Workflow primitives\n\n### Data and knowledge\n- Datasets\n- Search and retrieval endpoints\n- Content\n- Documents\n- Facts\n- Structured knowledge\n\n### Infrastructure\n- Model inference\n- Ranking and classification services\n- Authentication and identity services\n- Memory and state services\n- Storage and hosting\n- Observability and monitoring\n- Compute\n\n### Commerce\n- Payment and settlement rails\n\n## Access models\n\nMachine-native goods may be accessed through:\n\n- **Free access** — no cost, no authentication\n- **Open source** — freely available code and tools\n- **Public web access** — publicly available data and content\n- **Freemium** — basic access free, premium features paid\n- **Quota-based usage** — limited free tier, paid beyond limits\n- **Subscription** — recurring payment for access\n- **Per-call pricing** — pay per API invocation\n- **Per-task pricing** — pay per completed task\n- **Per-result pricing** — pay per successful outcome\n- **Enterprise provisioning** — negotiated access and SLAs\n- **Internal/private deployment** — self-hosted or on-premise\n- **Sponsored or subsidized access** — third-party funded\n- **Protocol-mediated settlement** — programmatic payment rails"
    },
    {
      "slug": "product-design-for-agents",
      "title": "Product Design for Agents",
      "description": "What products serving the headless economy require: machine-readable discovery, structured interfaces, strong error semantics, and more.",
      "section": "frameworks",
      "order": 5,
      "url": "/knowledge-base/product-design-for-agents/",
      "content": "## Designing for machine consumers\n\nProducts serving the headless economy must be built with agent consumption as a primary use case, not an afterthought. The requirements differ fundamentally from human-centered product design.\n\n## Requirements\n\n### Discoverability\n- **Machine-readable discovery** — agents need to find capabilities through structured registries, documentation, and protocol directories, not marketing pages\n- **Clear capability descriptions** — what the product does, expressed in terms agents can parse and evaluate\n- **Structured documentation** — not just human-readable docs, but machine-parseable specifications\n\n### Interface quality\n- **Stable interfaces** — breaking changes destroy automated workflows\n- **Predictable outputs** — agents need to parse responses reliably\n- **Strong error semantics** — clear, structured error messages that agents can act on programmatically\n- **Low latency** — agents operate at machine speed; human-acceptable response times may be too slow for agent workflows\n\n### Access and control\n- **Low-friction authentication** — complex OAuth flows designed for humans create barriers for agents\n- **Explicit permissioning** — agents need clear, granular permission models\n- **Revocability** — the ability to revoke agent access cleanly\n\n### Operations\n- **Observability** — visibility into how agents are using the product\n- **Usage transparency** — clear metering and reporting\n- **Policy compatibility** — alignment with organizational policies governing agent behavior\n- **Interoperability** — ability to work alongside other tools and systems in agent workflows"
    },
    {
      "slug": "economics",
      "title": "Economics of the Headless Economy",
      "description": "How the headless economy changes software economics: from seat-based to invocation-based pricing, workflow-level switching costs, and machine-driven retention.",
      "section": "frameworks",
      "order": 6,
      "url": "/knowledge-base/economics/",
      "content": "## How software economics change\n\nThe headless economy transforms several fundamental assumptions about how software businesses generate and capture value.\n\n## Pricing shifts\n\n- **Seat-based to invocation-based** — when the user is an agent, per-seat pricing loses meaning; usage shifts to per-call, per-task, or per-result models\n- **Free access as infrastructure** — free tiers serve as discovery and adoption mechanisms in a world where agents evaluate and select tools programmatically\n- **Bundled and subsidized models** — some capabilities may be sponsored or subsidized to attract agent traffic and workflow integration\n\n## Retention mechanics\n\n- **Workflow embedment over interface habit** — retention depends less on users returning to a familiar dashboard and more on the product being embedded in automated workflows\n- **Switching costs at the workflow level** — friction comes from reliability, accumulated context, integration depth, policy fit, and state — not from learning a new UI\n- **Machine-driven repeat consumption** — long-term value depends on repeated machine invocation rather than repeated human logins\n\n## Value capture\n\n- Value may be captured per call, per task, per result, or per workflow\n- The unit of engagement becomes the API call or tool invocation, not the session or page view\n- Products that become embedded in high-frequency automated workflows capture compounding value\n- Products with strong structured outputs, predictable billing, and low failure rates build durable agent relationships\n\n## Editorial position\n\ngetheadless studies the headless economy from a market perspective. Our primary interests:\n\n- What is being built\n- Who is building it\n- Who is adapting to it\n- How agents consume it\n- How businesses monetize it\n- How distribution works\n- Where trust and control sit\n- Which categories are emerging\n- Which business models appear durable"
    }
  ]
}