> For the complete documentation index, see [llms.txt](https://docs.kampeni.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kampeni.com/tokenomics-and-governance/in-game-fungible-tokens.md).

# In-Game Fungible Tokens

Along with NFTs for playable characters Kampeni uses a variety of fungible tokens as utility tokens representing different assets, resources, or abstract concepts in the game. These tokens can be earned through gameplay or airdropped. Examples of some of the initial tokens that will be available at the start of the game include:<br>

* **Denari** (Standard in-game currency)
* **Joy** (An asset generated by some characters as a positive externality for groups)
* **Carbon Emissions** (An asset by some characters as a *mostly* negative externality for groups)
* **Golden Dragon Scales** (Expendable asset used in crafting, spell-casting)
* **Crime** (An asset generated by organizations that *mostly* act as a negative externality for characters and organization)

Note: These tokens aren't intended to have value outside the Kampeni game ecosystem.


---

# 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.kampeni.com/tokenomics-and-governance/in-game-fungible-tokens.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.