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

# How monetization works

You can sell items in your game for Silicon without building a payment system, a wallet, or an inventory. Silicon is The Sandbox's platform currency. Players buy it from The Sandbox once and spend it in any game on the platform.

You price each item in Silicon. You decide what the player gets when they own it or use it. Sandbox Studio supplies the store. Xsolla, the commerce partner, keeps balances, inventories, and purchase records through the Sandbox Studio Store API.

## What the platform handles

|              | The platform handles                                                                          | You handle                                           |
| ------------ | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| Currency     | Selling Silicon to players, checkout, and balances                                            | Pricing your items in Silicon                        |
| Store        | The default in-game store: `Shop` and `Inventory` tabs, sign-in, and Get Silicon              | Adding it to your game, and restyling it if you want |
| Items        | Storing items and ownership, draft and live state, and linking each item to you and your game | Creating, describing, and publishing items           |
| Gameplay     | Who owns the item                                                                             | What an item does when a player owns or uses it      |
| Environments | Sandbox payments while you test, and real payments in your published game                     | Testing before you publish                           |

## Key terms

| Term                | Meaning                                                                                                                                    |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Silicon             | The Sandbox's platform currency. Players buy it from The Sandbox and spend it in any game. You price items in Silicon.                     |
| Xsolla              | The payment and commerce provider behind the store. It holds balances, inventories, and purchase records.                                  |
| `Store Manager`     | The editor panel where you create your game ID and create, edit, publish, take down, and delete items. Open it from the main menu.         |
| Game ID             | Your game's identifier in the store. Created the first time you open `Store Manager`. Every item is tied to it.                            |
| Item                | Something a player can buy or claim in your game. Each item has a name, description, price, behaviour, image, and SKU.                     |
| SKU                 | The item's unique code, shown in `Store Manager`. Your game logic uses it to check whether a player owns the item.                         |
| Draft               | An item only you can see and buy, and only in the editor. Players never see drafts.                                                        |
| Live                | A published item that players can see and buy in your published game.                                                                      |
| Inventory           | The items a player owns in your game. It persists across play sessions.                                                                    |
| Category            | What you are selling. The eight categories are on [What you can sell](https://studio-docs.sandbox.game/monetization/what-you-can-sell.md). |
| Behaviour           | How the store handles ownership: Permanent or Temporary. Store Manager labels Temporary as `Consumable`.                                   |
| Monetization skills | The three agent skills shipped with every new project. They teach your agent how to add the store and manage items.                        |

## What your agent already knows

Every new project includes the three monetization skills. There is nothing to install.

| Skill                           | What it gives your agent                                                                                                                                                                                                |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `monetization-store`            | The starting point. How the store, sign-in, environments, and payments work, and which specialist skill to use next.                                                                                                    |
| `monetization-store-components` | The store's source (controller, API client, and UI built on the engine's [UI kit](https://studio-docs.sandbox.game/the-editor/game-ui-kit-widget-reference.md)) and an install script that adds the store to your game. |
| `monetization-store-items`      | How to create, price, edit, publish, take down, and delete items, connect them to gameplay, and test without spending Silicon.                                                                                          |

Your login stays in the editor. The agent creates and manages items through that signed-in session. It never sees or stores your login token.

## What players see

Players can open the store and browse `Shop` without signing in. To buy or claim, they sign in through a popup. The game stays where it was.

Get Silicon opens Xsolla checkout. The player chooses a pack and pays, then returns to the game. They buy an item in one click. Their Silicon balance goes down, and the item appears in `Inventory`.

A permanent item takes effect straight away, and again on later visits. A temporary item waits in `Inventory` until the player uses it. If they do not have enough Silicon, the store offers a top-up.

## Open Store Manager before you add a store

The first visit to `Store Manager` creates your game ID. Your agent cannot create that ID. This is deliberate: a store is never added to a game by accident.

Open `Store Manager` from the main menu once, then ask your agent to add the store. If the agent reports that your game has no ID, open `Store Manager` and ask again. The steps are on [Add the store to your game](https://studio-docs.sandbox.game/monetization/add-the-store.md).

## Practical guidance

Work through the rest of this section in order.

* Open `Store Manager` once, then add the store. [Add the store to your game](https://studio-docs.sandbox.game/monetization/add-the-store.md)
* Choose a category for each item. [What you can sell](https://studio-docs.sandbox.game/monetization/what-you-can-sell.md)
* Create each item and give it an image and a Silicon price. [Create and manage items](https://studio-docs.sandbox.game/monetization/create-and-manage-items.md)
* Describe what the item does so your game can respond. [Connect items to gameplay](https://studio-docs.sandbox.game/monetization/connect-items-to-gameplay.md)
* Buy each item in the editor with sandbox Silicon. [Test purchases without spending Silicon](https://studio-docs.sandbox.game/monetization/test-purchases.md)
* Publish your game, then publish each item. [Publish, take down, and delete items](https://studio-docs.sandbox.game/monetization/publish-take-down-and-delete-items.md)

## Common mistakes

| Mistake                                                                       | What to do instead                                                                                                                                         |
| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Asking the agent to add the store before `Store Manager` exists for this game | Open `Store Manager` once so the game ID exists, then ask again.                                                                                           |
| Expecting a store item to change gameplay on its own                          | The store records who owns it. Wire the effect on [Connect items to gameplay](https://studio-docs.sandbox.game/monetization/connect-items-to-gameplay.md). |


---

# 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://studio-docs.sandbox.game/monetization/how-monetization-works.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.
