> ## 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

For the Neuro sandbox, follow the [account and identity quickstart](/neuron-api/quickstart), which uses public account enablement and automatic test-identity approval. The guide below covers the general provider-managed process.

Create an account, a signing key, and an approved Legal Identity so your user can sign agreements and own assets.

## Start from where you are

| What you have now | What to do next |
| - | - |
| No Neuron host or provisioning method | Ask the operator for the host, onboarding method, required fields, review provider, and test-data policy. |
| Existing account credentials | [Sign in with the existing account](/neuron-api/first-request), then continue with key creation. |
| No account and a trusted backend | Follow [User onboarding](/neuron-api/guides/user-onboarding). |
| No account and an interactive browser flow | Follow [Browser-based signup](/neuron-api/guides/browser-based-signup). |
| A current Legal Identity and signing key | Continue to [Agreements](/build/agreements/overview) or [Digital signatures](/build/digital-signatures/overview). |

## Account and identity stages

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

An account answers who controls the session. A Legal Identity identifies the person or organization whose information has been reviewed. Logging in does not create or approve a Legal Identity.

## Choose an onboarding method

| Application | Method | Credential handling |
| - | - | - |
| Trusted backend | [User onboarding](/neuron-api/guides/user-onboarding) | The backend protects the account-creation secret. |
| Browser | [Browser-based signup](/neuron-api/guides/browser-based-signup) | The browser uses the hosted flow; 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. |

## Complete the identity stages

1. [Create and verify an account](/neuron-api/guides/creating-an-account).
2. [Create a cryptographic key](/neuron-api/guides/creating-cryptographic-keys).
3. [Apply for a Legal Identity](/neuron-api/guides/applying-for-a-legal-identity).
4. [Upload each required attachment](/neuron-api/guides/applying-for-a-legal-identity#3-prepare-each-attachment).
5. [Call `ReadyForApproval`](/neuron-api/guides/applying-for-a-legal-identity#5-mark-the-application-ready-for-approval) to start review, unless the sandbox has already approved the identity.
6. [Observe review and approval](/neuron-api/guides/getting-your-identity-approved).

Identity review is asynchronous. Persist the application state and do not continue to a dependent workflow until the identity is approved.

## Keep the resulting state

| State | Why you need it |
| - | - |
| Account identifier | Associate the Neuro account with the correct application user. |
| Verified contact status | Resume any deployment-required contact verification. |
| `keyId` | Select the correct cryptographic key for later actions. |
| Identity application state | Resume and display pending review. |
| `legalId` | Identify the actor in signatures, contracts, and other trusted workflows. |
| Approval or rejection state | Decide whether the next dependent step is allowed. |

## Continue building

<CardGroup cols={2}>
  <Card title="Create an agreement" icon="file-signature" href="/build/agreements/overview">
    Use current Legal Identities and signing keys as contract parties.
  </Card>

  <Card title="Request a signature" icon="signature" href="/build/digital-signatures/overview">
    Sign data or request a signature from a trusted party.
  </Card>
</CardGroup>

Return to [Build with Neuro](/build/overview) to choose your next task.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.