> 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/create-and-manage-items.md).

# Create and manage items

You can create items by asking your agent or by filling in the form in `Store Manager`. Both write to the same store. Every new item starts as a draft. Players cannot see or buy a draft.

Categories and behaviours are on [What you can sell](https://studio-docs.sandbox.game/monetization/what-you-can-sell.md). The store itself is added on [Add the store to your game](https://studio-docs.sandbox.game/monetization/add-the-store.md).

## Step 1: Create the items with your agent

Describe what you want to sell and what it should do in play. The agent creates the item, sets its behaviour, and wires the effect in the same pass.

```
Add two items to the store. First, a flaming sword: a permanent item that increases base damage, shows flames rising from the blade, and equips automatically on purchase. Second, an apple: a consumable that restores 30 health when used.
```

Use that prompt in a project that already has a weapon and health, or change the sword and the apple to items your game already has.

Your agent can also change the name, description, or Silicon price, and attach an image from your project or from your computer.

## Step 2: Create an item in Store Manager

Open `Store Manager` from the main menu. Select `New item`.

1. Enter a name and a description.
2. Set the price in Silicon, or mark the item as free.
3. Choose `Permanent` or `Consumable`. `Consumable` is the Temporary behaviour.
4. Add an image by URL, or upload a PNG, JPEG, or WebP from your computer. An uploaded image is saved in your game's assets.
5. Confirm.

The item is created as a draft. `Store Manager` lists it with its state and its SKU.

{% hint style="info" %}
*NOTE: An item created in `Store Manager` is in the store and does nothing in play until your game responds to it. Wire it up on* [*Connect items to gameplay*](https://studio-docs.sandbox.game/monetization/connect-items-to-gameplay.md)*.*
{% endhint %}

## Step 3: Review the list

`Store Manager` lists every item with its state, draft or live, and its SKU. Your game uses the SKU to check whether a player owns the item.

{% hint style="info" %}
*TIP: If an item the agent created is missing from the list, select `Refresh`.*
{% endhint %}

## Step 4: Change an item

Select the item in `Store Manager`. Change the name, description, Silicon price, or image, then save.

You can ask your agent to make the same change. Say the item's name and what should be different.

Publishing a draft, taking a live item down, and deleting an item are on [Publish, take down, and delete items](https://studio-docs.sandbox.game/monetization/publish-take-down-and-delete-items.md).

## What You've Done

The items are drafts in your store. An item you described to your agent already has its effect in play. An item you created in `Store Manager` still needs that effect, on [Connect items to gameplay](https://studio-docs.sandbox.game/monetization/connect-items-to-gameplay.md). Buy the drafts in the editor before you publish them, on [Test purchases without spending Silicon](https://studio-docs.sandbox.game/monetization/test-purchases.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/create-and-manage-items.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.
