> For the complete documentation index, see [llms.txt](https://docs.chaingpt.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chaingpt.org/dev-docs-b2b-saas-api-and-sdk/ai-crypto-news-api-and-sdk-and-rss/rss-reference.md).

# RSS Reference

## ChainGPT AI News Generator RSS Reference

ChainGPT exposes a set of **public, read‑only RSS 2.0 feeds** that surface the latest AI‑driven crypto and blockchain news. Because the feeds are *open to the public*, you can pull them with any HTTP client—no API key, credits, or headers required.

***

### Retention window

Each feed always contains up to **30 days of articles**; older items roll off automatically.

***

### Feed catalogue

| Feed                | URL                                              |
| ------------------- | ------------------------------------------------ |
| **All Crypto**      | `https://app.chaingpt.org/rssfeeds.xml`          |
| **Bitcoin (BTC)**   | `https://app.chaingpt.org/rssfeeds-bitcoin.xml`  |
| **BNB Chain (BNB)** | `https://app.chaingpt.org/rssfeeds-bnb.xml`      |
| **Ethereum (ETH)**  | `https://app.chaingpt.org/rssfeeds-ethereum.xml` |

***

### Quick fetch example

```bash
curl -L https://app.chaingpt.org/rssfeeds.xml
```

The endpoint returns standard RSS 2.0 XML. Parse it with any RSS library or an XML parser in your language of choice.

***

### Best practices

* **Cache intelligently** – the content changes as new articles publish, but the 30‑day cap prevents unbounded growth.
* **Respect intervals** – polling every 5‑10 minutes is plenty for most use‑cases.
* **Filter client‑side** – if you need category or token‑specific filtering beyond the four provided feeds, fetch the general feed and apply your own logic, or switch to the REST API/SDK for granular queries.


---

# 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.chaingpt.org/dev-docs-b2b-saas-api-and-sdk/ai-crypto-news-api-and-sdk-and-rss/rss-reference.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.