# twitter.surf.cascade.fyi – User Tweets by Username

> twitter.surf.cascade.fyi – User Tweets by Username is a paid API for AI agents from twitter.surf.cascade.fyi, paid per call via x402, $0.004000/call, status unknown (last checked 2026-09-14).

Fetches the recent tweets posted by a specific Twitter/X user, identified by username in the URL path

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/users/IvanCryptoSlav/tweets
- Price: $0.004000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-surf-cascade-fyi-afee973c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OO0JopwfAe1cxD5afwJaA

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 twitter-surf-cascade-fyi-afee973c
```

Example prompt: Can you pull the latest tweets from @IvanCryptoSlav on Twitter, including any replies they've posted?

## When to prefer this

Use this endpoint when you need to retrieve the tweet history or recent posts of a specific Twitter/X user identified by their handle. Best suited for monitoring a particular account's activity, conducting research on what a user has posted, or aggregating content from a known username. Prefer this over search-based endpoints when you already know the exact username.

## Known failure modes

- User not found – username in path does not exist or has been suspended
- Rate limiting – too many requests in a short period, returning 429
- Payment failure – x402 payment of $0.004 USDC not processed correctly
- Empty result – user exists but has no recent tweets or account is private
- Network timeout – upstream Twitter API unavailable

## How this service works

User tweets

## Output

A list of recent tweets from the specified Twitter/X user, potentially including replies if the include_replies flag is set. Each tweet likely contains the tweet text, timestamp, and associated metadata.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "pathParams": {},
  "queryParams": {
   "include_replies": false
  }
 }
}
```

## 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",
     "properties": {
      "include_replies": {
       "type": "boolean",
       "description": "Include replies"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "data",
  "meta"
 ],
 "properties": {
  "data": {
   "type": "array",
   "items": {
    "type": "unknown"
   }
  },
  "meta": {
   "type": "object",
   "required": [
    "next_cursor",
    "result_count",
    "has_next_page"
   ],
   "properties": {
    "next_cursor": {
     "type": "string"
    },
    "result_count": {
     "type": "number"
    },
    "has_next_page": {
     "type": "boolean"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/twitter-surf-cascade-fyi-afee973c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twitter.surf.cascade.fyi](https://www.zero.xyz/host/twitter.surf.cascade.fyi/llms.txt)