# ReadX Hashtag Tweet Search

> ReadX Hashtag Tweet Search 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).

Searches and returns tweets matching a specific hashtag on X/Twitter, paginating via cursor.

## Facts

- Endpoint: GET https://readx.sh/api/hashtag/:hash
- 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-hashtag-tweet-search-db1d06df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rMjAt_apY2TQ6o2aNhcvD

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-hashtag-tweet-search-db1d06df
```

Example prompt: Can you pull the latest tweets tagged with #typescript from X so I can see what the community is discussing?

## When to prefer this

Use this endpoint when you need tweets specifically filtered by hashtag rather than general keyword search. It is equivalent to searching `#tag` but provides a dedicated, clean interface. Prefer this over the general search endpoint when the input is definitely a hashtag, and over scraping when you need structured JSON output with pagination support.

## Known failure modes

- Invalid or empty hashtag returns an error or empty result set
- Rate limiting or upstream X API restrictions may block requests
- Pagination cursor mismatch or expired cursor returns an error
- Hashtag with no recent activity returns empty tweets array
- Payment failure ($0.01 USDC) prevents the request from being processed

## How this service works

Tweet search for a hashtag. Same as `/api/search?q=%23tag`. Example: GET /api/hashtag/typescript

## Output

A JSON list of tweets matching the given hashtag, including tweet content, author metadata, engagement stats, and a pagination cursor (bottom) to fetch the next page; also includes a has_more flag to indicate whether more results exist.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "tag"
     ],
     "properties": {
      "tag": {
       "type": "string",
       "minLength": 1,
       "description": "Hashtag without the leading #."
      },
      "cursor": {
       "type": "string",
       "description": "Pagination cursor from a previous response's pagination.next_cursor (the conversation endpoint at /api/{name}/tweets/{id} instead takes its own nested reply cursor — see that endpoint)."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-hashtag-tweet-search-db1d06df/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)