Skip to main content
Can Vexa put real names on speakers it separated? Today: No. The participants endpoint returns who was invited and who spoke, and deliberately refuses to merge the two — matching a voice to an invitee is a guess. Sponsorable: yes — An explicit mapping step you control, on top of speaker separation.
Put real names on separated speakers, from a list you supply.

​
What it does

  • Matches separated speakers to a roster or calendar invite you provide.
  • Names come from your list. Nobody enrols a voice.
  • Leaves a speaker unnamed rather than guessing at one.

​
What exists today

The participants endpoint returns who was invited (from the calendar) and who spoke (distinct transcript speakers), and deliberately refuses to merge the two — matching a voice to an invitee is a guess, and a wrong guess silently merges two people.

​
What this adds

An explicit mapping step you control, on top of speaker separation.
Speaker separation separates speakers. Names come from a roster you supply. Nobody enrols a voice.

​
How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so “done” means done on your meetings. Your name goes on the release note. Sponsorship buys the order of the queue — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

​
Two doors

Sponsor this

Fifteen minutes. Bring the constraint you are under.

Watch this

One email when it ships. The mail is already written — send it as it is.

​
Questions

No. The participants endpoint returns who was invited and who spoke, and deliberately refuses to merge the two — matching a voice to an invitee is a guess.
An explicit mapping step you control, on top of speaker separation.
No. Speaker separation separates speakers; names come from a roster you supply. Nobody enrols a voice.
Ships upstream Apache-2.0 when sponsored.