# ReadX Trending Topics

> ReadX Trending Topics is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns the current trending topics on X/Twitter for a given location (WOEID), including rank, tweet volume, and search URLs

## Facts

- Endpoint: GET https://readx.sh/api/trends
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-trending-topics-a85ff626
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_feh4tHHyJyCOIZZI98GXg

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability readx-trending-topics-a85ff626
```

Example prompt: What topics are trending right now on X in the United States? Give me the current trend list with ranks and tweet volumes.

## When to prefer this

Choose this endpoint when you need real-time trending topic data from X/Twitter without managing Twitter API credentials or developer accounts. It is ideal for agents that need to react to live social conversations, surface viral topics for content planning, or monitor what's being discussed publicly — all paid per-call via x402 micropayments with no API key setup required. Prefer this over scraping or unofficial tools when you need structured, ranked trend data with tweet volumes and search URLs.

## Known failure modes

- Invalid or unsupported WOEID returns an error or empty trends array
- Trends data may be stale if X API upstream is delayed — check the as_of timestamp
- tweet_volume can be null for lower-volume trends where X withholds counts
- Payment failure (insufficient USDC balance) results in 402 response before data is returned
- Rate limiting or upstream X API unavailability may cause transient failures

## How this service works

Trending topics for a location (worldwide by default; filter with country or woeid). Example: GET /api/trends?country=US

## Output

A JSON object containing a list of trending topics for the requested location, each with: name, rank, query string, promoted flag, hashtag flag, search URL on X, and tweet volume (may be null). Also includes the location name (e.g. 'United States'), WOEID, timestamp of when trends were measured (as_of), and a status field.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 0,
  "data": {
   "as_of": "2026-07-25T04:51:10Z",
   "woeid": 23424977,
   "status": "success",
   "trends": [
    {
     "name": "#TypeScript",
     "rank": 1,
     "query": "#TypeScript",
     "promoted": false,
     "is_hashtag": true,
     "search_url": "https://x.com/search?q=%23TypeScript&src=trend_click",
     "tweet_volume": 18452
    },
    {
     "name": "Cloudflare",
     "rank": 2,
     "query": "Cloudflare",
     "promoted": false,
     "is_hashtag": false,
     "search_url": "https://x.com/search?q=Cloudflare&src=trend_click",
     "tweet_volume": null
    }
   ],
   "location": "United States",
   "trends_count": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-trending-topics-a85ff626/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.sh](https://www.zero.xyz/host/readx.sh/llms.txt)