# X Data Gateway – User Tweets

> X Data Gateway – User Tweets is a paid API for AI agents from x-data-gateway.annushka1190.workers.dev, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-13).

Fetches the recent tweets posted by a specified Twitter/X user by username

## Facts

- Endpoint: GET https://x-data-gateway.annushka1190.workers.dev/tweets/user
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x-data-gateway-user-tweets-7c4e42a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2vzRn0ANnIBHsWc82O9V8

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 x-data-gateway-user-tweets-7c4e42a9
```

Example prompt: Pull the most recent tweets from the X account 'ycombinator' — no @ symbol — and show me what they've been posting.

## When to prefer this

Choose this endpoint when you need real-time tweet data for a specific Twitter/X user without setting up a Twitter developer account or managing API keys. It is especially useful for AI agents that need on-demand, pay-per-request access to public tweet timelines using USDC micropayments via the x402 protocol.

## Known failure modes

- Username not found — returns empty data array or 404-equivalent
- Invalid or missing username parameter — schema validation error
- Account is private/protected — tweets not accessible, empty response
- Rate limit or payment failure via x402 — request blocked
- Cloudflare Worker timeout if upstream Twitter API is slow

## How this service works

Recent posts from a user (newest first) with author and metrics. e.g. GET /tweets/user?username=elonmusk

## Output

Returns a JSON object with a 'data' array of tweet objects (each containing tweet ID and text) and a 'meta' object with a pagination token for fetching more results. The response follows the Twitter API v2 format.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "username"
     ],
     "properties": {
      "username": {
       "type": "string",
       "description": "X handle without @"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x-data-gateway-user-tweets-7c4e42a9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x-data-gateway.annushka1190.workers.dev](https://www.zero.xyz/host/x-data-gateway.annushka1190.workers.dev/llms.txt)