Glassly Miniapp SDK betaThe SDK is in beta, so its APIs may change before general availability.Developing on Mentra Live? We recommend using the Glassly Bluetooth SDK.The developer tools are available in the Glassly App under Settings → Miniapp Developer Settings.Share feedback with an in-app bug report, on Discord, or by email at [email protected].
Users can enter their own provider API keys in the Glassly App under Settings > API Keys. session.keys reads them, so a miniapp can call a provider directly on the user’s account instead of shipping a key of its own.
Reading keys needs the API_KEYS permission in your manifest. Without it get() rejects with PERMISSION_NOT_DECLARED. session.keys.hasPermission reports whether you declared it.
miniapp.json

​
Readable providers

The phone serves an explicit allowlist. Asking for anything else, including the Soniox transcription key, rejects with INVALID_ARGUMENT.

​
get

Values aren’t cached SDK-side. Re-fetch on retry — after a 401 from the provider, say — to pick up a key the user edited in Settings while your miniapp was running.
Keys are device-local settings. The value travels only across the local bridge between the phone and your background context; it never goes through a Glassly server. Don’t log it, persist it in session.storage, or forward it to your own backend.

​
When to use this instead of session.ai

session.ai is the default for LLM work: it needs no key from the user, the platform pays, and the call stays provider-neutral. Reach for session.keys when you need something session.ai deliberately doesn’t cover — streaming, provider-specific server-side tools, or a provider API that isn’t completions at all, such as ElevenLabs voices or Mapbox tiles.