AI Agents · On the roadmap

D3x

Casa Layer serves the Master Profile to D3x's hospitality agents, which resolve guest requests across WhatsApp, voice and email.

The connection

Direction: Casa Layer serves the Master Profile to D3x. The record flows outwards: D3x is not a source we read guest data from.
Status: On the roadmap
Website: www.d3x.ai

What this takes from you

Work on your side: Nothing to build per agent. D3x 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 D3x 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

Other integrations

We have not built D3x yet

D3x is on the roadmap, not connected, so there is nothing to demonstrate on it today. If you run D3x, 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 D3x