twitter.surf.cascade.fyi – User Tweets

Use this endpoint when you need to programmatically fetch tweets from a specific known Twitter/X username via a paid x402-compatible API, especially in agent workflows where per-call micropayments are acceptable and you need structured tweet data without managing Twitter API credentials directly.

• User not found or handle misspelled — likely returns 404 or empty result
• Payment failure — x402 payment not accepted, returns 402
• Rate limiting or quota exceeded — returns 429
• Account is private or suspended — returns error or empty dataset
• Network/service timeout from upstream Twitter API