Hilton runs a real partner API — Content, DCShop and DCRes — covering browse-to-book, but credentials are Hilton-issued and agreement-gated, with no self-serve or agent-native door. Which endpoints a partner may call depends on its agreement with Hilton, and added functionality requires working with a Hilton sponsor.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Hilton's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | PARTNER-GATED | Hilton Partner API — Content / DCShop via developer.hilton.io — Dev portal documents property/shop endpoints (e.g. GET /hospitality-partner/v2/dcshop/props) but Client ID/Secret are 'provided to you by Hilton' and allowed endpoints depend on 'your agreement with Hilton'. | Source — developer.hilton.io | 2026-11-01 |
| Prices | PARTNER-GATED | Hilton Partner API — DCShop — DCShop returns rates/pricing for partners (shop responses, rate plans in portal docs/release notes); access is credential- and agreement-gated, not self-serve. | Source — developer.hilton.io | 2026-11-01 |
| Inventory | PARTNER-GATED | Hilton Partner API — DCShop availability — Availability shopping is a documented partner API function; existing partners must work with a 'Hilton sponsor' for added functionality — no open signup. | Source — developer.hilton.io | 2026-11-01 |
| Ordering | PARTNER-GATED | Hilton Partner API — DCRes (reservations) — Portal offers downloadable Swagger specs for partner products including reservation creation (DCRes in portal docs); gated by Hilton-issued credentials and partner agreement. | Source — developer.hilton.io | 2026-11-01 |
| Tracking | PARTNER-GATED | Hilton Partner API — DCRes reservation retrieval/status — Portal docs reference reservation status fields (e.g. /dcres/{id}?fields=resStatus) for partners; guest-side tracking otherwise is hilton.com/app human-only. | Source — developer.hilton.io | 2026-11-01 |
Agent-native surfaces at Hilton: official MCP server — none found; llms.txt — not verified; API catalog (RFC 9727) — none published. Automated access: Restrictive: robots.txt disallows /search/, /book/, /confirmation/ and /modify/ for * (only named ads bots allowed /search/ and /book/) (evidence).
One page per task an agent might attempt at Hilton — the door-state for that task alone, and what fits instead.
| Task | State | The page |
|---|---|---|
| Menu / browse | PARTNER-GATED | Can an AI agent search Hilton hotels? |
| Prices | PARTNER-GATED | Can an AI agent check prices at Hilton? |
| Inventory | PARTNER-GATED | Can an AI agent check availability at Hilton? |
| Ordering | PARTNER-GATED | Can an AI agent book a stay at Hilton? |
| Tracking | PARTNER-GATED | Can an AI agent check the status of a Hilton reservation? |
If you came to do something at Hilton and the door was closed, say so here — and take the receipt with you.
POST your intent — what you were trying to do, and for which of the five intents — to the intent endpoint. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at Hilton, the current door-state document, and any alternatives the Options Registry can offer — another business whose door is open for the same need. If nothing fits, the answer is demand logged: your intent joins the aggregate count. The receipt also carries a notify token: poll the notify endpoint and you will learn when this door-state changes — a new API, a changed gate, a converted Outpost.
This Outpost measures agent demand at your wall.
Every intent registered here is an agent that arrived at Hilton with a task — something to browse, a price to check, an order to place, a delivery to follow — and could not complete it through a sanctioned agent door. That demand is currently invisible to you: blocked attempts never become sessions. The registry counts it, categorizes it by intent, and timestamps it, so the size of the agent channel you are not serving is a number rather than a guess.
Converting this Outpost into Hilton's official agent gateway — a real door for agents, operated by Agent Outposts under your terms — is a conversation with Agent Outposts. Palo Alto, California.
This page is already public. Start with your demand report.
This Outpost counts declared agent demand at the Hilton wall — by intent, in aggregate, never resold as raw data. Your demand report pairs this door-state dossier with that demand shape as it accrues. How claiming works · Talk to us about your Outpost
Agent Outposts is not affiliated with Hilton. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.