CAPABILITY STATUS
Capability status
Everything the open platform offers, where it is documented, and the scope each part needs: on the cloud, on the card, and in the AI tools your users already work in.
開放平台提供的全部能力、文檔在哪裡，以及每一項需要的權限：雲端、卡片，以及用戶本來就在用的 AI 工具。
Cloud
| Capability | Scope | Where |
|---|---|---|
| Self-serve app registration, secrets, callback allowlist | — | REST |
| Sandbox mode: full integration without hardware or outside users | — | Quickstart |
| User consent and revocation, per scope, with a revocation list | — | Scopes & tokens |
| Capability tokens with 60-day offline grace and silent renewal | — | Scopes & tokens |
| Transcripts, summaries and speaker identity with its source | recordings.read | REST, Android, iOS |
| Listing and search across recordings | recordings.read | Android, iOS |
| Original audio download | recordings.audio | REST |
| Webhook events: recordings, processing progress, capture, smart wake, button, charging | recordings.readevents.subscribe | Webhooks |
| Transcription API: upload any audio file, get a transcript and optionally a summary | transcription.create | Android, iOS |
| Weekly insights, speaking share and to-dos | insights.read | Android, iOS |
| Device list and cloud status snapshot with observedAt | device.status.read | Android, iOS |
| Multiple cards on one account | — | Android, iOS |
| Bring your own model for summaries, per app or per user; the selected service is the only one called | — | support@vyslo.ai |
| Self-hosting: run the VYSLO server yourself, with results labelled as your own instance | — | support@vyslo.ai |
| OpenAPI description of the REST API | — | REST API |
| Starter apps for Android, iOS and React Native | — | support@vyslo.ai |
| 能力 | 權限 | 入口 |
|---|---|---|
| 自助建立應用、密鑰與回跳白名單 | — | REST |
| Sandbox：不需要硬件、不涉及外部用戶即可完整聯調 | — | 快速接入 |
| 用戶逐項同意與撤銷，附撤銷清單 | — | 權限與令牌 |
| 能力令牌，60 天離線寬限，靜默續簽 | — | 權限與令牌 |
| 轉寫、摘要與帶來源的說話人身份 | recordings.read | REST, Android, iOS |
| 跨錄音的列表與搜索 | recordings.read | Android, iOS |
| 音頻原件下載 | recordings.audio | REST |
| Webhook 事件：錄音、處理進度、起停錄音、智能喚醒、按鍵、充電 | recordings.readevents.subscribe | Webhook 事件 |
| Transcription API：上傳任意音頻，得到轉寫及可選摘要 | transcription.create | Android, iOS |
| 週洞察、發言佔比與待辦 | insights.read | Android, iOS |
| 設備列表與帶 observedAt 的雲端狀態快照 | device.status.read | Android, iOS |
| 一個帳號多張卡 | — | Android, iOS |
| 自帶模型生成摘要，按應用或按用戶；只調用所選服務 | — | support@vyslo.ai |
| 自託管：自行部署 VYSLO 服務端，結果標明為你自己的實例 | — | support@vyslo.ai |
| REST API 的 OpenAPI 規範 | — | REST API |
| Android、iOS 與 React Native 示例工程 | — | support@vyslo.ai |
On the card
| Capability | Scope | Where |
|---|---|---|
| Direct BLE: scan, pair and connect, no VYSLO app at runtime | — | Android, iOS |
| Start, pause, resume and stop recording under an exclusive control lease | capture.control | Android, iOS |
| Live card status: battery, storage, firmware, recording, listening, smart wake | device.status.read | Android, iOS |
| Card events: capture, smart wake, listening, button, charging | events.subscribe | Android, iOS |
| Pull audio off the card as Opus, WAV or PCM, or in bulk over Wi-Fi | recordings.audio | Android, iOS |
| Live audio: hold the button and speak into the foreground app | audio.live | Android, iOS |
| Device management: smart wake, card name, voiceprint enrolment, firmware updates, delete and unbind with on-card confirmation | device.manage | Android, iOS |
| LED per card state and vibration per card event, saved on the card | device.manage | Android, iOS |
| Offline token verification on the card, with revocation | — | Scopes & tokens |
| 能力 | 權限 | 入口 |
|---|---|---|
| BLE 直連：掃描、配對、連接，運行時不需要 VYSLO App | — | Android, iOS |
| 持有控制權租約時起錄、暫停、繼續、停錄 | capture.control | Android, iOS |
| 實時卡片狀態：電量、存儲、固件、錄音、監聽、智能喚醒 | device.status.read | Android, iOS |
| 卡片事件：起停錄音、智能喚醒、監聽、按鍵、充電 | events.subscribe | Android, iOS |
| 從卡上導出 Opus、WAV 或 PCM，或經 Wi-Fi 批量快傳 | recordings.audio | Android, iOS |
| 實時音頻：按住按鍵說話，流入前台 App | audio.live | Android, iOS |
| 設備管理：智能喚醒、卡片名稱、聲紋註冊、固件升級，刪除與解綁需卡上確認 | device.manage | Android, iOS |
| 按卡片狀態設置 LED、按事件設置振動，保存在卡片上 | device.manage | Android, iOS |
| 卡片離線校驗令牌並執行撤銷 | — | 權限與令牌 |
AI tools and zero-code
| Capability | Scope | Where |
|---|---|---|
| Official MCP server for Claude, ChatGPT, Cursor and other MCP clients | — | MCP |
vyslo CLI: sign in, list, search and export recordings, card status, local MCP server | — | MCP |
| Zero-code layer: keyboard extension, Shortcuts and Intents, the system share sheet | — | VYSLO app |
| VYSLO's own app on this same public SDK, with no private API | — | Overview |
| 能力 | 權限 | 入口 |
|---|---|---|
| 官方 MCP server，支援 Claude、ChatGPT、Cursor 等 MCP 客戶端 | — | MCP |
vyslo CLI：登入、列出/搜索/導出錄音、卡片狀態、本地 MCP server | — | MCP |
| 零代碼層：鍵盤擴展、快捷指令與 Intent、系統分享面板 | — | VYSLO App |
| VYSLO 自家 App 使用同一套公開 SDK，沒有私有接口 | — | 概覽 |
How device access stays safe
Opening the card to third parties rests on one foundation: the card arbitrates several clients with a single control lease, verifies capability tokens offline, keeps reliable time and checks revocation. Destructive operations also wait for a press on the card itself.
That is also why the raw protocol is not a public contract and why the firmware signing chain stays closed. Two things can never be recalled: data already handed to a third party, and a protocol that every card already sold will keep accepting. The capability token exists so that everything else can be.
把卡片開放給第三方，建立在同一塊地基上：卡片用單一控制權租約仲裁多個客戶端、離線校驗能力令牌、保有可靠時間並校驗撤銷狀態； 破壞性操作還要等卡片上的一次按鍵確認。
這也是裸協議不作為公開承諾、固件簽名鏈不開放的原因。有兩樣東西永遠收不回：已經交給第三方的數據， 以及一套所有已售卡都會繼續認的協議。能力令牌存在，就是為了讓其餘的一切可以收回。
Missing something?
Tell us what you are building and what is missing: support@vyslo.ai.
告訴我們你在做什麼、還缺什麼：support@vyslo.ai。