Building on Trillet today
How software partners run Trillet voice agents for their customers with white-label and the standard API, what Trillet OEM adds, and the status of each part.
Trillet OEM is in early access with design partners. You do not need it to start: partners already run Trillet for their customers with white-label and the standard API. This page explains that setup, what Trillet OEM adds, and what is built today.
The setup that works today
Your account holds your branding: portal domain, logo, colours and email sender. Client workspaces can inherit it, so your customers see your brand, not Trillet's.
Each of your customers gets its own workspace with its own agents, call flows, numbers, call history and knowledge bases. Create them in the dashboard. Each workspace can draw on your account's wallet or hold its own balance.
Create an API key and send the client workspace ID in x-workspace-id to manage that customer's agents, call flows, numbers, calls, batch calls and call history. See Authentication.
Configure the post-call webhook and the inbound call webhook on each call flow to send call results to your system.
# List one customer's agents, using your API key and that customer's workspace ID
curl https://api.trillet.ai/v1/api/agents \
-H "x-api-key: YOUR_API_KEY" \
-H "x-workspace-id: CLIENT_WORKSPACE_ID"
A Business Associate Agreement is available on Agency and Enterprise accounts at no extra fee. Execute it before any customer workspace handles protected health information.
What Trillet OEM adds
| Today | With Trillet OEM |
|---|---|
| API keys belong to a person and reach every workspace that person can access | Partner keys belong to your account, with scopes and optional tenant restrictions |
| Client workspaces are created in the dashboard | Tenants are created, suspended, deleted and restored by API, keyed by your own customer ID, with safe retries |
| Numbers are bought per workspace | Phone numbers are bought per tenant and billed to your account, or brought over SIP or Twilio |
| Webhooks are set on each call flow | One set of signed events for all tenants, with retries, an event log and redelivery |
| Usage is viewed per workspace in the dashboard | A usage API per tenant and per call, with monthly spend caps |
| Each customer's agent is configured separately | Templates installed in every tenant and upgraded in staged rollouts (planned) |
| Your users sign in to the Trillet portal (under your brand) | Embedded screens inside your own app, with no separate login (planned) |
Release status
| Area | Status |
|---|---|
| Platform groundwork: tenant isolation, suspension that stops traffic, usage recorded per tenant, safe retries, hashed API keys | Built, in early access |
| Partner keys, scopes and tenant restrictions | Built, in early access |
| Tenants: create, update, suspend, resume, delete and restore | Built, in early access |
| Phone numbers: partner-billed purchase, release, and bring your own (SIP or Twilio) | Built, in early access |
| Call flow settings: greeting, speech, recording and call handling | Built, in early access |
Node flows created with a partner key start on platform-llm with recommended speech settings | Built, in early access |
| Signed events, event log and redelivery | Built, in early access |
| Usage and spend caps | Built, in early access |
In-call events: call.started, call.transferred, call.transfer_failed, tool.failed and call.blocked | Built, in early access |
sms.* events | Planned |
| Templates and rollouts | Planned |
| Embedding | Planned |
| Sandbox environment | Planned |
| Partner invoices endpoint | Planned |
| Adopting existing client workspaces as tenants | Planned |
Version pinning with a Trillet-Version request header | Planned |
Pages in this section marked Early access describe what is built. Details may still change while it is tested with design partners. Pages marked Coming soon describe planned designs. To join early access, contact your Trillet account manager or talk to us.
Last updated on