Authentication
Use an authenticated deterministic client session or scoped server credential. Tenant identity is never inferred from prompts or model output.
Smoozen integration quickstart
This overview is safe to share with prospective clients. It contains no credentials and does not authorize an integration.
Use an authenticated deterministic client session or scoped server credential. Tenant identity is never inferred from prompts or model output.
Use synchronous server-to-server REST for bounded requests. Include tenant scope, capability scope, request correlation, and idempotency.
Use asynchronous jobs and signed callbacks only when an operation cannot finish within the fast request path.
Treat recommendations as advisory. The client remains canonical for identity, consent, bookings, payments, safety, and final user-facing records.
Complete the client launch profile, data schedule, owner assignments, consent and network approvals, test plan, monitoring plan, and rollback plan before enabling real data or production actions.