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

# Track X accounts

Add public X accounts to receive the contract addresses they post, alongside your selected Telegram groups. **No X sign-in is needed.**

## Add an account

1. Open **Options → X accounts** in the bot, or send `/x`.
2. Tap **Add account** and send an `@handle` or an X profile link.
3. Check the name and handle, then tap **Add account** to confirm.

Kyela starts with new posts. It does not fill your inbox with the account's old calls. You can select up to ten accounts initially.

## Choose what matters

Tap an account to **Make priority**, turn priority off, or **Remove account**. Priority mentions alert immediately outside your quiet hours. Other mentions follow your **Notifications** settings. Choose **Every new address now** if you do not want to wait for a digest.

Quiet hours, pause, repeat suppression and history retention apply to your whole inbox. Removing an X account stops its future alerts and withdraws its unsent items. Cards already delivered can remain in Telegram.

## What appears

Only supported addresses in that account's own public posts and replies are included. Other people's replies, reposts, quoted posts and addresses visible only in images or video are excluded. A ticker without an address is not enough.

Cards identify the X author and original post time. **Open X post** takes you to the source. Token name, market cap, volume and price appear when the same address lookup used for Telegram cards can identify them. The full CA is copyable; GMGN and Basedbot keep the usual Kyela referral links.

An address remains unverified. A post is not proof that its author recommends buying it.

## Timing and connection

**X checking continues when the Mini App is closed.** Your Telegram groups still use the reader on your device; your Telegram credentials stay there.

X checks usually run about once a minute, with longer waits during busy periods or source problems. Open an account to see its last successful check. Temporary failures retry automatically without sending repeated connection notices.

This feature uses FxEmbed's free public source. It can delay or omit posts and cannot guarantee complete recovery, edit detection or deletion recall. After a gap, Kyela checks the recent posts available, up to 24 hours old. Older recovered mentions are grouped instead of presented as fresh calls. An account that becomes protected is not supported.

Your selected accounts and inbox belong to you. Public posts can be retrieved once for multiple people who independently selected the same public account; private Telegram records and other customers' watchlists are never shared by this feature.

For help, contact [@kyela\_inbox on X](https://x.com/kyela_inbox). Do not send login details or private group messages.


---

# 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://kyela-inbox.gitbook.io/kyela-inbox-docs/x-accounts.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.