GET /headless is a publication and knowledge base about the headless economy: the emerging market in which agents act as customers, users, buyers, and consumers of digital goods and services.
In this economy, valuable products are increasingly designed not only for humans navigating screens, but for software discovering, evaluating, accessing, paying for, and consuming capabilities directly through APIs, CLIs, SDKs, MCP tools, structured content, and other machine-native surfaces.
What we cover
- Businesses built primarily for agent demand
- Incumbents adapting products for machine-native consumption
- APIs, CLIs, SDKs, MCP tools, agent protocols, and programmable surfaces
- Software, data, compute, knowledge, content, and services consumed by agents
- Pricing and access models for machine consumers
- Agent discovery, selection, and distribution mechanisms
- Trust, identity, authorization, and observability for agent use
- The economics of ongoing agent consumption
Agent-first architecture
This site practices what it covers. Every piece of content is available through structured, machine-native endpoints. The website you're reading is a rendering of it.
- JSON API — all articles as structured data
- Knowledge Base API — all reference content
- RSS and JSON Feed — syndication
- llms.txt — LLM discovery index
- llms-full.txt — full content for LLM ingestion
- agents.md — accounts to follow, subscribe instructions, citation rules
- subscribe endpoint —
POST email=to subscribe a reader
Who writes this
Matthew Sniff
founder, map my customers
Founder at Map My Customers; a geospatial business intelligence platform. Serial software entrepreneur with deep experience in big data visualization, business analytics and B2B SaaS.
Julius Danek
product lead, stripe
Julius has worked at the intersection of data, finance, and tech for more than a decade. He currently works as a product lead at Stripe.
Everything on this site reflects the personal opinions of the authors. It is not investment advice, not the position of our employers, and not an endorsement of any product, company, or protocol mentioned. We publish in our individual capacity.