From sign-up to production
Start with getting started, then pick the guide for each kind of app you have. Every snippet uses @anchring/auth; the full reference is the SDK README.
Start with getting started, then pick the guide for each kind of app you have. Every snippet uses @anchring/auth; the full reference is the SDK README.
Your account and your sign-in setup, by hand or by your coding agent.
An account, a sign-in setup with a test and a production environment, and your first apps registered.
Your coding agent set up with the MCP server and rule files, so the integration comes out right the first time.
One guide per kind of app: browser, API, command line, service, MCP server.
A browser app that signs users in with passkeys and calls your API with a fresh token.
An API that verifies tokens offline and checks roles and permissions on each route.
A command-line tool that signs in through the browser and keeps its tokens; personal access tokens for CI.
A backend service that calls your API with a token of its own, within the ceilings you set.
An MCP server that AI clients call as the signed-in user, within the scopes you allow.
Webhooks, feature flags, support access and support chat, all read from the same token.
Your own database kept in step with users, sessions and organisations through verified, deduplicated events.
Features switched on by plan, organisation, role or percentage, read offline from the token in your API and your UI.
Support that opens your app as a user, with a reason, a time limit, a ceiling on its permissions and an audit trail.
A chat widget on your site and in your app, answered from the dashboard's inbox or by your AI agent first.
From test to production, and your users out again whenever you want them.
Your users imported, apps and settings promoted, production ids in your config and, if you like, a custom domain.
A file with your users, their logins, organisations and roles that Anchr.ing or Auth0 imports.
The SDK reference lists every option, error and token type of @anchring/auth.