Reference

Every route and every setting.

Generated from the software, not written beside it, so what you read matches the build answering your requests.

Your instance's interactive reference. Every route your build registers, with a form to call it from the browser. It lives on your instance, and this page tells you the address.
The route list. The same routes, readable here, without an instance to hand.
Configuration. Every signet.toml key. What a hosted dashboard hides behind a toggle, this names as a line you can read, diff and review.

Docs · the interactive reference

Send requests to your instance.

Every Signet instance serves its own interactive API reference at /api/auth/reference: every route the running build registers, with a form to call each one. It is the same page the better-auth openAPI() plugin serves, rendered by Scalar, built into the binary.

Your instance

The origin your better-auth client already points at. The base path is /api/auth unless you changed it.

Open the reference → See it live on a test instance

Why it lives on the instance and not here. A request sent from this page to your instance would be cross-origin. The Signet binary itself sends no Access-Control-Allow-Origin header, and its origin check refuses any request whose Origin is not base_url or one of [server].trusted_origins. On Signet Cloud the edge in front of your instance answers cross-origin requests only for an origin you have allowed; a self-hosted instance needs its own proxy to do the same. Either way, every customer would have to allow https://signetauth.dev before a reference hosted here could send a single request. On the instance's own origin the reference sends requests exactly as your app would: same cookies, same origin check, nothing to configure. It works on an air-gapped instance with no CDN to reach.

What it covers. The auth wire: sign-up, sign-in, sessions, organizations, API keys, the OAuth and OIDC provider, two-factor, passkeys, SCIM and the rest of what your build registers. The document behind it is at /api/auth/open-api/generate-schema; agents get the same list from /llms-full.txt. The operator API (/admin/v1) is a separate repository contract on /admin-api and is not served by instances. Some operations do not yet describe their request body; those are being filled in release by release, and the page shows what the running build knows.