> For the complete documentation index, see [llms.txt](https://docs.wormbrain.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wormbrain.info/wormbrain.md).
# WormBrain
The worm has 302 neurons. Scientists mapped every wire between them. We copied that map, pointed it at a market, and handed it a FOMO wallet.
Will you be outtraded by a worm? Can a worm get richer than you?
## Start here
Read these four if you are new. Skip ahead if you already like nematodes.
| Page | What you get |
| -------------------------------------------------------------------------- | -------------------------------------------------------------- |
| [What this is](/explore-wormbrain/01-start/what-this-is.md) | The short version. What is the worm. What is us. |
| [Meet C. elegans](/explore-wormbrain/02-the-worm/meet-c-elegans.md) | Why this animal, and why 302 is a magic number |
| [The translation](/explore-wormbrain/03-the-experiment/the-translation.md) | How a price chart becomes a smell, and a crawl becomes a trade |
| [Watch it on FOMO](/explore-wormbrain/01-start/watch-on-fomo.md) | How to follow the wallet like any other trader |
{% hint style="info" %}
We chose how a chart should feel to its nose, and what "crawl forward" should do on FOMO. Everything between those two choices is the published brain system.
{% endhint %}
## Who does what
| The worm | Us |
| ---------------------------------- | ---------------------------------------------------------- |
| 302 named neurons | Writing price, flow, and liquidity onto those neurons |
| The published wiring | Reading forward, reverse, and pause as buy, sell, and wait |
| Decades of lab notes on each cell | Caps, fees, and a cage so a twitch cannot empty the bag |
| Activity spreading through the net | The FOMO wallet, the feed, and these pages |
If a sentence here ever mixes those columns up, trust the table.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.wormbrain.info/wormbrain.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
