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

# Items and trading

Your items live on Solana.

## The market

Buy and sell devices in the game. The market runs on Tensor, so your listings show on Tensor too, and Tensor listings show here.

You set the price and get all of it. The buyer pays the fees.

A listed device can't play. Unlist it to play again.

You can trade devices, power-ups and studio passes. Gems, crowns and invite codes stay on your account.

## Locked items

The training rig and gift devices are locked to your account. You can play with them, but you can't sell or send them. The game shows which items are locked.

## Your wallet

Send tradable items to your own wallet any time. Moving them out of your managed wallet costs standard Solana network fees.

## Coming soon

* Power-ups on the in-game market


---

# 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://beatking.gitbook.io/beatking-docs/rewards/trading.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 `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.
