Runnable example apps for building on Hypery — OAuth
sign-in with @hyperyai/sdk, AI API
calls, checkout, error/restriction handling, and both OAuth integration
patterns (frontend PKCE and backend proxy).
Each example is a standalone app with its own package.json — cd in,
install, and run. No monorepo tooling, no database (examples persist to
localStorage or a local JSON file).
| App | Port | What it shows |
|---|---|---|
auth-demo |
3003 | @hyperyai/sdk component gallery — sign-in, modals, checkout, hooks |
chat |
3002 | Chat UI on the AI API; backend-proxy OAuth (confidential client) |
fiber |
3006 | React Three Fiber 3D generation with @hyperyai/sdk |
imagine |
3007 | Image generation; backend-proxy OAuth (confidential client) |
justmakeit |
3004 | AI IDE with MCP tools, Monaco, WebContainers; @hyperyai/sdk |
vercel-demo |
3005 | Vercel AI SDK integration with @hyperyai/sdk |
Start with INTEGRATION_PATTERNS.md — it explains the two OAuth patterns (frontend PKCE vs. backend proxy) and when to use each.
Every example talks to a Hypery gateway and needs an OAuth client:
- Sign in to your gateway dashboard and go to Settings → Apps → Create App
- Set the redirect URI to the example's callback (e.g.
http://localhost:3003/callback— each app's.env.examplehas the exact value) and the scopes its README lists - Copy
.env.exampleto.env.localinside the example and fill in your client ID (+ client secret only for the two backend-proxy examples, where it stays server-side)
cd auth-demo # or any example
cp .env.example .env.local # then edit
npm install
npm run dev- Never commit
.env.local(gitignored here; CI fails if any env file appears). - Never put a client secret in a
NEXT_PUBLIC_*variable — those are bundled into the browser. The PKCE examples need no secret at all.
MIT.