vexa-ai/vexa

开源会议机器人和实时转录——云端或完全自托管。

一个机器人加入你的Google Meet、Microsoft Teams和Zoom通话，并以演讲者身份进行直播 实时转录——通过我们的API或你的主机——然后向沙盒代理提供数据，这些代理由其构建 你们团队拥有的Markdown知识库。Apache-2.0，空气间隙准备。（吉茨语：加入+捕获 离线验证，实时验证待定 — #883。）

vexa.ai运行Vexa 0.12，用于会议机器人和转录。 沙盒知识代理仅自托管——自托管Vexa以运行全栈。

---

联系你的经纪人 ·获取API密钥 ·和创始人谈谈

为什么是维克萨

你能买到的每一个会议AI工具都会把你的对话发送到他们的云端，然后租用你 回去访问。Vexa则反过来：自己运行堆栈，指向自己的模型，拥有什么 你的会议变成了。

没有人同时拥有这三种：

1. Vexa在会议中。 真正的机器人加入了Meet、Teams和Zoom——Jitsi离线验证，实时 验证待定——并实时直播与演讲者有关的文字记录。那支机器人队伍是 真正难的是——所有“与医生聊天”工具都是在成绩单存在之后才开始的。

---

Connect your agent · Get an API key · Talk to the founder

Why Vexa

Every meeting-AI tool you can buy sends your conversations to their cloud and rents you access back. Vexa inverts that: run the stack yourself, point it at your own models, own what your meetings become.

No one else has all three:

1. Vexa is in the meeting. A real bot joins Meet, Teams and Zoom — Jitsi offline-proven, live validation pending — and streams speaker-attributed transcripts live. That bot fleet is the genuinely hard part — every “chat with your docs” tool starts after a transcript exists. Vexa produces it.

2. Your knowledge is files you own. Meetings compile into Markdown in a git repo — portable, diffable, greppable. Knowledge as code.

3. Agents work it, safely. Sandboxed coding agents read and write that repo like developers — isolated ephemeral containers, no egress, thousands in parallel, on Docker or your Kubernetes.

Only here for the transcription API? It’s a complete standalone product — send a bot, read the stream, ignore the agent lane entirely.

---

⚡ Quickstart

Just want a bot in a meeting? Use the hosted service — no install. Sign in at vexa.ai/signin, copy your key from your account page, and send a bot:

curl -X POST "https://api.cloud.vexa.ai/bots" \
  -H "X-API-Key: $API_KEY" -H "Content-Type: application/json" \
  -d '{"platform":"google_meet","native_meeting_id":"abc-defg-hij","bot_name":"Vexa"}'

New accounts get $2 of free bot credit, no card required — about 6 hours of bot time at