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

# Introduction

> An overview of the Neuron API — what it does, who it's for, and how to get started.

## What is the Neuron API?

The Neuron API is the HTTP interface to the **Neuron** — the central server node of the Neuro platform. It lets trusted back-end services interact with the full range of Neuron capabilities without requiring a persistent XMPP connection.

Through the API you can onboard users, authenticate sessions, manage legal identities, create and sign smart contracts, handle tokenized assets and state machines, send XMPP messages, and store encrypted data in the vault. All operations use standard HTTPS requests with JWT bearer token authentication.

<Note>
  The Neuron API is designed for **trusted back-end clients** that can securely store API keys and secrets. If you need browser-based account creation, use the [Create web form](/neuron-api/api-reference/accounts-and-onboarding/create-web-form) endpoint instead.
</Note>

## What you can build

* **Identity-verified applications** — onboard users, apply for legal identities, and attach cryptographic signatures to documents and contracts
* **Smart contract workflows** — create contract templates, propose and collect signatures from multiple parties, and track contract state
* **Token management** — query and annotate tokenized assets linked to smart contracts and state machines
* **Secure messaging** — send text and rich XMPP messages, manage rosters and presence, and register event handlers
* **Encrypted storage** — save private XML data and vault items with masking, search, and shareable links
* **Cryptographic operations** — discover algorithms, create signing keys, and retrieve public keys for validation

## Get started

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/neuron-api/quickstart">
    Make your first API call in minutes.
  </Card>

  <Card title="Authentication" icon="lock" href="/neuron-api/authentication">
    Learn how JWT tokens and HMAC signing work.
  </Card>

  <Card title="API reference" icon="code" href="/neuron-api/api-reference/overview">
    Browse all endpoint groups and operations.
  </Card>

  <Card title="Guides" icon="map" href="/neuron-api/guides/user-onboarding">
    Follow step-by-step integration flows.
  </Card>
</CardGroup>

## How the API is structured

All endpoints are grouped by capability under a common base URL:

```text theme={null}
https://{host}
```

Where `{host}` is the Neuron domain you were issued credentials for.

| Group                                                                                       | Description                                         |
| ------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| [Accounts & onboarding](/neuron-api/api-reference/accounts-and-onboarding/overview)         | Create accounts, verify email/phone, recover access |
| [Authentication & sessions](/neuron-api/api-reference/authentication-and-sessions/overview) | Login, refresh, Quick Login, JWT validation         |
| [Messaging](/neuron-api/api-reference/messaging/overview)                                   | Send messages, manage presence and rosters          |
| [Legal identities](/neuron-api/api-reference/legal-identities/overview)                     | Apply for IDs, attach evidence, request approval    |
| [Contracts](/neuron-api/api-reference/contracts/overview)                                   | Create, propose, and sign smart contracts           |
| [Wallet](/neuron-api/api-reference/wallet/overview)                                         | Query balances, process eDaler URIs, buy/sell flows |
| [Tokens](/neuron-api/api-reference/tokens/overview)                                         | Inspect token metadata, events, and notes           |
| [State machines](/neuron-api/api-reference/state-machines/overview)                         | Query state and generate transition reports         |
| [Storage](/neuron-api/api-reference/storage/overview)                                       | Private XML, encrypted vault, content hosting       |
| [Cryptography](/neuron-api/api-reference/cryptography/overview)                             | Algorithms, signing keys, public keys               |
| [Open intelligence](/neuron-api/api-reference/open-intelligence/overview)                   | Publish and query endpoint intelligence records     |

## Core concepts

* **JWT authentication** — most endpoints require a short-lived JWT obtained via [Login](/neuron-api/api-reference/authentication-and-sessions/login). Tokens must be refreshed before expiry.
* **HMAC signing** — account creation and login use HMAC-signed requests to prove ownership of the API key without transmitting secrets.
* **Pattern matching** — request and response schemas use a readable notation for required/optional fields. See [Pattern matching](/neuron-api/pattern-matching) for a full reference.
* **Federated network** — Neurons are federated. Some operations (e.g. contract signing, Quick Login) can target remote Neurons in the network.

## Reference

* [API basics](/neuron-api/api-basics) — base URL, HTTP methods, request structure
* [Content types](/neuron-api/content-types) — supported formats and encoding
* [Error handling](/neuron-api/error-handling) — status codes and common failure modes
* [Security and transport](/neuron-api/security-and-transport) — TLS, rate limits, and best practices
* [Versioning](/neuron-api/versioning) — how API versions are managed and deprecated