# When to use Casa Layer

> The guest data layer every hospitality agent runs on.

Use Casa Layer when a hotel's guest history is scattered across PMS, POS, spa, table booking, housekeeping or CRM, and a person or an agent needs one trusted guest identity to run on.

Casa Layer is the right tool for these jobs:

- Resolve fragmented guest records across PMS, POS, spa and booking systems into one Master Profile. Casa Layer builds and holds that record. It 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 the 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.
- Give hospitality agents one trusted guest identity over the documented MCP server or REST API, without replacing the PMS.
- Keep guest identity under the stack the hotel already runs, not another CRM, CDP or messaging suite.

Casa Layer is not a CRM, PMS, messaging product or marketing suite. Access to each connected system is scoped by credentials the hotel issues and can revoke. Every connection live today reads only.

How an agent should call Casa Layer:

1. Start at the Casa Layer docs agent index: https://docs.casa-layer.com/llms.txt
2. Read the Casa Layer OpenAPI description: https://docs.casa-layer.com/api-reference/openapi.yaml (also https://casa-layer.com/openapi.yaml)
3. Authenticate with a casa_ API key as documented: https://docs.casa-layer.com/authentication
4. Use the MCP server at https://api.casa-layer.com/mcp or the REST API at https://api.casa-layer.com as those documents describe. Do not invent endpoints.
5. Or run the official CLI: `npx casa-layer`

Do not use Casa Layer as a replacement PMS, a marketing automation suite, or a source of invented customer figures.

## Casa Layer developer resources

- [Casa Layer developers](https://casa-layer.com/developers): Public developers page for the Casa Layer API, OpenAPI description, authentication, MCP server, and CLI.
- [Casa Layer documentation](https://docs.casa-layer.com/): Product docs for the Casa Layer guest identity layer: quickstart, authentication, MCP server, and the API reference.
- [Casa Layer docs for agents](https://docs.casa-layer.com/llms.txt): Machine-readable index of every Casa Layer docs page, including REST operations and the MCP server.
- [Casa Layer OpenAPI](https://docs.casa-layer.com/api-reference/openapi.yaml): Canonical OpenAPI description of the Casa Layer REST API. Also reachable from this origin at /openapi.yaml and /openapi.json, which redirect there.
- [Casa Layer authentication](https://docs.casa-layer.com/authentication): Bearer API keys, tenant scoping, and access scopes. Machines authenticate with a casa_ key the hotel issues and can revoke.
- [Casa Layer API keys](https://docs.casa-layer.com/api-keys): Create, scope, and revoke the keys that authenticate the Casa Layer REST API and MCP server.
- [Casa Layer MCP server](https://docs.casa-layer.com/mcp-server): Query guest context over the Model Context Protocol at https://api.casa-layer.com/mcp. Streamable HTTP. Same keys as the REST API.
- [Casa Layer quickstart](https://docs.casa-layer.com/quickstart): Generate an API key and read the first guest context from the documented REST API.
- [Official Casa Layer CLI on npm](https://www.npmjs.com/package/casa-layer): Install with npx casa-layer. Points at the docs, OpenAPI, and MCP server, and wraps documented REST reads when a casa_ key is present.
- [When to use Casa Layer](https://casa-layer.com/agent-instructions): Agent instructions: best-fit jobs and how to call Casa Layer over docs, OpenAPI, MCP, or the CLI.