> 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-district/buying-an-office.md).

# Buying an Office

One flat price, paid once. You own it — there is no rent and nothing to renew.

Every office in the district costs the same, and you pay it once.

| The deal                          | What it is                        |
| --------------------------------- | --------------------------------- |
| Price                             | **100,000 $DEFUND**               |
| Applies to                        | Every office in the district      |
| More expensive in the good towers | No                                |
| More expensive higher up          | No                                |
| Renews                            | Never — there is nothing to renew |

## Why every address costs the same

Your output is decided entirely by what you put **inside** the office. A suite on the top floor of Perpetual High and a shed in The Trenches, fitted with the same desks, the same staff and the same servers, produce exactly the same points.

So the address is a free choice. Pick the view, the silhouette and the reputation you want to trade under — none of it will ever cost you a point of production.

## What the price is worth

100,000 $DEFUND is set so that an office runs to about **$10 at a $100,000 market cap**.

## Budgeting for it

The office is only the entry fee. An empty office produces almost nothing, so plan for the first income chain in the same breath: one terminal, one trader and one server cluster together come to **185,000 $DEFUND**, nearly three times the office itself.

| To be trading on day one |        Cost |
| ------------------------ | ----------: |
| Office                   |     100,000 |
| First income chain       |     185,000 |
| **Total**                | **285,000** |

{% hint style="warning" %}
If you cannot afford something, the purchase is simply refused. There is no debt in this game and no way to go negative.
{% endhint %}

## Who is already there

An office is either **available** or **taken**. Taken ones belong to another player and cannot be bought out from under them; available ones are yours for the flat price the moment you click.

{% hint style="info" %}
A resale market between players is on the way, so an office you buy today will be something you can pass on later.
{% endhint %}

![How an address becomes an office number](https://3552858075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGyJ2fCw8mpbx6YAYcG8z%2Fuploads%2F2yosrDMi7W3HHtZ9JMl6%2Ffig-04-addressing.svg?alt=media)

Office numbers run in one continuous range across all seven buildings, so a number on its own tells you the tower, the floor and the suite.


---

# 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://degen-capital-1.gitbook.io/degen-capital-docs/degen-capital/the-district/buying-an-office.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.