# AIsa Payment Gateway - Tweet Replies Fetcher

> AIsa Payment Gateway - Tweet Replies Fetcher 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).

Retrieves paginated replies to a specific tweet by tweet ID, ordered by reply time descending

## Facts

- Endpoint: GET https://pay.lnpay.ai/twitter/tweet/replies
- 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-tweet-replies-fetcher-f82a9d0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_U4L_JcPBMEunxQNNOS3_W

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-tweet-replies-fetcher-f82a9d0f
```

Example prompt: Can you fetch me the replies to tweet ID 1846987139428634858, starting from the beginning — I want the first page of replies and then we can page through more if needed.

## When to prefer this

Use this endpoint when you need to retrieve paginated replies to a specific original tweet or the first tweet in a thread, with optional time range filtering. Prefer this over general search endpoints when you have a known tweet ID and want structured, paginated reply retrieval ordered by recency. Best for social listening, engagement analysis, or thread exploration on Twitter/X.

## Known failure modes

- Invalid or non-existent tweet ID returns empty results or error
- Providing a reply tweet ID instead of an original/first-thread tweet causes unexpected results
- Invalid cursor string causes pagination failure
- sinceTime or untilTime outside valid range may return empty set
- Rate limit exceeded returns payment or access error
- Tweet may be deleted or unavailable, returning empty results

## How this service works

Get tweet replies by tweet id. Each page returns up to 20 replies (Sometimes less than 20, because we will filter out ads or other not tweets). Use cursor for pagination. Order by reply time desc

## Output

Returns up to 20 tweet replies per page for the given tweet ID, ordered by reply time descending. Includes a cursor value for fetching the next page. Ads and non-tweet content are filtered out. Response includes reply content, metadata, and pagination cursor.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "tweetId"
 ],
 "properties": {
  "cursor": {
   "type": "string",
   "description": "The cursor to paginate through the results. First page is \"\"."
  },
  "tweetId": {
   "type": "string",
   "description": "The tweet ID to get. Must be an original tweet (not a reply to another tweet) and should be the first tweet in a thread. eg. 1846987139428634858"
  },
  "sinceTime": {
   "type": "integer",
   "description": "On or after a specified unix timestamp in seconds."
  },
  "untilTime": {
   "type": "integer",
   "description": "Before a specified unix timestamp in seconds."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aisa-payment-gateway-tweet-replies-fetcher-f82a9d0f/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)