product

authenticationlogin, sessions, and a full oauth 2.0 providerai gatewayone endpoint fronting 200+ modelsbillingcredits, spending limits, and auto top-upuser managementteams, roles, and user-owned app access

solutions

add login to your ai appdrop-in auth with passkeys and socialmonetize with usage-based billingturn ai usage into metered revenueadd checkout to your ai appone-click buy: login, charge, add-cardoauth provider for your ai productlet other apps sign in with your identitybuild an ai app marketplacepublish, install, and review appsship an ai saas in a weekendauth, billing, and ai in one stackview all solutions
modelspricing>docs

OAuth scopes

Permission scopes for Hypery OAuth apps and API access

Scopes constrain delegated OAuth tokens. First-party session cookies and personal API keys (ak_…) are not scope-gated — they act as the user.

An OAuth app may only mint scopes that appear in both:

  1. The global allowlist below
  2. The scopes registered on that app

AI scopes

ScopeGrants
ai:chatChat completions (/chat/completions, /v1/ai/language-model)
ai:completionsAlias for chat completions
ai:modelsList / inspect models
ai:imagesImage generation, predictions, /v1/ai/image-model
ai:embeddingsPOST /api/v1/embeddings and /v1/ai/embedding-model
ai:audioTTS, transcriptions, realtime session mint

Embeddings and audio do not inherit from ai:chat.

Account & billing

ScopeGrants
readRead-oriented management APIs
writeMutating management APIs (where declared)
billing:readWallet / usage reads
billing:chargePOST /api/v1/usage/charge (Browserbase, realtime settle, Deepgram, …)

billing:charge is required for usage charges — ai:chat / write alone are rejected.

Least privilege

Example for a chat + voice + RAG + browser app:

read write ai:chat ai:embeddings ai:audio ai:images ai:models billing:read billing:charge