# AIsa Payment Gateway - Twitter User Tweets

> AIsa Payment Gateway - Twitter User Tweets is a paid API for AI agents from pay.lnpay.ai, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).

Retrieve paginated tweets posted by a specific Twitter/X user, sorted by creation date

## Facts

- Endpoint: GET https://pay.lnpay.ai/twitter/user/tweets
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aisa-payment-gateway-twitter-user-tweets-c2b89192
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IUDZg7S5yrYe3hxCdZRQA

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 aisa-payment-gateway-twitter-user-tweets-c2b89192
```

Example prompt: Can you fetch the latest tweets from the Twitter account @elonmusk — skip replies, and start from the first page?

## When to prefer this

Use this endpoint when you need to programmatically retrieve a paginated timeline of tweets from a known Twitter user by their screen name or user ID, especially in automated workflows or agents that monitor or analyze user tweet activity. Prefer this over search-based endpoints when you know the specific account you want.

## Known failure modes

- Invalid or non-existent userName/userId returns an error or empty result
- Both userId and userName omitted causes a missing parameter error
- Invalid cursor value may result in a pagination error or empty page
- Payment failure (402) if USDC balance is insufficient
- Rate limiting or upstream Twitter API errors causing 429 or 503 responses

## How this service works

Retrieve tweets by user name. Sort by created_at. Results are paginated, with each page returning up to 20 tweets.

## Output

A paginated list of up to 20 tweets from the specified user, sorted by creation date (newest first), including tweet text, timestamps, and a cursor for fetching the next page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "cursor": {
   "type": "string",
   "description": "The cursor to paginate through the results. First page is \"\"."
  },
  "userId": {
   "type": "string",
   "description": "user id of the user. userId is recommended, could be more stable and faster than userName. userId and userName are mutually exclusive. If both are provided, userId will be used."
  },
  "userName": {
   "type": "string",
   "description": "screen name of the user. userId and userName are mutually exclusive. If both are provided, userId will be used."
  },
  "includeReplies": {
   "type": "boolean",
   "description": "Whether to include replies in the results. Default is False."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aisa-payment-gateway-twitter-user-tweets-c2b89192/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pay.lnpay.ai](https://www.zero.xyz/host/pay.lnpay.ai/llms.txt)