Integrations
AI Agents · On the roadmap
Onsai
Casa Layer serves the Master Profile to Onsai's digital hotel agents, which handle calls, chat and email in the guest's own language.
The connection
- Direction
- Casa Layer serves the Master Profile to Onsai. The record flows outwards: Onsai is not a source we read guest data from.
- Status
- On the roadmap
- Website
- onsai.com
What this takes from you
- Work on your side
- Nothing to build per agent. Onsai reads the same record through the MCP server as every other consumer, so there is no bespoke integration to commission.
- Cost to you
- Serving the record to an agent is part of the platform licence, not a separate integration fee. What you pay Onsai for its own usage is between you and them.
- Time to first answer
- Once your Master Profile is live, pointing an agent at it is configuration rather than a build.
- What the agent cannot read
- An agent can only read what the record holds, and the record never holds:
- Payment card numbers, CVV codes, or anything else in PCI DSS scope
- Rate negotiation, contract, and commercial terms
- Staff, payroll, and HR records
- Anything outside the read scope you approve before we connect
We have not built Onsai yet
Onsai is on the roadmap, not connected, so there is nothing to demonstrate on it today. If you run Onsai, tell us: the systems our customers ask for are the systems we build next, and we will tell you honestly where it sits in the queue.
Ask us for Onsai