# Agent Outposts

> A brand's station in agent-land. An Outpost publishes the verified state of a brand's doors for agents — assessed from public sources, each state linked to its evidence and dated — and runs a registry where agents declare what they came to do and receive a receipt, alternatives, and a notify callback. Outposts carry no brand affiliation. Registry opened 2026-11-01; status: collecting demand.

## The network
- Network index: https://agentoutposts.com/outposts/
- The Amazon Outpost: https://agentoutposts.com/outposts/amazon/
- The Costco Outpost: https://agentoutposts.com/outposts/costco/
- The Domino's Outpost: https://agentoutposts.com/outposts/dominos/
- The Starbucks Outpost: https://agentoutposts.com/outposts/starbucks/
- The McDonald's Outpost: https://agentoutposts.com/outposts/mcdonalds/
- The Walmart Outpost: https://agentoutposts.com/outposts/walmart/
- The Target Outpost: https://agentoutposts.com/outposts/target/
- The United Airlines Outpost: https://agentoutposts.com/outposts/united/
- The Airbnb Outpost: https://agentoutposts.com/outposts/airbnb/
- The Chipotle Outpost: https://agentoutposts.com/outposts/chipotle/

## API (base: https://api.agentoutposts.com)
- GET /outposts — list the Outpost network.
- GET /outposts/{brand} — the brand's door-state document as JSON (brand: amazon | costco | dominos | starbucks | mcdonalds | walmart | target | united | airbnb | chipotle). The same document published on the brand's Outpost page.
- POST /outposts/{brand}/intent — register intent: what you were trying to do, and for which of the five intents (menu/browse, prices, inventory, ordering, tracking). Returns a receipt (ticket id, queue position for that brand and intent), the current door-state document, alternatives from the Options Registry, and a notify token. If nothing fits, the answer is "demand logged": the intent joins the aggregate the brand team sees.
- GET /outposts/{brand}/notify/{token} — poll for door-state changes (a new API, a changed gate, a converted Outpost).

## Machine-readable discovery
- API catalog (RFC 9727): https://agentoutposts.com/.well-known/api-catalog — the linkset anchored at https://api.agentoutposts.com/outposts; also sent as the `api-catalog` Link header on this site's pages.
- OpenAPI 3.1 specification: https://agentoutposts.com/openapi.json (also linked as `service-desc` from the catalog and the Link header).
- Authentication: https://agentoutposts.com/auth.md — how an agent registers and authenticates for this service. Short answer: it doesn't; the API is anonymous and keyless, and auth.md states the rate gates (intent POST 100/day per hashed caller, 5,000/day service ceiling, 429 with Retry-After) that are the only limits.
- For agents (the machine shelf): https://agentoutposts.com/agents/ — endpoint reference (https://agentoutposts.com/agents/endpoints.html: the four calls, the receipt contract, error shapes) and pricing (https://agentoutposts.com/agents/pricing.json: every call is $0; there are no paid tiers).

## Logging (disclosed)
Registered intents are stored as declarations and reported to brand teams only in aggregate — counts and shapes of demand, never resold as raw data.

## For brand teams
An Outpost measures the agent demand at a brand's wall: agents that arrived with a task and found no sanctioned way through. Converting an Outpost into the brand's official agent gateway — a real, sanctioned door for agents, operated by Agent Outposts under the brand's terms — is a conversation with the operator.

## Operator
Agent Outposts — the agent-readiness registry. Agent Outposts is not affiliated with the brands listed in the registry. Palo Alto, California.