> 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/your-feed.md). # Read your feed A card tells you that someone posted an address. It is not a recommendation to buy it. ## What is on a card * **Token name and ticker:** shown at the top when they can be identified from the post or an exact-address market lookup. * **Market cap and volume:** grouped with the token and its address. Volume includes its time period. **24h pair volume** means trading volume for the selected pool, not every market for that token. * **CA:** the full address in monospace. Tap it to copy where your Telegram client supports that, or use **Copy CA** below the card. * **Posted by:** the posting account, with a username when available. Bot posts and forwarded context are identified when known. * **Group and time:** where and when the message appeared. * **Network:** shown when the source provides enough information. Otherwise it remains unspecified. * **Context:** a short excerpt in a quote block when the person adds commentary. These are their words, not an AI summary. Address-only posts leave this out. * **MC at post:** the market cap quoted in that message, when it can be matched to the address. This is a source quote, not a live price. Missing or ambiguous figures are left out. * **Additional flags:** priority, caution wording or previous mentions where relevant. **At post** values come from the source message. **Market data** has a separate checked time and may be newer than the call. If only fully diluted valuation is available, it is labelled **FDV**, not market cap. Kyela can look up missing basics through DEX Screener using the public address and chain. Your group names, callers, message text and Telegram sign-in details are not sent with that lookup. Missing details can appear as an update to the same card; they do not delay the initial alert or produce another notification. The card is a snapshot, not a continuously updating price ticker. New, unlisted or ambiguous addresses may have incomplete information. **Lookup: Base ยท source chain not confirmed**, for example, means the lookup found a Base match, but the original post did not establish its chain. Check the address and chain before using a trading tool. An address's format alone cannot tell Kyela whether it belongs to a token, wallet, pool or something else. **Address unverified** means Kyela has not established that. If Telegram hides the author, Kyela cannot reliably name them. A forwarded author's name is separate from the account that posted the message in your group. ## When a bot posts the address Kyela checks who the bot is replying to. If that person can be identified, **Reply to** appears above the bot's name. Without a human reply, Kyela checks the previous two posts in that group. **Earlier post** identifies a person who shared the same address within five minutes. It is supporting context, not proof they triggered the bot or made the first call. Ambiguous matches stay unidentified. These checks happen on your device. A relevant human excerpt is limited to 240 characters; addresses and links inside it are labelled rather than repeated. Unrelated conversation text is not uploaded. Later commentary without a clear link to the address is not attached. Bot names remain labelled as bots; an unknown chain stays unconfirmed. ## Use the buttons The first row has **Copy** and **Open source**. Copy saves the full address to your clipboard; Open source opens the original Telegram message, where you still need access to the group. The second row has **GMGN** and **Basedbot**. GMGN opens the chart link where supported. Basedbot passes the address to [Basedbot in Telegram](https://t.me/based_eth_bot). Telegram may first show its **Start** button. Your settings in that trading bot apply. These links include Kyela's referral codes. Kyela may earn a referral commission on eligible trades through those services. ## Digests and catch-up A digest groups new mentions into one message. If it has more items than fit on the first page, use **View remaining items**, or open **My inbox** in the bot. A **Catch-up digest** contains mentions found after a gap in checking. Their original timestamps matter: they are not necessarily new calls. ## Why a post might not appear Kyela reads supported addresses in text, captions and recognised links. It does not read addresses inside images, voice notes or videos. A ticker without an address is not enough. A repeated address may be suppressed, a caller filter may exclude it, or the group may not have been checked while your phone was inactive. [Check a missing mention](/kyela-inbox-docs/help.md#an-address-is-missing). --- # 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://kyela-inbox.gitbook.io/kyela-inbox-docs/your-feed.md?ask=&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.