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

# Walls

Three dividers, and the only things you buy with points.

Walls are four cells wide, sit on the edges between cells, and are the only things in the catalogue with **no effect on your output at all**. They are also the only things you buy with **points** instead of $DEFUND.

The two door walls differ only in which cell the opening sits in.

### Solid Wall

*One seamless four-cell divider*

| Detail         | Value          |
| -------------- | -------------- |
| Price          | **800 points** |
| Space it takes | 4 × 1 cells    |

***

### Door Wall / Left

*Doorway on the second wall cell*

| Detail         | Value            |
| -------------- | ---------------- |
| Price          | **1,200 points** |
| Space it takes | 4 × 1 cells      |

***

### Door Wall / Right

*Doorway on the third wall cell*

| Detail         | Value            |
| -------------- | ---------------- |
| Price          | **1,200 points** |
| Space it takes | 4 × 1 cells      |


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://degen-capital-1.gitbook.io/degen-capital-docs/degen-capital/the-catalogue/walls.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 `build a script that syncs our docs to a CMS` 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.