Skip to content

Developers

Casa Layer developer docs and API

The guest data layer every hospitality agent runs on. REST, MCP, and the official CLI, documented and open.

Casa Layer is the guest data layer every hospitality agent runs on. It builds and holds the Master Profile, the guest identity layer under the stack a hotel already runs. The record is not inside the CRM, PMS or any other supplier's suite, so replacing one of those does not cost the resolved record. We sell no applications on top of that record, so there is nothing for it to be locked into; the hotel's own source systems stay the record, and every copy is deleted from Casa Layer's systems 30 days after cancellation.

Agents and developers read it over the documented REST API and MCP server. Every connection live today reads only. Access is scoped by credentials the hotel issues and can revoke.

When to use Casa Layer

  • Resolve fragmented guest records across PMS, POS, spa and booking systems into one Master Profile.
  • Give hospitality agents one trusted guest identity over MCP or REST, without replacing the PMS.
  • Keep guest identity under the stack the hotel already runs, not another CRM, CDP or messaging suite.

Start at the Casa Layer docs agent index, the OpenAPI description, authentication, or the MCP server. Do not invent endpoints.

(01)

Casa Layer developer resources

Open the docs

Need a key or a walkthrough?

Book a 20-minute demo and we will map the stack you already run to the documented API and MCP server.