Leexi
Read Leexi calls, transcripts and AI summaries, import recordings, manage meeting events and the meeting assistant, and administer users and teams (plus the reseller endpoints).
About
Leexi ships in the w6w first-party pack. It declares 39 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.leexi- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- AI & Machine Learning · Productivity · Video & Streaming
Overview
Leexi is an AI meeting assistant and call recorder for sales and customer-facing teams. This app lists and reads calls and meetings with their transcripts, AI summaries (prompt completions), call topics, tasks and speakers; imports a call from an uploaded recording; reads, edits and deletes call notes; manages meeting events and sends the Leexi assistant to a meeting; administers users and teams; and, with a reseller key, manages client companies, their subscriptions, teams and users.
Build with Leexi
Three routes to the same 39 actions. The Workflow tab is generated from Leexi's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Call
call-create Create a call or meeting from an already-uploaded recording. Asynchronous: the answer is only an acknowledgement and the call appears a few minutes later. Limited to 10 requests/minute.
Get Call
call-get Retrieve one call or meeting with its AI completions plus the call topics and the full transcript (word-level timestamps), and its simple transcript. A call outside the key's access scope answers 404.
List Calls
call-list List calls and meetings within the API key's access scope, with summaries, tasks, speakers and customers. Filter by date, owner, integration source or customer.
Request Recording Upload
call-presign-recording Get a presigned S3 URL and `recording_s3_key` for uploading a call recording by a single PUT. The file expires after 3 days unless used by Create Call.
Create Client Company
client-company-create Reseller only: create a client company with a Leexi trial. It has no team or user yet.
Deactivate Client Company
client-company-deactivate Reseller only: deactivate a client company (cancels its subscription and deactivates every user).
List Client Companies
client-company-list Reseller only: list the client companies attached to your reseller account.
Update Client Company
client-company-update Reseller only: update a client company's name, license, seats, billing plan or trial.
Cancel Client Subscription
client-subscription-cancel Reseller only: end a client's trial or cancel its paid subscription.
Start Client Subscription
client-subscription-start Reseller only: end the client's Leexi trial and start its paid Stripe subscription using the plan set on the company. 422 when billing goes through Leexi; 409 when a subscription is already open.
Delete Client Team
client-team-delete Reseller only: delete a team of a client company. A team that still has users answers 422.
Create Meeting Event
meeting-event-create Register a meeting (by its video-call URL) so Leexi can send an assistant to record it.
Launch Meeting Assistant
meeting-event-launch-bot Send the Leexi meeting assistant to a meeting event now (or stop one that is running). A bot already running answers 409.
List Meeting Events
meeting-event-list List the calendar and API meeting events the Leexi assistant can join.
Create User
user-create Create a user in your workspace. Billed licenses are affected, so the API key needs the write_users scope.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Leexi's real ids.
{
"manifestVersion": "2",
"name": "leexi-example",
"steps": [
{
"id": "call-create",
"uses": {
"app": "io.w6w.leexi",
"action": "call-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"recording_s3_key": "<recording_s3_key>",
"external_id": "<external_id>",
"direction": "<direction>"
}
}
]
}Here are some of the things you can do
-
Create Call
performcall-create -
Get Call
readcall-get -
List Calls
searchcall-list -
Get Call Note
readcall-note-get -
List Call Notes
searchcall-note-list
+34 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Leexi, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Leexi. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "call-create",
payload: {
recording_s3_key: "<value>",
external_id: "<value>",
direction: "<value>",
performed_at: "<value>",
user_uuid: "<value>",
// title: "<value>",
// locale: "<value>",
// tags: "<value>",
// customers: "<value>",
// participating_user_uuids: "<value>",
// custom_fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action call-create --payload '{"recording_s3_key":"<value>","external_id":"<value>","direction":"<value>","performed_at":"<value>","user_uuid":"<value>"}'Give an AI agent Leexi — without giving it Leexi's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.leexi#call-create",
"input": {
"recording_s3_key": "<recording_s3_key>",
"external_id": "<external_id>",
"direction": "<direction>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Leexi connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Leexi's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Leexi itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Leexi declares its own checks, so its health is a property of the app rather than something the host guesses at.
Leexi platform status
status.leexi.ai (Better Stack). The `api.leexi.ai` resource decides; the `leexi.ai` web app is capped at degraded.
API reachability
Unauthenticated GET of public-api.leexi.ai/v1/users. The documented 401 is the expected healthy answer; credential validity is the `auth:basic` check's job.