> For the complete documentation index, see [llms.txt](https://docs.bellsight.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bellsight.xyz/bellsight/bellsight-sns-api/namespaces.md).

# Namespaces

## Create a namespace <a href="#create-a-namespace" id="create-a-namespace"></a>

![](https://docs.satsnames.org/~gitbook/image?url=https%3A%2F%2F2381352238-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F8HLCZlJ7Ep94FnlQr8aR%252Fuploads%252FJtMnZFnE61skrmBn6nhQ%252FTwitter%2520post%2520-%25201.png%3Falt%3Dmedia%26token%3Dec7a7037-d90f-406c-b77a-1e44ab45086a\&width=768\&dpr=4\&quality=100\&sign=3fbedcc4\&sv=1)

Here are few reasons to inscribe a namespace operation for your community:

* Help indexers and marketplaces "find" your namespace.
* Include a description so inscribers know the purpose of the namespace.
* Include a nice avatar or logo for marketplaces.

A few other important details about namespaces:

* Like names, namespaces (specifically the `ns` value) are globally unique, and the first inscription of any namespace is the only valid instance. First is first.
* The namespace inscription does not add, or remove, or limit anything related to how others inscribe names.
* You can inscribe any SNS name, on any namespace, before the namespace inscription has been created.
* No special permissions are given to the namespace inscription holder.
* Namespace inscriptions have no speculative or secondary market value.

## Namespace operation <a href="#namespace-operation" id="namespace-operation"></a>

Copy

```
{
    "p": "sns",
    "op": "ns",
    "ns": "bel",
    "about": "Names on Bellscoin. First is first.",
    "avatar": "6373fce7c218e344d78e6c1802651ee1557eb6ebd2292b2ba24d449792227869i0",
}
```

| Key    | Required? | Description                                                                                          |
| ------ | --------- | ---------------------------------------------------------------------------------------------------- |
| p      | Yes       | Helps indexers identify the SNS protocol                                                             |
| op     | Yes       | New namespace operation                                                                              |
| ns     | Yes       | Defines the namespace, for example `sats` defines the .sats namespace. Do not include the period `.` |
| about  | No        | A short description. Aim for under 50 characters.                                                    |
| avatar | No        | A logo or image symbolizing the namespace. Use Inscription ID.                                       |

Do not include the period, or dot, in the operation.

You're welcome to put any UTF-8 character in your namespace but we recommend keeping things simple. Emoji, rare unicode characters, etc. are probably a bad idea and may have poor support by indexers or marketplaces.

## ⚠️ Registration limitations <a href="#registration-limitations" id="registration-limitations"></a>

These rules apply to all namespaces and names:

* Only the first instance of each name/namespace is valid.
* Only one name operation per ordinal inscription.
* Any UTF-8 character is valid.
* Capitalization does not matter. All names/namespaces will be indexed as lowercase.
* No spaces are permitted within a name.


---

# 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:

```
GET https://docs.bellsight.xyz/bellsight/bellsight-sns-api/namespaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.