# Introduction

**Nerve Protocol: Your Private Intelligence Stack**

See how deep the rabbit hole goes—then disappear with Nerve. The protocol is a privacy-first intelligence layer built on Trusted Execution Environments (TEEs), zero-knowledge attestations, and decentralized coordination. Operate inside secure enclaves, stay invisible on the open web, and pilot an ecosystem that belongs only to you.

Nerve Protocol enables operators to:

* **Jack in through the Nerve Console**, a TEE-native control deck for encrypted missions.
* **Command autonomous executors** that respect policy guardrails while executing across your stack.
* **Route signal between cloud, chain, and air-gapped tools** without breaking the cryptographic perimeter.
* **Extract insights** that only you can decrypt while collaborators verify progress through zero-knowledge receipts.

Every workflow is sealed inside enclaves, attested on-chain, and orchestrated by privacy-native AI agents.

**Why Choose Nerve Protocol?**

* **Privacy Native by Default:** Your data, models, and keys remain hermetically sealed inside TEEs.
* **Composable Intelligence:** Plug in SaaS tools, on-chain feeds, and air-gapped systems with circuit-level integrations.
* **Operator-Centric UX:** Collaborate with AI copilots in real-time shadow ops while your footprint disappears.
* **Provable Trust:** Remote attestation, zk receipts, and programmable policies prove compliance without revealing payloads.

**Operator Achievements**

✅ Spin up private sessions with Nerve AI and orchestrate missions through the console.\
✅ Wire Uber, Amazon, Slack, Notion, and Google Workspace into the Integration Matrix.\
✅ Convert raw data into encrypted insight feeds that only you can decrypt.\
✅ Dispatch autonomous executors to prep investor decks, coordinate teams, and enforce compliance.\
✅ Share zero-knowledge proofs with auditors or investors—evidence without exposure.

## Explore the Documentation

* [Nerve Protocol Overview](https://archive.nerve-protocol.com/overview/nerve-protocol-overview) – the core concepts.
* [Nerve Console](https://archive.nerve-protocol.com/overview/nerve-console) – operator loop and mission decks.
* [How It Works](https://archive.nerve-protocol.com/product/how-it-works) – step-by-step architecture flow.
* [Feature Grid](https://archive.nerve-protocol.com/product/features) – capabilities across the stack.
* [Access Tiers](https://archive.nerve-protocol.com/product/pricing) – pricing and service levels.
* [Jack-In Guide](https://archive.nerve-protocol.com/guides/jack-in-guide) – launch your first mission.
* [Integration Matrix](https://archive.nerve-protocol.com/guides/integration-matrix) – wire your daily tools.
* [Architecture](https://archive.nerve-protocol.com/architecture/nerve-protocol-infrastructure-overview) – protocol layers and TEE design.
* [Tokenomics](https://archive.nerve-protocol.com/tokenomics/npx-tokenomics) – economic incentives and rewards.

Prefer to let the agents drive? Skip ahead to the [Executor Tactics](https://archive.nerve-protocol.com/architecture/tee-nodes) and deploy autonomous squads.


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.