DEVELOPER DOCS
White label, data roles, rollout
Your brand, your invoice, your practices. Our infrastructure underneath.
The agent layer is infrastructure you resell, not a brand you host.
Branding
- Agent cards and reception endpoints carry the practice's name and run under your platform's domain.
- The reception introduces itself as the practice's reception. We appear nowhere in the patient experience.
- You sell it as your feature, on your invoice, at your price. Commercials are revenue share or per-practice wholesale; details live on the commercials section.
Data roles
| Party | Role |
|---|---|
| The practice | Data controller |
| You (the platform) | Data processor |
| Founder Execute | Sub-processor under a DPA |
Conversation and booking data is processed only to answer, verify and book: typically name, phone number and the reason for contact. Transport and storage are encrypted, access is least-privilege and tenant-scoped, retention windows are configurable, and transcripts are redacted after the window. A current sub-processor list and DPA are part of the partner paperwork; the short version is on the security page.
The rollout shape
- Integration call. Your backend, the channels, the commercials. One call.
- Build. We build the integration against your sandbox and maintain it. Free.
- Launch cohort. You pick the first practices; agent endpoints go live under your brand.
- Scale. Every further practice is configuration, not engineering.
We never sell to practices directly, and we do not run a marketplace. Your practices stay yours.
Put your platform on the agent web.
One integration call: your backend, the channels, the commercials — and a live booking you can watch.