> For the complete documentation index, see [llms.txt](https://docs.kyte.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyte.sh/about/verified.md).

# Verified organization

Kyte is a Verified Organization on X. How to recognise the official Kyte accounts, links and contracts.

Kyte is a **Verified Organization on X**. The official account, [@useKyte](https://x.com/useKyte), carries X's gold checkmark, and the Kyte name, logo and colours are the same everywhere Kyte appears: the website, these docs and X. One consistent identity makes Kyte easy to recognise and hard to impersonate.

{% embed url="<https://twitter.com/useKyte/status/2118066181634695514>" %}
The announcement on X, 5 November 2026
{% endembed %}

### What the gold checkmark means

X gives the gold checkmark only to accounts in its **Verified Organizations** programme, after it confirms that the account belongs to the organisation it names. It is different from the blue checkmark that individual accounts can subscribe to.

<figure><img src="https://996751035-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVsnNtaBRxeClOSpEHWrf%2Fuploads%2Fgit-blob-3afbbb557507c2893e8a32915ad4301659abc34d%2Fx-profile-verified.jpg?alt=media" alt="The @useKyte profile on X, with the gold checkmark next to the Kyte name"><figcaption><p>The official profile: <strong>Kyte</strong>, <strong>@useKyte</strong>, gold checkmark, kyte.sh in the bio</p></figcaption></figure>

| What to look for   | The official Kyte account                     |
| ------------------ | --------------------------------------------- |
| Name               | **Kyte**                                      |
| Handle             | **@useKyte**, spelled exactly like this       |
| Badge              | Gold checkmark next to the name               |
| Avatar             | The Kyte wordmark on the green-to-cyan aurora |
| Website in the bio | **kyte.sh**                                   |

### Official Kyte, in one place

|                 | Official                                     | Notes                                                                                                  |
| --------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Website and app | [kyte.sh](https://kyte.sh)                   | The only web address for the app                                                                       |
| X               | [@useKyte](https://x.com/useKyte)            | Gold checkmark                                                                                         |
| Email           | <contact@kyte.sh>                            | Questions and [security reports](/protocol/security.md)                                                |
| Contracts       | [Deployed addresses](/protocol/addresses.md) | Every address links to the Robinhood Chain explorer                                                    |
| `$KYTE` token   | [The $KYTE token](/token/kyte.md)            | `0x072D88c2F31F568C0F4B8F613692eB489541Ed45`, published only on these docs, on kyte.sh and by @useKyte |

### Check that you are on the real Kyte

{% stepper %}
{% step %}

#### Check the address bar

The app runs on **kyte.sh**. Bookmark it and open it from the bookmark.
{% endstep %}

{% step %}

#### Check the account

Official posts come from **@useKyte** with the gold checkmark. Announcements, the token launch and the `$KYTE` address are posted there.
{% endstep %}

{% step %}

#### Check the contract

Before you confirm, compare the contract your wallet shows with [Deployed addresses](/protocol/addresses.md). Every transaction kyte.sh asks you to sign either calls one of those contracts or is an `approve` on the token you are using, with one of them as the spender.
{% endstep %}

{% step %}

#### Keep your keys to yourself

Kyte is non-custodial. Nobody from Kyte will ever ask for your seed phrase or private key, and the app never needs them.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Seen an account or site that uses the Kyte name and is not listed here? Report it to <contact@kyte.sh> or in a message to [@useKyte](https://x.com/useKyte).
{% endhint %}

### Related

{% content-ref url="/pages/PpaKVkr4va16JUXAFXlH" %}
[Brand, links and contact](/about/brand.md)
{% endcontent-ref %}

{% content-ref url="/pages/Weg2PWJzFovv9c3a4mEi" %}
[Contracts](/protocol/addresses.md)
{% endcontent-ref %}


---

# 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://docs.kyte.sh/about/verified.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.