# Public Hybrid ID signup for applications

Users can now create a Hybrid ID at https://hybrid-id.com/signup or select
**Create a Hybrid ID** within your existing Hybrid ID sign-in screen.

For StarQuest and other applications, keep the usual Authorization Code + PKCE
redirect. The signup link stays inside that transaction: after account creation,
the user approves your requested permissions and returns to your registered
callback with the original state. No invitation is required for a new Hybrid ID.

An optional `screen=signup` authorization parameter opens the signup form first.
It is a presentation hint, not a scope or permission. Returning signed-in users
may continue using their existing account. No client-secret or callback changes
are needed.

Open the app's sign-in flow as a top-level browser navigation, not inside an
iframe or embedded demo. Hybrid ID deliberately blocks embedded authentication.
The **Create a Hybrid ID** link on that sign-in screen preserves the app's
transaction and return destination. Sending users to the standalone
`https://hybrid-id.com/signup` page instead starts a separate Hybrid-ID account
flow; it does not carry another app's sign-in transaction.

Identify users by the validated issuer and subject. Signup does not verify email
ownership; do not assume `email_verified` is true or merge accounts by email.
Existing or pending accounts cannot be claimed by signing up with their address.
Those users must use sign-in, recovery, or their original invitation.

Guest linking remains explicit and app-bound through the documented guest API.
Creating an account alone does not link or delete a guest profile. Developer plan
metering and guest capacity remain governed by the existing quota contract.

Hybrid-Chain's separate native registration remains invitation-only. Creating a
Hybrid ID grants no wallet, trading, payment or administrator access.

First and last names are optional at signup. Apps must tolerate missing names.
For later collection and explicit disclosure, use [progressive profiling](https://hybrid-id.com/developers/progressive-profiling). These names are self-declared, not KYC.
