> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Verified identity

> Create an account, cryptographic key, and reviewed Legal Identity

A verified-identity workflow turns an application user into an actor who can sign agreements and participate in trusted Neuro workflows.

<Warning>
  No end-to-end identity example is currently available. Account fields, identity providers, review steps, and status delivery depend on the target Neuron.
</Warning>

## Start here

* Use [User onboarding](/neuron-api/guides/user-onboarding) for a trusted backend.
* Use [Browser-based signup](/neuron-api/guides/browser-based-signup) for an interactive browser flow.
* Read [Accounts and Legal Identities](/platform/accounts-and-identities) before storing identity state.
* Check the [account](/neuron-api/api-reference/accounts-and-onboarding/overview), [cryptography](/neuron-api/api-reference/cryptography/overview), and [Legal Identity](/neuron-api/api-reference/legal-identities/overview) operations.

## Workflow

```text theme={null}
Account
  ↓
Email and phone verification where required
  ↓
Cryptographic key
  ↓
Legal Identity application and attachments
  ↓
Review or approval
  ↓
Current Legal Identity
```

## Choose an onboarding method

| Application         | Method                                                          | Credential handling                                                                 |
| ------------------- | --------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| Trusted backend     | [User onboarding](/neuron-api/guides/user-onboarding)           | Backend protects the account-creation secret                                        |
| Browser             | [Browser-based signup](/neuron-api/guides/browser-based-signup) | Browser submits the hosted form and exchanges its session; no API secret is exposed |
| Existing Neuro user | [Sign in with Neuro](/build/sign-in-with-neuro/overview)        | Reuse the user's existing account and identity                                      |

## Data to store

| State                      | Persist?                          |
| -------------------------- | --------------------------------- |
| Account identifier         | Yes                               |
| Verified contact status    | As application state where needed |
| `keyId`                    | Yes                               |
| Identity application state | Yes while pending                 |
| `legalId`                  | Yes after creation                |
| Approval/rejection state   | Yes                               |

## Follow the identity guides

* [Create and verify an account](/neuron-api/guides/creating-an-account)
* [Create cryptographic keys](/neuron-api/guides/creating-cryptographic-keys)
* [Apply for a Legal Identity](/neuron-api/guides/applying-for-a-legal-identity)
* [Get the identity approved](/neuron-api/guides/getting-your-identity-approved)

Before implementing the full sequence, ask the operator which fields are required, which review providers are enabled, and how your application should detect approved and rejected states.