Alibaba Qianwen AI Glasses

Covered here: Alibaba's 千问AI眼镜 (Qianwen AI Glasses) S1 and G1, and the 千问AI硬件开放平台 developer platform at device.qianwen.com — both its self-serve Skill platform and its brokered industry platform.

Not covered here: Tmall Genie speakers and the 哇哦闺蜜机 portable screen (same organisational lineage, not eyewear) · Alibaba Cloud Bailian (百炼) and Coze (扣子), which this platform consumes as Agent plugins rather than competing with · the Qwen model family and the 千问 assistant app, which are software, not wearables.

Overview

Alibaba sells two pairs of AI smart glasses and runs a developer platform for them that looks like nothing else in this landscape: on the self-serve path there is no SDK to download, no app to compile, and no code that runs on the device. A third-party integration is a Skill — a SKILL.md file with YAML frontmatter, executed by Alibaba's cloud agent, which calls tools you register. Those tools can be your existing REST API, an MCP server, or an agent you already built on Bailian or Coze. The platform describes itself as the official ecosystem platform for the glasses, "为企业和个人开发者提供AI眼镜定制和眼镜技能一站式搭建能力" (千问AI硬件开放平台), and it splits in two: a 技能平台 (Skill platform) open to individual and enterprise developers, and a 行业开放平台 (industry platform) for enterprises building custom units.

Two models, and the difference decides what you can build. The industry platform names them as the two base products: 千问AI眼镜S1（带屏显）或者G1（不带屏显） — S1 with a display, G1 without (platform introduction). Alibaba's own portal product cards describe S1 as a 全感知旗舰 AI 终端 whose 显示方案 reads 双显双光机 (dual display, dual optical engines), aimed at industrial inspection, retail, remote collaboration and announcements; and G1 as a 轻量化智能 AI 终端 whose display field simply reads 无屏幕, aimed at in-car use, voice announcements and lightweight capture (device.qianwen.com, product cards in the portal's own shipped front-end). No optical stack, resolution or brightness figure appears on any surface readable without a login, so none is claimed here. The one display property Alibaba does state sits on the UI-tool pages: the on-glasses display is 单原色, single primary colour, with a small display area.

Shipping status and price need stating carefully. Both SKUs have live Tmall retail listings, linked by item id from the developer portal's own 产品中心 footer — S1 as item 1035065479567, G1 as item 1020553105651. Both of those pages bounce an unauthenticated request to login.taobao.com, from desktop, mobile and crawler user agents alike, and on the one shell that does render the price element is served empty. So no price is quoted on this page, and purchasability and stock could not be confirmed for either SKU. The dated evidence that the hardware ships is indirect but solid: the 千问AI穿戴 companion app has been live on the China App Store since 21 October 2025 and was last updated 10 August 2026 (App Store listing), and the developer docs treat real hardware as the normal test target. Regions: no purchase path outside mainland China was found. There is no English developer surface — /en and /en/docs both 404, global.qianwen.com, developer.qianwen.com and device.qwen.com do not resolve, and all 49 documentation entries are lang="zh-Hans". One nuance cuts against a flat "China-only": the companion app itself is listed in the US and Hong Kong App Stores as well as China, and absent from GB, DE, JP and SG. That is an app listing, not a way to buy the glasses.

