hypery
Unified API gateway for multiple AI providers, authentication, billing, and team monitoring
- BPM
- 150
- GRADE
- SSS
- LEVEL
- 8
- RELEASES
- 7
- YEARS
- 2024–2026
One Gateway, Many Providers
Hypery started in August 2023, and the domain, hypery.ai, came in April 2024. The public packages came a lot later: the SDK and examples on July 4, 2026, and @hyperyai/sdk on npm the next day at 1.1.5.
It's a single API gateway across multiple AI providers, with authentication, billing and team monitoring. @hyperyai/sdk is a drop-in OAuth 2.0 with PKCE library for React, modeled on Clerk: a HyperyProvider at the root, SignedIn and SignedOut components, a UserButton, auto-refreshing tokens, and structured errors for things like spending limits and insufficient credits.
There are six standalone example apps, with no monorepo tooling and no database: a chat client, an image generator, a React Three Fiber demo, a Vercel AI SDK integration, an AI IDE with MCP tools and WebContainers, and a component gallery. They show two OAuth patterns side by side, frontend PKCE and a backend proxy. I've been building billing and auth plumbing since LitePay in 2005.
Auth For The Gateway
Hypery started in August 2023, and I had the hypery.ai domain by April 2024. The SDK and its examples started on July 4, 2026, and the first release went out the next day at v1.1.5 with the npm publish of @hyperyai/sdk.
Hypery is a unified API gateway across AI providers, with authentication, billing and team monitoring. The SDK is the part developers use: OAuth 2.0 with PKCE, React hooks and components, token auto-refresh, storage you can swap between localStorage, sessionStorage and memory, and structured error handling for spending limits and insufficient credits. I modeled it on Clerk.
@hyperyai/sdk publishes from source, the same way the tishlang packages do. After months of working in the tish monorepo I had a release setup I liked, so I copied it over on day one.
led to
- TULAS2026AI provider gateway