# ReadX Pinned Tweet Lookup

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

Returns a user's currently pinned tweet on X/Twitter given their handle

## Facts

- Endpoint: GET https://readx.sh/api/:name/pinned
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-pinned-tweet-lookup-5cf556a4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PCf34lhyrpDOyH-LW-Dkg

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-pinned-tweet-lookup-5cf556a4
```

Example prompt: What tweet does jack have pinned on his X profile right now?

## When to prefer this

Use this endpoint when you need only the pinned tweet for a specific X/Twitter user and don't need full profile or timeline data. It's more targeted and cost-effective than fetching a full profile when the pinned tweet is the sole interest. Prefer it over the full profile endpoint to minimize cost and response payload size.

## Known failure modes

- User has no pinned tweet — returns empty or null result
- Invalid or non-existent X handle — 404 or error response
- Handle contains invalid characters (must match ^[A-Za-z0-9_]+$) — validation error
- Payment failure or insufficient USDC balance — 402 payment required
- Rate limiting or X API unavailability — 5xx error

## How this service works

Just the user's pinned tweet, if any. Example: GET /api/jack/pinned

## Output

A JSON object containing the pinned tweet for the specified X/Twitter user, including tweet text, metadata such as timestamp, engagement counts, and tweet ID. Returns null or an empty result if the user has no pinned tweet.

## 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": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_]+$",
       "minLength": 1,
       "description": "X handle without the leading @ (alphanumeric and underscore)."
      }
     }
    }
   },
   "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-pinned-tweet-lookup-5cf556a4/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)