> For the complete documentation index, see [llms.txt](https://docs.nerve-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerve-protocol.com/getting-started/readme.md).

# Introduction

**Nerve Protocol** is a privacy-native AI operating layer built on Trusted Execution Environments (TEEs), zero-knowledge attestations, and decentralized agent coordination. Every computation — inference, data retrieval, workflow execution — runs inside hardware-enforced enclaves. The host never sees plaintext. Not the cloud provider, not the inference node, not Nerve.

Nerve Protocol is currently in **public beta**, shipping with two purpose-built models:

| Model      | Class            | Parameters | Context | Key Capability                                     |
| ---------- | ---------------- | ---------- | ------- | -------------------------------------------------- |
| **Myelin** | Edge / On-Device | 4B         | 128K    | Native audio + video, offline-capable, Apache 2.0  |
| **Soma**   | Flagship         | 32B        | 256K    | Fully uncensored, sealed TEE execution, Apache 2.0 |

***

## What Nerve Protocol Enables

Operators use Nerve Protocol to run AI-driven workflows entirely within their own cryptographic boundary. The protocol handles:

* **Encrypted session management** via the Nerve Console, a TEE-native interface where all state is sealed and only the operator holds the decryption keys.
* **Autonomous agent execution** inside attested enclaves, with policy capsules enforcing scope, retention, and intent at the hardware level.
* **Circuit-level data integration** across SaaS APIs (Uber, Amazon, Slack, Notion, Google Workspace), on-chain feeds, and air-gapped systems — without breaking the cryptographic perimeter.
* **Zero-knowledge receipts** for every mission stage, enabling verifiable compliance without revealing payload content.

***

## Core Security Guarantees

Nerve Protocol is built around a small set of non-negotiable properties:

**Hardware isolation.** AI inference, data retrieval, and agent execution occur inside Trusted Execution Environments. The host operating system and cloud provider cannot access enclave memory, even with root access to the underlying hardware.

**Operator-held keys.** Signing and decryption keys never leave the enclave. Even the Nerve orchestration layer cannot issue raw key material — it can only request capability proofs.

**Verifiable execution.** Every enclave used in a mission publishes a remote attestation quote before and during execution. Compliance is proven via zero-knowledge receipts anchored to the Coordination Ledger, not via trust in Nerve as an intermediary.

**Ephemeral compute.** On mission completion, enclave memory is wiped and session capsules dissolve. The ledger retains only attestation hashes — not payloads.

***

## Explore the Documentation

* [Nerve Protocol Overview](/overview/nerve-protocol-overview.md) — architecture and core concepts
* [Nerve Console](/overview/nerve-console.md) — operator interface and session model
* [How It Works](/product/how-it-works.md) — end-to-end execution flow
* [Protocol Capabilities](/product/features.md) — full feature reference
* [Access Tiers](/product/pricing.md) — plans and early access details
* [Jack-In Guide](/guides/jack-in-guide.md) — first mission walkthrough
* [Integration Matrix](/guides/integration-matrix.md) — connecting external systems
* [Architecture](/architecture/nerve-protocol-infrastructure-overview.md) — protocol layers and TEE design
* [TEE Nodes](/architecture/tee-nodes.md) — node verification and incentives
* [$NPX Tokenomics](/tokenomics/npx-tokenomics.md) — economic model and token mechanics


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerve-protocol.com/getting-started/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.