Docs

Pick how you want Quota to fit into your app. Three questions decide which path you walk through.

The product axis in one line

Two integration patterns share the same OAuth flow under the hood and only differ in what Quota gives your app: Sign in with Quota provides identity and credits (Quota replaces NextAuth/Clerk). Connect to Quota Wallet only adds credits to your existing users (your auth stays in place). Pick by whether you already have an auth stack — see questions 2 and 3 below.

01 I just want to try the API

Mint a developer key, point your existing OpenAI / Anthropic / Google SDK at Quota, and run a chat completion. You pay for the usage. No OAuth, no user accounts, no schema changes. About four minutes from zero.

Quickstart — Developer API key

OpenAI-compatible base URL + an sk-quota-… key. Best for prototypes, internal tools, and seeing what Quota does end-to-end.

02 My app already has users

Keep your existing auth (NextAuth, Clerk, Passport, custom — any of them). Add a Connect Quota Wallet button so each user attaches their own AI credit balance. From then on, Quota bills the user, not you.

Connect Quota Wallet

Your auth + Quota credits. The user clicks Connect, you store their token, requests bill their wallet. Plain Express and Next.js.

03 I'm building a new app, no auth yet

Let Quota provide identity and billing in one flow. Users sign in with a Quota account, your app reads the OIDC profile, and every user shows up pre-funded with a small welcome balance. Skip building a user table, password reset, or payment infrastructure.

OIDC + OAuth in one. <QuotaSignInButton /> for Next.js or a 100-line plain Express recipe. PKCE, id_token verification, refresh built in.

The three paths at a glance

Same picker as above, side-by-side, when you want to compare before committing.

Path	Who pays	Bearer on model calls	What Quota provides	You build
Developer API key	Your developer wallet	`sk-quota-…`	Inference + billing	Nothing user-facing — internal tools, prototypes, fixed-price apps
Sign in with Quota	The signed-in user's wallet	`quota_token_…`	Identity + wallet + inference	UI only — no user table, no auth, no payments
Connect Quota Wallet	The connected user's wallet	`quota_token_…`	Wallet + inference	Your own auth + a Connect button

Reference

If you already know which path you're on:

Quickstart

Self-contained walkthrough for all three integration paths. Pick a tab at the top and follow it end to end.

Tokens and actors

The credentials you'll touch — what each one represents, which endpoints they call, which wallet they bill.

Billing modes

Developer, user, sandbox — the ways requests get billed and how to pick.

OpenAI compatibility

Drop-in /v1 endpoint surface, OpenAI SDK config, model routing across providers.

Authentication

API keys, OAuth, sessions, PKCE, OIDC discovery, scopes — the deep-dive reference.

API reference

Every endpoint, every parameter, every response field.