# PayWeave Twitter – Tweet Lookup by ID

> PayWeave Twitter – Tweet Lookup by ID is a paid API for AI agents from twitter.payweave.services, paid per call via x402, $0.000266/call, status unknown (last checked 2026-09-14).

Fetches full tweet data for up to 50 tweets by their numeric IDs via a pay-per-call API.

## Facts

- Endpoint: POST https://twitter.payweave.services/tweets
- Price: $0.000266/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payweave-twitter-tweet-lookup-by-id-cb5dc5f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9nDpr2qVlNw9q3xD2XMxG

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 payweave-twitter-tweet-lookup-by-id-cb5dc5f3 -d '<json body>'
```

Example prompt: Can you look up the tweets with IDs 1234567890123456789 and 9876543210987654321 and tell me what they say?

## When to prefer this

Use this endpoint when you have specific tweet IDs and need to hydrate them into full tweet objects — ideal for enriching datasets, verifying specific tweets, or retrieving content for known tweet references. Prefer this over search-based endpoints when you already know the exact IDs you need.

## Known failure modes

- Invalid or non-numeric tweet ID returns an error or empty result
- Tweet deleted or suspended returns not-found response
- Exceeding 50 IDs per call may result in rejection or truncation
- Payment failure or insufficient USDC balance blocks the request
- Rate limiting or API quota exhaustion from the upstream Twitter API

## How this service works

X/Twitter data — tweets, users, communities, lists, articles, and trends.

## Output

Returns structured tweet objects for each requested ID, including tweet text, author, timestamps, engagement metrics, and any associated metadata provided by the Twitter API.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ids": {
   "anyOf": [
    {
     "type": "array",
     "items": {
      "type": "string",
      "pattern": "^\\d+$",
      "description": "Numeric ID string"
     }
    },
    {
     "type": "string"
    }
   ],
   "description": "Tweet IDs to look up: either an array of numeric ID strings or a comma-separated string. Max 50."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payweave-twitter-tweet-lookup-by-id-cb5dc5f3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twitter.payweave.services](https://www.zero.xyz/host/twitter.payweave.services/llms.txt)