# Surf Twitter – User Tweets Lookup

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

Fetches a user's tweets from Twitter/X by user reference, billed via x402 micropayments at $0.004 USDC per call

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/users/%7Bref%7D/tweets
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-09
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/surf-twitter-user-tweets-lookup-9f6d21c6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KSzpk9timdM4dMBimdHP1

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 surf-twitter-user-tweets-lookup-9f6d21c6
```

Example prompt: Can you fetch the latest tweets from @elonmusk's Twitter account? I want to see what he's been posting recently.

## When to prefer this

Use this endpoint when you need pay-per-use, low-friction access to a specific Twitter/X user's tweet history without managing Twitter API credentials directly. Ideal for agents that need occasional tweet lookups and want to pay per call via x402 USDC micropayments rather than maintaining API keys or subscriptions.

## Known failure modes

- Invalid or non-existent user reference returns empty data or 404-equivalent
- Payment failure via x402 micropayment protocol blocks the request
- Rate limits on the underlying Twitter/X API cause upstream errors
- Suspended or private accounts may return no data
- Malformed user reference (e.g. missing @ or incorrect ID format) causes lookup failure

## How this service works

Pay-per-use Twitter/X data API with x402 micropayments.

## Output

A JSON array of tweet objects each containing an ID and text, plus metadata with total result count and a boolean indicating whether more pages are available for pagination.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "id": "123",
    "text": "Hello world"
   }
  ],
  "meta": {
   "result_count": 20,
   "has_next_page": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/surf-twitter-user-tweets-lookup-9f6d21c6/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)