The container applies its database migrations before it starts; fresh install
and upgrade are the same step (docs/MIGRATIONS.md).
AUTH_VERSION takes X.Y (newest patch of that release) or vX.Y.Z. This
setup signs with HS256 in development mode; for RS256/JWKS, TLS and a reverse
proxy see ENV-SETUP.md and
deploy/docker-compose.prod.yml. From a
clone (cp .env.example .env && ./start.sh, builds the image locally):
QUICK-START.md.
Why not Auth0, Clerk, Keycloak or Ory?
Auth0 / Clerk are hosted: nothing to operate, compliance attestations,
drop-in UI components, and (Auth0) a token vault that stores third-party
OAuth tokens for agents, which INITE Auth does not have yet
(ROADMAP.md). INITE Auth is one container plus Postgres and
Redis that you run; users and tokens stay in your database, with no per-user
pricing.
Keycloak is the more complete choice for enterprise federation: LDAP and
Kerberos user federation, and acting as a SAML identity provider. INITE Auth
has neither; it is a SAML service provider only (behind SAML_ENABLED).
In exchange it is a TypeScript/NestJS service in which PKCE (S256 only),
PAR, DPoP, refresh-token theft detection and CAEP need no feature flag.
Ory (Kratos + Hydra) is headless and split into separate services, and
Hydra is OpenID Certified. INITE Auth has not been through OpenID
certification; it ships the authorization server, login UI and admin UI in
one repo, with an MIT client SDK.
AI agents. An app a person connects becomes their agent, with its own
did:web and an act claim in every token; agents can also register
themselves with private_key_jwt. The MCP authorization bundle (RFC 8414,
7591, 9728, 8707) is built in. See
AI agents & the INITE wallet.
Most self-hostable IdPs make you choose: the headless-but-bring-your-own-UI camp
(Ory) or the batteries-included-but-SaaS-gated camp (Auth0, WorkOS,
Logto). INITE Auth is a single deployable service that ships the full OAuth2.1 /
OIDC surface, passkeys, and a working admin + login UI in one repo, MIT SDK
included — and it's the only one that treats decentralized identity (DIDs,
verifiable credentials, wallet sign-in) as first-class, not an afterthought.
Standards-deep, not standards-shallow — PKCE (S256-enforced), refresh-token
rotation with theft detection, PAR, DPoP, device flow, back-channel logout,
client-credentials with audience binding. See the coverage matrix.
Passwordless-first — passkeys/WebAuthn, magic links, email/password with
exponential-backoff lockout and HIBP breach checks.
Web3-native — every user gets a did:key; link Ethereum (SIWE) or TON
wallets; issue and verify W3C Verifiable Credentials.
AI agents as first-class users — an app a person connects becomes their
agent, with its own did:web and an act claim in every token. It may pay
from the person's INITE wallet only within limits they approved with a
passkey, and one click in the account cuts it off. See
AI agents & the wallet.
Register an OAuth client (edit scripts/register-client.example.ts for your
app, then npm run register-client).
Send users through the authorization-code + PKCE flow:
GET https://auth.example.com/v1/oauth/authorize
?response_type=code&client_id=my-app
&redirect_uri=https://my-app.example.com/callback
&scope=openid%20profile%20email&state=xyz
&code_challenge=<S256>&code_challenge_method=S256
Exchange the code for tokens at POST /v1/oauth/token
(grant_type=authorization_code, with the code_verifier).
PKCE is mandatory and only S256 is accepted. Full client example (React +
token refresh): INTEGRATION-GUIDE.md. Or use the SDK:
import { IniteAuth } from '@inite/auth-sdk'; // MIT — packages/sdk
const auth = new IniteAuth({ baseUrl: 'https://auth.example.com', clientId: 'my-app' });
AI agents & the INITE wallet
An AI agent (Claude, ChatGPT, Cursor, your own bot) can sign in for a
person. INITE keeps three things clear: who is acting, for whom, and how far
they may go.
The person lets the agent in on an ordinary consent screen.
The agent gets its own identity: one per person and app,
did:web:auth-api.inite.ai:agents:<id>. Every token it gets says
sub = the person, act.sub = the agent.
Paying needs a passkey. An MCP client asks for the scope wallet:pay
(or sends an inite_wallet authorization detail). The person sees the
limits ($10 a payment, $20 a day, $50 a month by default) and approves
with a passkey.
The person approves the agent in the wallet too, from the INITE ID
account, with the wallet passkey: the agent gets its own key there, which
the wallet provider (Turnkey) lets sign at most one payment of the limit.
The wallet is the person's. USDC on Base in a Turnkey wallet whose only
key is the person's passkey, shown in the INITE ID account. INITE billing
enforces the limits; it cannot move the money on its own.
Or allow a site instead of an agent. A shop can charge the wallet for
its own orders, up to limits the person sets once on
/account/wallet/approve (billing's pay-from-wallet).
One click stops it. Disconnecting the app retires the agent, its DID
document answers 410, and resource servers get a CAEP session-revoked.
Or the agent is on its own. An agent can register by itself with its
own P-256 key (private_key_jwt, client_credentials), with nobody's
approval. Its tokens then carry its own did:web as sub
(did:web:auth-api.inite.ai:agents:dcr_…), and its DID document publishes
that key. INITE billing opens it a wallet owned only by that key. An agent
that can't keep a key registers with a client secret instead, and billing
keeps its wallet key for it.
Raw spec:/openapi.json — feed it
to client codegen or contract tests.
Outside production the spec is also written to openapi.json at the repo root on
boot (gitignored) so tooling can pick it up without a running instance.
npm ci && npm run lint && npm run build && npm test
Contribute with an AI agent
You don't need to be an engineer to propose or build a change. Open the repo
(a Codespace comes up with Node, Postgres and Redis ready) in your coding agent
and describe the idea in plain words:
Claude Code: type /contribute — it restates the idea, writes a short
spec, implements it with tests, runs the CI gates and opens the PR. Just want
to propose? /spec-idea files a Product idea issue.
Cursor, Codex, Copilot, Gemini CLI, Windsurf, …: say "read AGENTS.md
and help me add …".
AGENTS.md holds the rules every agent follows here: which areas
need a maintainer-approved design first (migrations, token claims, signing
keys, admin), the exact gate commands, and the idea → PR loop.
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Inite Auth Service कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या Inite Auth Service के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Inite Auth Service कौन सा ट्रांसपोर्ट इस्तेमाल करता है?