Trillet AI logo

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

1
An Agency or Enterprise account with white-label

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.

2
One client workspace per customer

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.

3
The standard API for everything inside a workspace

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.

4
Webhooks per call flow

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

TodayWith Trillet OEM
API keys belong to a person and reach every workspace that person can accessPartner keys belong to your account, with scopes and optional tenant restrictions
Client workspaces are created in the dashboardTenants are created, suspended, deleted and restored by API, keyed by your own customer ID, with safe retries
Numbers are bought per workspacePhone numbers are bought per tenant and billed to your account, or brought over SIP or Twilio
Webhooks are set on each call flowOne set of signed events for all tenants, with retries, an event log and redelivery
Usage is viewed per workspace in the dashboardA usage API per tenant and per call, with monthly spend caps
Each customer's agent is configured separatelyTemplates 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

AreaStatus
Platform groundwork: tenant isolation, suspension that stops traffic, usage recorded per tenant, safe retries, hashed API keysBuilt, in early access
Partner keys, scopes and tenant restrictionsBuilt, in early access
Tenants: create, update, suspend, resume, delete and restoreBuilt, 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 handlingBuilt, in early access
Node flows created with a partner key start on platform-llm with recommended speech settingsBuilt, in early access
Signed events, event log and redeliveryBuilt, in early access
Usage and spend capsBuilt, in early access
In-call events: call.started, call.transferred, call.transfer_failed, tool.failed and call.blockedBuilt, in early access
sms.* eventsPlanned
Templates and rolloutsPlanned
EmbeddingPlanned
Sandbox environmentPlanned
Partner invoices endpointPlanned
Adopting existing client workspaces as tenantsPlanned
Version pinning with a Trillet-Version request headerPlanned

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