Client integrations

Meet users where the client already serves them.

Smoozen is an optional intelligence provider. A client remains the system of record and can disable Smoozen without losing core operations.

Embedded client experience

Render Smoozen inside the client website while the client controls branding, identity, consent, and final checkout.

Client-branded URL

Use a memorable tenant route such as client.smoozen.com for a white-label booking and planning surface.

Server-to-server REST

Use signed, tenant-scoped requests for the fast path. Never infer tenant identity from user text or model output.

Asynchronous callbacks

Use bounded jobs and HMAC-signed webhooks only for slow operations, with retries, replay protection, and manual fallback.

Safety boundary

Model outputs are advisory. Publication, booking, payments, safety actions, network distribution, and user-facing canonical records require deterministic client controls and the appropriate human approval.

View MVP scope · Back home