# Magnum.ai Twitter v1.1/v2 API

> Magnum.ai Twitter v1.1/v2 API is a paid API for AI agents from magnum-ai-flame.vercel.app, paid per call via x402, $0.12/call, status unknown (last checked 2026-09-14).

Provides access to Twitter API v1.1 and v2 endpoints via a pay-per-call proxy on Base chain

## Facts

- Endpoint: POST https://magnum-ai-flame.vercel.app/api/twitter-v1-1-v2-api
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/magnum-ai-twitter-v1-1-v2-api-16751574
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wEQGGecWApvCY9A3aQvZ9

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 magnum-ai-twitter-v1-1-v2-api-16751574 -d '<json body>'
```

Example prompt: Can you pull the latest tweets from @elonmusk using the Twitter v2 API and show me his most recent 10 posts?

## When to prefer this

Use this endpoint when you need to access Twitter/X data (tweets, user profiles, timelines, search) without managing your own Twitter API credentials, and you are operating in a pay-per-call environment using x402 payments on Base chain. Prefer this over direct Twitter API integration when you want frictionless per-call billing in USDC.

## Known failure modes

- Payment failure on Base chain results in 402 response and no data returned
- Invalid Twitter API parameters may return an error in the result object
- Twitter rate limits may be hit resulting in a 429-style error from the underlying API
- Missing or malformed request body returns a generic error
- Twitter API endpoint unavailability causes upstream failure

## How this service works

Pay-per-call API marketplace with 150 endpoints powered by x402 payments on Base chain.

## Output

Returns a JSON object with a result field containing the Twitter API response data, including tweet content, user metadata, engagement counts, and other fields depending on the specific Twitter endpoint proxied.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "example": {
  "result": {
   "data": "example response"
  }
 },
 "properties": {
  "result": {
   "type": "object",
   "description": "API response data"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/magnum-ai-twitter-v1-1-v2-api-16751574/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from magnum-ai-flame.vercel.app](https://www.zero.xyz/host/magnum-ai-flame.vercel.app/llms.txt)