> For the complete documentation index, see [llms.txt](https://somniaexchange.gitbook.io/nia/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://somniaexchange.gitbook.io/nia/game-mechanics/swap-to-earn.md).
# Swap to Earn
Every user begins by minting their very first Chicken with SOMI. This is where the game starts and it immediately tells us that we need to earn Feed tokens. Oh no, our chicken must not go hungry!
### **Earn Feed Points by Swapping**
Feed is a token earned by swapping within the NIA–USDC pair. By feeding your chicken with these tokens, you enable it to lay eggs. Each chicken has its own fertility level and a cooldown period that determines how often it produces eggs. Unlike your very first chicken, all subsequent chickens come with randomly assigned fertility rates at the time of minting.
Now, to discover how we can hatch even more chickens, let’s move into the **Liquidity to Earn** mechanic.
---
# 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://somniaexchange.gitbook.io/nia/game-mechanics/swap-to-earn.md?ask=&goal=
```
`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.