Public API
Read your hotel's own data over a conventional REST API. Operators generate a key inside Foyer; you send it as a bearer token.
Connect
Connect an AI agent to a hotel. Once the operator approves, the agent reads and acts on that hotel's data within the scope it was granted.
Start with an agent
Point an MCP client at Foyer and it registers itself — nothing needs setting up on our side first. In Claude Code:
claude mcp add --transport http foyer https://getfoyer.app/mcpThen hand your agent the docs. llms-full.txt is every guide on this site plus the full tool catalogue as one markdown file, so it can read the whole surface in a single request instead of crawling the pages. llms.txt is the short index if you only need the map.
Read the quickstart for what happens on the first call, and what to be careful with — there is no sandbox hotel.
Which one do I want?
Use the Public API when you are building against one hotel and hold its API key — reporting, a dashboard, an export. Use Connect when an agent needs to act for a hotel it does not own a key for: the operator grants access and can withdraw it.
Browse the tool reference to see everything an agent can call. It is generated from the running server, so it states the real surface rather than a maintained copy of it.