> For the complete documentation index, see [llms.txt](https://docs.neuriio.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neuriio.xyz/trading/feed-and-points.md).

# Feed and Points

## Feed

The **Feed** is where creators and holders talk about the tokens they back.

* **Send $** on any post sends the poster any token you hold on Elysium, straight to their Neuriio wallet.
* Live trades for each token show on its page in **Explore**.

{% hint style="info" %}
Posting to the feed is coming soon. Until then, the feed shows sample posts.
{% endhint %}

## Points

Points reward activity on Neuriio. You earn them by:

* **Trading** launched tokens, on the curve or in their pools.
* **Launching** your own token.

Points are already being counted for every trade and launch. The **Points** panel and a public leaderboard are coming soon. Point rates can change; changes apply going forward only and never remove points you've already earned.

Points are a measure of activity on Neuriio. They are not a token and have no promised value.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neuriio.xyz/trading/feed-and-points.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.