# AIsa Payment Gateway - Tweet Thread Context

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

Retrieves the full thread context of a tweet, including ancestor and descendant replies, given any tweet ID in the thread.

## Facts

- Endpoint: GET https://pay.lnpay.ai/twitter/tweet/thread
- Price: $0.015/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-thread-context-bf2bd13d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DlFwRJdJmQj9kf4qaFcbQ

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-thread-context-bf2bd13d
```

Example prompt: Can you pull the full thread context for tweet ID 1234567890123456789 — I want to see the original tweet, all the replies leading up to it, and all the replies branching off from it?

## When to prefer this

Use this endpoint when you need to reconstruct a full Twitter/X conversation thread — both the ancestor chain and all descendant replies — from any tweet in that thread. It is preferable when you need the complete context of a discussion, not just direct replies or the original tweet alone.

## Known failure modes

- Invalid or non-existent tweetId returns empty results or error
- Tweet is private/protected and not accessible
- Pagination cursor is invalid or expired
- Rate limiting or payment failure returns 402 or 429 status
- Twitter API downstream outage causes failure

## How this service works

Get the thread context of a tweet. Suppose a tweet thread consists of t1, t2 (replying to t1), t3 (replying to t2), and t4, t5, t6 (all replying to t3). If we provide an API where you input t3 and receive t1, t2, t3, t4, t5, t6. Pagination is supported. The pagination size cannot be set (due to Twitter's limitations), and the data returned per page is not fixed.

## Output

Returns a paginated list of tweets forming the full thread context: ancestors (tweets leading up to the input tweet) and descendants (all replies branching from it). Each page contains a variable number of tweets due to Twitter API limitations, plus a cursor for fetching the next page.

## 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. Can be a reply tweet or a original tweet."
  }
 }
}
```

## More

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