# Twitter/X API v1 & v2 Proxy (sna4an-mega-v3)

> Twitter/X API v1 & v2 Proxy (sna4an-mega-v3) is a paid API for AI agents from sna4an-mega-v7.vercel.app, paid per call via x402, $0.18/call, status unknown (last checked 2026-11-05).

Proxies Twitter/X API v1 and v2 requests to retrieve social media data such as tweets, user profiles, timelines, and search results

## Facts

- Endpoint: POST https://sna4an-mega-v7.vercel.app/api/twitter-v1-v2?utm_source=zero.xyz
- Price: $0.18/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-05
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-x-api-v1-v2-proxy-sna4an-mega-v3-b76941a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Enx_AOorpQNvmrssMQftS

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 twitter-x-api-v1-v2-proxy-sna4an-mega-v3-b76941a9 -d '<json body>'
```

Example prompt: Can you pull the latest tweets from @elonmusk's timeline and show me his most recent 10 posts along with their engagement stats?

## When to prefer this

Use this endpoint when you need quick, pay-per-call access to Twitter/X data without managing your own Twitter developer credentials or API quota. Best suited for one-off lookups, agent workflows that occasionally need social data, or when you want to avoid Twitter's own API billing complexity. Avoid if you need high-volume scraping or guaranteed schema stability, as this is an undocumented proxy hub.

## Known failure modes

- Empty or missing input parameters may cause 400 or unhandled errors due to empty input schema
- Twitter rate limits on the upstream API may cause 429 responses
- Invalid or suspended Twitter usernames/IDs return not-found errors
- Private or protected accounts return no tweet content
- The endpoint may time out if the upstream Twitter API is slow or unavailable
- No schema documentation makes it unclear which fields are required

## How this service works

Mega API hub - 118 endpoints covering social media, finance, sports, AI, e-commerce, and more

## Output

Returns structured JSON containing tweet objects (text, timestamp, retweet count, like count, author info) or user profile data (username, bio, follower/following counts, verified status) depending on the query type

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/twitter-x-api-v1-v2-proxy-sna4an-mega-v3-b76941a9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sna4an-mega-v7.vercel.app](https://www.zero.xyz/host/sna4an-mega-v7.vercel.app/llms.txt)