VYSLO OPEN PLATFORM
Build on trusted voice capture.
A VYSLO card captures the conversations of a day and turns them into transcripts, summaries and a speaker-identity signal. The open platform hands those results to the app you are building — free to use, with no private API reserved for our own app.
VYSLO 卡把一天裡值得留住的對話，變成轉寫、摘要與說話人身份訊號。開放平台把這些結果交給你正在做的 App——免費使用，而且沒有任何只留給我們自家 App 的私有接口。
Four commitments
Free to build on
The API and the SDK are free. Authentication and quotas exist to govern abuse, not to bill you. We sell cards, not API calls.
No private APIs
Whatever the VYSLO app can do, you can do. Our own app runs on this same public platform, so it is a reference client rather than a privileged one.
One account, self-serve
Your VYSLO account is your developer account — user and developer are roles, not two logins. You do not need to own a card to build against the cloud path.
The user holds the keys
Every grant is approved scope by scope by the person whose voice it is, and can be revoked by them at any time, from inside the VYSLO app.
免費接入
API 與 SDK 免費。鑑權與配額只為治理濫用，不為收費——我們賣的是硬件，不是調用次數。
沒有私有接口
VYSLO App 能做的，你也能做。我們自家 App 用的就是同一套公開平台，它只是參考客戶端，而不是特權客戶端。
一個帳號，自助註冊
你的 VYSLO 帳號就是開發者帳號——用戶與開發者是角色，不是兩套登入。接入雲通路不要求你持有硬件。
鑰匙在用戶手上
每一次授權都由聲音的主人逐項確認，也可以由他隨時在 VYSLO App 內撤銷。
Available today
| Capability | Scope | Where |
|---|---|---|
| Transcripts, summaries and speaker identity for a recording | recordings.read | GET /open/ext/recordings/{id} |
| Listing and search across recordings | recordings.read | Android · iOS SDK |
| Original audio file, streamed | recordings.audio | GET /open/ext/recordings/{id}/audio |
| Webhook events: recording ready, capture, smart wake, button, charging | recordings.readevents.subscribe | your webhook URL |
| Weekly insights, speaking statistics and to-dos | insights.read | Android · iOS SDK |
| Transcription of any audio file, with an optional summary | transcription.create | Android · iOS SDK |
| Direct BLE: scan, pair, start, pause and stop recording | capture.control | Android · iOS BLE |
| Card status and card events over BLE | device.status.readevents.subscribe | Android · iOS BLE |
| Live audio into a foreground app | audio.live | Android · iOS BLE |
| Device management: smart wake, voiceprint enrolment, firmware updates, delete and unbind | device.manage | Android · iOS |
| LED per card state, vibration per card event | device.manage | Android · iOS |
Official MCP server and vyslo CLI | — | MCP |
| Self-serve app registration, secrets, callback allowlist, sandbox | — | POST /open/apps |
| Android SDK and iOS SDK, no third-party dependencies | — | Android · iOS SDK |
| 能力 | 權限 | 入口 |
|---|---|---|
| 一條錄音的轉寫、摘要與說話人身份 | recordings.read | GET /open/ext/recordings/{id} |
| 跨錄音的列表與搜索 | recordings.read | Android · iOS SDK |
| 音頻原件，流式下載 | recordings.audio | GET /open/ext/recordings/{id}/audio |
| Webhook 事件：錄音就緒、起停錄音、智能喚醒、按鍵、充電 | recordings.readevents.subscribe | 你的 webhook 地址 |
| 週洞察、發言統計與待辦 | insights.read | Android · iOS SDK |
| 任意音頻檔案轉寫，可選摘要 | transcription.create | Android · iOS SDK |
| BLE 直連：掃描、配對、起錄、暫停、停錄 | capture.control | Android · iOS BLE |
| 經 BLE 的卡片狀態與卡片事件 | device.status.readevents.subscribe | Android · iOS BLE |
| 實時音頻流入前台 App | audio.live | Android · iOS BLE |
| 設備管理：智能喚醒、聲紋註冊、固件升級、刪除與解綁 | device.manage | Android · iOS |
| 按卡片狀態設置 LED、按卡片事件設置振動 | device.manage | Android · iOS |
官方 MCP server 與 vyslo CLI | — | MCP |
| 自助建立應用、密鑰、回跳白名單與 sandbox | — | POST /open/apps |
| Android SDK 與 iOS SDK，零第三方依賴 | — | Android · iOS SDK |
How the data reaches you
Two paths sit behind one SDK. On the cloud path the card records offline and syncs, the cloud produces the transcript, summary and identity result, and your app reads them with a capability token. It never has to go through the VYSLO app at runtime.
On the BLE path your app talks to the card directly: scan, pair, start and stop recording, follow card events, stream live audio and pull recordings off the card. The card checks your token itself, so this works with no network. And through the MCP server, the user's own AI assistant reads the same data with the same consent.
同一個 SDK 背後有兩條通路。雲通路：卡片離線錄音並同步，雲端產出轉寫、摘要與身份結果， 你的 App 用能力令牌讀取——運行時不必經過 VYSLO App。
BLE 通路：你的 App 直接連接卡片——掃描、配對、起停錄音、接收卡片事件、實時串流音頻、 從卡上導出錄音。卡片自己校驗你的令牌，所以不需要網絡。此外經 MCP server， 用戶自己的 AI 助手也能以同樣的授權讀取同一份數據。
Privacy gates you inherit
- Only recordings marked
visibility=visibleleave the platform. Hidden or rejected recordings are never pushed to a webhook and never returned by the API. - A grant binds one user to one app. The token carries the intersection of the scopes the app registered and the scopes that user approved — tampering with the request cannot widen it.
- Users list and revoke every connected app from inside the VYSLO app. After a revocation the server refuses the next call immediately.
- Destructive device operations — unbinding, deleting all recordings, resetting a voiceprint — additionally require a physical button press on the card. That rule applies to our own app too.
- Firmware signing stays closed: a third party can trigger an update, but a card only ever runs an image we signed.
- 只有
visibility=visible的錄音會離開平台。隱藏或被拒的錄音永不推送、也不會由 API 返回。 - 一份授權綁定一個用戶與一個應用。令牌裡寫的是「應用登記的權限」與「該用戶同意的權限」的交集——改請求參數不能越權。
- 用戶在 VYSLO App 內可以看到並撤銷每一個已連接的應用。撤銷後，服務端立刻拒絕後續調用。
- 破壞性設備操作——清綁定、刪除全部錄音、重置聲紋——還需要卡片上的物理按鍵確認。這條規則對我們自家 App 同樣生效。
- 固件簽名鏈不開放：第三方可以觸發升級，但卡片永遠只跑我們簽名的鏡像。
Start here
What to build
Four project patterns — forward, accumulate, recall, capture — and the one rule all four follow.
02Scopes & tokens
The scope bits, the capability token, the 60-day offline grace period and revocation.
03Webhooks
The recording.ready payload, signature verification and the retry schedule.
能做什麼
四種項目模式——轉發、沉澱、回憶、採集——以及它們共同遵守的那一條原則。
02權限與令牌
權限位、能力令牌、60 天離線寬限期與撤銷機制。
03Webhook 事件
recording.ready 的載荷、簽名校驗與重試節奏。
Developer access
App registration is self-serve through the REST API with your own account token — see Quickstart.
Questions, a sandbox that will not behave, or a capability you need that is not here: write to support@vyslo.ai and say what you are building.
建立應用是自助的：用你自己的帳號令牌調 REST API 即可，見快速接入。
有疑問、sandbox 不按預期工作，或你需要的能力這裡沒有：寫信到 support@vyslo.ai，說明你在做什麼。