Skip to main content
Mentra Miniapp SDK betaThe SDK is in beta, so its APIs may change before general availability.To put a miniapp in front of users, host it at an HTTPS URL and share the link, or get it listed in the Mentra Miniapp Store. See Publish your miniapp.Developing on Mentra Live? We recommend using the Mentra Bluetooth SDK.The developer tools are available in the Mentra App under Settings → Miniapp Developer Settings.Share feedback with an in-app bug report, on Discord, or by email at help@mentra.glass.
These APIs are restricted to system miniapps (Mentra AI today). A regular miniapp that calls them gets NOT_PERMITTED. They’re documented here for reference. To make your own miniapp callable, expose actions instead, see Actions.
System miniapps can discover other miniapps, control their lifecycle, invoke the actions those miniapps expose, and use a small set of privileged device controls.

Discover and control miniapps

session.miniapps lists installed miniapps and starts or stops them.
Each MiniappInfo also reports system (the Mentra App build ships this miniapp). Actions declared with "audience": "host" are not listed.

Installing miniapps

session.miniapps.install({url}) installs the miniapp at a miniapp URL, the HTTPS address that serves its miniapp.json. The Mentra App shows no install sheet, so ask the person first. Only a miniapp on the Mentra App’s system list may install; any other caller, a development build included, gets NOT_PERMITTED.
packageName is optional: the package the person agreed to. A URL that serves another one installs nothing and fails with not_a_miniapp. session.hostFeatures.miniappInstall says the Mentra App installs from a URL. Older Mentra Apps don’t advertise it, and answer install with NOT_PERMITTED. The Mentra App installs it as it installs from a link: it fetches miniapp.json, checks the package name against the URL’s domain, registers the URL with Mentra, checks the phone can run the miniapp, and downloads, verifies and installs its bundle. status is installed, opened (it was installed from that URL already, or a newer release of it is) or deferred (the miniapp is running, so its update waits until it stops or the person answers the Mentra App’s update prompt). A failed install rejects with INSTALL_FAILED. Its reason says why: not_a_miniapp, domain_mismatch, archived, needs_newer_app, access_denied, age_restricted, network, cancelled, integrity or signature_invalid. checkInstallCompatibility checks a release’s minHostVersion, sdkVersion and hardwareRequirements against the phone and the paired glasses, and reports what it finds. Only a host or sdk blocker stops an install; a hardware blocker never does. uninstall(packageName) removes a miniapp installed from a miniapp URL; a miniapp the Mentra App bundles, one a workspace manages and a development build stay, with NOT_PERMITTED.

Invoke an action

session.actions.invoke calls an action another miniapp exposed via session.actions.handle. It headless-wakes the target if it’s stopped, runs the handler, and returns the result.
invoke() rejects with { code, message } where code is one of: A thrown handler in the target surfaces its own error message to the caller. The action descriptor returned by session.miniapps.list() includes an optional outputSchema, which describes the structured result for result-aware callers.

Privileged device controls

Wi-Fi ADB (Mentra Live)

session.glasses.setWifiAdbState toggles wireless debugging on Mentra Live. The preference is persisted on the glasses and reapplied at boot (default off). Non-system callers get NOT_PERMITTED.