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

# Marketplace: Listings

Sell to the whole server instead of just one person. Put a card up for a set price and anyone can grab it right away. Want people to bid on it instead? Check out Auctions.

## Selling

Use the card's Card ID or card code to say which one you mean.

| Command                                      | What it does                                                                                 |
| -------------------------------------------- | -------------------------------------------------------------------------------------------- |
| `%sell <card id or code> <price> [currency]` | List a card you own for a set price. Any currency works, Gold's the default if you don't say |
| `%unlist <card id or code>`                  | Cancel your listing whenever you want and get the card back right away                       |

`[currency]` takes a name, nickname, or emoji, see the table on Currencies & Daily Rewards.

A couple examples:

* `%sell 12 5000` lists Card ID 12 for 5,000 Gold
* `%sell n7FQHj 40 gems` lists that card for 40 Gems

A card that's already listed (or up for auction) can't be listed a second time until it's sold, bought back, or unlisted. One thing to watch for: the bot won't stop you from also trading or gifting a card while it's up for sale, so it's best not to do that. Unlist it first if you want to hand it off some other way.

Free accounts can have a handful of listings and auctions active at once combined - Tome+ raises that cap, see Currencies & Daily Rewards.

## Buying

| Command               | What it does                                      |
| --------------------- | ------------------------------------------------- |
| `%market`             | Browse what's for sale, 10 per page, newest first |
| `%m [cards\|posters]` | Same thing, filter to just posters if you want    |

Picking something from the list opens it up: show, print number, stars, what kind of art (normal, poster, misprint, or both), price, and its card code, with four buttons:

| Button           | What it does                                    |
| ---------------- | ----------------------------------------------- |
| Star             | Add it to your wishlist                         |
| Magnifying glass | See all the art for that card (same as `%card`) |
| Handshake, Buy   | Buy it right now for the listed price           |
| Back arrow       | Go back to the list                             |

Buying takes the price straight out of your wallet and into the seller's. No haggling, the price is the price. If two people click Buy on the same thing at almost the same time, only one of them actually gets it, the other just gets told it's gone.

You can't buy your own listing.

The [website](https://tomebot.pages.dev/) has the marketplace too, so you can browse and buy without even opening Discord.


---

# 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://studio0.gitbook.io/tome-docs/marketplace-listings.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.
