> For the complete documentation index, see [llms.txt](https://docs.roxin.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roxin.network/how-it-works.md).

# How it works

How Roxin works

## How Roxin Works

Roxin acts as a translation layer between participating game economies.

A simple value transfer can follow three steps.

### 1. Earn

A player earns eligible value inside a game.

This could come from:

* gameplay
* achievements
* events
* purchases
* creation
* other approved activities

### 2. Transfer

The eligible value is represented through the Roxin ecosystem.

The system checks the rules defined by the participating games.

### 3. Use

The destination game decides how that value appears inside its own economy.

For example:

```
Game A
Reward
   ↓
ROXIN
Portable value
   ↓
Game B
Crafting credit
```

The same value does not need to have the same form in every game.

### Developer Control

A participating game can define:

* what value it accepts
* where it accepts value from
* conversion rules
* spending limits
* eligibility requirements
* expiry rules
* local utility
* emergency controls

Roxin is not intended to replace game economies.

It connects them.


---

# 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.roxin.network/how-it-works.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.