On the name. Our earlier watch entry called these Quark AI Glasses. Alibaba has moved them onto the 千问 brand: the old portal host wearables.aligenie.com now 302s to device.qianwen.com (while the new portal's JSON-LD still carries "url":"https://wearables.aligenie.com/"), the portal's own careers link points at talent.quark.cn, the account-upgrade guide walks developers off their 原淘宝账号 onto a 千问账号, and zero occurrences of 夸克 remain anywhere in the current portal front-end or its documentation. The old name survives on a sibling surface Alibaba forgot: its Tmall Genie hardware site still lists 天猫精灵,夸克ai眼镜,夸克智能眼镜,哇哦闺蜜机 in its meta keywords (tmallgenie.com, re-read 25 August 2026). Use 千问AI眼镜 / Qianwen AI Glasses.

What you can buy

Cheapest way to run your own code: Reading costs nothing and needs no account; running anything needs a Chinese identity document. All 49 documentation entries read anonymously (device.qianwen.com/docs returns HTTP 200 with window.loginStatus = false, while /guide 302s to /account/login), and once registered, authoring a Skill, importing an MCP/OpenAPI/Agent plugin and running it in the sandbox need no hardware. No fee is published for any of that, and no page states there is none — 免费, 收费, 费用, 付费 and 价格 appear on none of the 49 entries, so nothing about cost is asserted beyond the published quotas (official demo tools capped at 30 calls per API per user per day; an unpublished daily model-tool quota raised by asking support in a DingTalk group). Two walls follow. First, registration: 个人实名认证或企业认证 is mandatory, sign-in is 手机号 / 千问App扫码 / 淘宝 / 支付宝, the individual form validates an 18-digit mainland-China ID number with the full checksum, HK/Macau/Taiwan applicants are told to email AliGenie@list.alibaba-inc.com, and enterprise verification needs a corporate Alipay account (applicants who cannot use one, 如大型外企, are routed to offline email approval). Second, hardware: the 真机 step needs a physical S1 or G1 bound by QR through the 千问AI穿戴 app, and both SKUs sell only through Alibaba's Tmall storefront, whose price could not be read from an unauthenticated session. Practically: a developer outside mainland China can read the entire platform and design against it today, and can execute nothing on it.

What the listings leave out

Access

There is a native SDK, and it is the part you cannot have. The 千问AI硬件开放平台专业版 SDK "面向接入方 App 提供双端一致的设备接入能力" — consistent device access across both mobile platforms — and its capability page reads like a real SDK reference: Bluetooth scan and dedupe, connect and disconnect, battery and brightness state, camera capture returning bytes versus on-device save, video record, live preview, unsynced-media badges, mic pickup direction, and Android process revival for background stability (APP capability opening). Alibaba's own privacy notice for it states "本SDK支持的平台：iOS版、Android版" and lists its core functions as 账号授权、蓝牙连接、设备管理、拍照、录像、实时视频流、媒体同步、麦克风录音, with 上海智信普惠科技有限公司 as provider (SDK privacy notice). And there is no download link on any of the 49 public documentation entries — no Maven, Gradle, CocoaPods, .aar or .framework instruction of any kind. Access begins with "需要业务侧与官方客服获取 accessKeyId、accessKeySecret 等必要信息", and the industry platform states outright that 当前暂无完全自助式配置后台，接入采取线下对接的方式 — no fully self-service console; integration happens offline (access guide). A GitHub search turns up no official repository — nothing under the alibaba, QwenLM or alibaba-inc orgs, and the aligenie and qianwen orgs do not exist — only a handful of zero-star third-party repos. The logged-in console behind the identity gate was not inspected.

App model

For a self-serve Skill, code runs in Alibaba's cloud and on your own servers — never on the glasses, and never in a phone app you ship. The unit of work is a Skill directory, and its shape will look familiar:

skill-name/
├── SKILL.md          # required, main file
├── tool_schema.json  # required, generated by the platform
├── references/       # optional, loaded on demand
└── assets/           # optional, loaded on demand

SKILL.md carries YAML frontmatter with exactly two required fields — name (2–64 chars) and description (up to 1000 chars, "Agent 凭此字段决定是否激活 Skill") — and the platform is strict about it: "文件名必须是 SKILL.md，大小写敏感，不接受 skill.md 或 SKILL.MD" (Skill specification). Only name and description load at startup; the full instructions load when a request matches. Body content is recommended under 500 lines and hard-capped at 2000 lines or 80,000 characters, with overflow pushed into references/ for on-demand loading. Tools are referenced from the body with a ^^{pluginCode}.{toolCode}^^ syntax, inserted with @ in the editor, and the platform writes tool_schema.json for you. The layout mirrors Anthropic's Agent Skills convention closely, though the vendor never says so — Anthropic is not named anywhere in the documentation set.

Three enterprise-only routes escape the cloud-only model: the Professional Edition SDK inside your own phone app; your own H5 pages hosted inside Alibaba's companion app (see Distribution); and an RTC stream your own server consumes. The 千问AI穿戴 companion app is Alibaba's and is not optional.

The inner loop is short. Debug in a sandbox that is isolated from production, watching each tool call's parameters and return values; then bind real hardware: "进入 Skill 编辑页，点击「真机」菜单，页面将生成设备绑定二维码", scanned from 我的 - 扫码 in the 千问 AI穿戴 app, after which you talk to the glasses (real-device testing). Binding is sticky — once on, the device stays in that mode until every Skill is removed in device management.

Distribution

For a consumer, an app reaches a wearer exactly one way: the skill market inside Alibaba's own 千问AI穿戴 companion app. There is no sideload and no APK. Publishing offers three scopes (publish):

One documented route runs inside the companion app rather than through the market. An enterprise that takes the 双向授权 (two-way authorisation) path can host its own H5 pages and have users open them from within the companion app with no second login — "用户在千问AI穿戴APP 中访问企业开发的 H5 页面无需再次登录", governed by a one-time, ≤5-minute, HTTPS-bound ticket (third-party H5) — and can have a custom entry placed on that app's home screen, either replacing an existing 推荐服务 entry or adding one under 更多服务 (custom app entry). Enterprise on-glasses desktop apps reach devices through an offline process instead: contact platform staff for a productKey, agree a desktopAppCode, prepare five icon assets, and have the platform enter the configuration for you (desktop menu, icon specification).

Public publishing is open in principle and gated twice in practice. There is no partner list and no invite: any registered developer can submit to the public market. But every version 自动进入小二审核环节 — automatic entry into platform-staff review, with a rejection returning the Skill to 待上架 for resubmission — and no review criteria are published anywhere. The page that should carry them, 应用开发与上架规范, exists in the navigation and is published with nothing but its own title. The harder gate is upstream, at the account: without mainland-China real-name or enterprise verification you never reach the console at all. That, not a partner programme, is what closes this platform to a developer outside China.

Publishing has one structural constraint worth designing around: "SKILL发布上线时，其引用的所有工具都必须处于已发布", and a published plugin or tool enters a locked state and cannot be edited, which the platform explains as avoiding disruption to live Skills. Plan tool versions before you ship, not after.

Capabilities, limits & AI

The published tool catalogue is short, explicit, and sorted into three categories — 镜端工具 (glasses-side), 云服务工具 (cloud), and 屏显工具 (screen display) (overview).

AI & the assistant

This is where Alibaba diverges hardest from everyone else on this map. The platform states plainly that it is built on Alibaba's own model — "平台基于阿里千问模型" (platform introduction) — and rather than reserving that model behind a wake word, it hands a general-purpose model to third parties as two ordinary callable tools. 4F2df8.general_qa_stream is documented as a "通用大模型问答工具，基于用户 query 生成回答", streaming its answer back in chunks (model service). 4F2df8.image_qa_stream takes a publicly reachable imageUrl plus a query and streams back an understanding of the image (image recognition). Neither tool page names a model, a version or a family, so treat "Qwen" here as the platform's brand rather than a documented model identity. Compose them with capture_photo and you have wearable visual Q&A in three tool calls and no AI vendor of your own — Alibaba's own worked example is a museum-artefact identifier that does exactly that.

Your Skill is the agent. Intent routing, prompting, refusal wording and tool selection are all yours, written in Markdown; the platform supplies the model and the runtime. And bring-your-own is a first-class alternative rather than a workaround: the RTC path streams the wearer's microphone and camera to your infrastructure and lets your server speak back through SPEAK, so a fully self-hosted ASR → LLM → TTS loop is a documented shape, not a hack. Third-party agents are welcome from the other direction too — the Agent plugin type imports a Bailian or Coze app with nothing but an appId and apiKey, and the platform's own quick-start builds its first Skill on a Bailian MCP service (quick start). The one thing that is not open is the front door: Skills are reached by the agent matching your description against what the wearer said, and the wake phrase itself stays first-party unless you are an enterprise buying a second one.

Roadmap

21 October 2025 — the companion app appears. 千问AI穿戴 lands on the China App Store, published by Shanghai Zhixin Puhui Technology Co., Ltd. (上海智信普惠科技有限公司), and has been updated steadily since; version 1.11.5 shipped 10 August 2026, and the app reached the US and Hong Kong storefronts in November 2025 (App Store). This is the earliest hard date available for the product line.

14 July to 18 August 2026 — the entire developer platform is written. Every one of the 49 documentation entries was last modified inside this five-week window: the industry platform's pages cluster on 16 July, the Skill platform's on 14–17 July, and the whole 开放能力介绍 capability catalogue — photo, RTC streaming, geolocation, model service, image recognition and all three UI tools — on 17–18 August. The Professional Edition SDK's compliance guide and privacy notice both took effect 15 July 2026. A platform this young with documentation this specific is a real investment, not a placeholder.

In flight now. The RTC audio and video path is labelled 功能公测中 (public beta) and is the only capability carrying a status marker. The account system is mid-migration, moving developers off Taobao accounts onto 千问 accounts. Six of the 49 entries are section landing pages carrying nothing but their own title, and a seventh — 应用开发与上架规范, the page that should carry the review criteria — is published with nothing but its title as well.

Announced but unshipped, and the honest gaps. No international surface of any kind has been announced: no English documentation, no non-China storefront found, and no route for a foreign individual developer beyond an email address. No self-service console exists for the industry platform. No SDK download, no versioning scheme for the platform itself, and no published developer licence. And no vendor page we could read states a price, a fee for the platform, a launch date, or the S1's optical specification — the storefront that would answer the first and third sits behind a Taobao login.

What to watch. Three signals would each change this row materially: an English or international developer surface appearing; the Professional Edition SDK becoming self-serve rather than brokered; and any widening of the three display templates into something a developer can lay out. The first would open the platform to everyone reading this page.

In the landscape

Alibaba's Qianwen platform is one of the platforms tracked in the third-party smart-glasses landscape. It is the sharpest illustration of why that map separates build-time from ship-time openness — see how open it is relative to platforms whose gate is a partner list rather than a passport, and how AI works across them, where it stands nearly alone in handing a general-purpose model to third parties instead of reserving it behind a wake word.

Related