# Sna4an Twitter API (via RapidAPI)

> Sna4an Twitter API (via RapidAPI) is a paid API for AI agents from sna4an-social.vercel.app, paid per call via x402, $0.14/call, status unknown (last checked 2026-09-15).

Fetches Twitter/X social media data by proxying RapidAPI Twitter endpoints with configurable sub-paths and query parameters

## Facts

- Endpoint: POST https://sna4an-social.vercel.app/api/twitter-api-45
- Price: $0.14/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sna4an-twitter-api-via-rapidapi-cae0b03d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u8bZMVs8IWltQ0Doy_QHq

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 sna4an-twitter-api-via-rapidapi-cae0b03d -d '<json body>'
```

Example prompt: Can you pull the latest 20 tweets from @elonmusk's timeline using the Twitter API proxy — use the user-timeline sub-endpoint path with screen_name=elonmusk and count=20 as query params?

## When to prefer this

Use this endpoint when you need Twitter/X data without managing your own RapidAPI key, want pay-per-call pricing at $0.14 USDC via x402, and need flexibility to call different Twitter RapidAPI sub-endpoints by varying the path and params fields.

## Known failure modes

- Invalid or unsupported RapidAPI sub-endpoint path returns an error or empty response
- Rate limiting from the underlying RapidAPI Twitter service
- Twitter account is private or suspended resulting in empty data
- Missing required query parameters for the specified sub-endpoint
- Payment failure via x402 protocol before request is processed

## How this service works

Social media data APIs - YouTube, TikTok, Instagram, Twitter, Medium

## Output

Returns a JSON object containing Twitter data for the requested sub-endpoint, such as user profiles, tweet lists, search results, or engagement metrics — structure varies by the RapidAPI sub-endpoint path specified.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "path": {
   "type": "string",
   "description": "RapidAPI sub-endpoint path"
  },
  "params": {
   "type": "object",
   "description": "Query parameters"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sna4an-twitter-api-via-rapidapi-cae0b03d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sna4an-social.vercel.app](https://www.zero.xyz/host/sna4an-social.vercel.app/llms.txt)