# QRBase $SCAN Twitter Info Fetch

> QRBase $SCAN Twitter Info Fetch is a paid API for AI agents from www.qrbase.xyz, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-12).

Fetches Twitter-related data for the QRBase $SCAN token by paying 0.1 USDC via the x402 payment protocol

## Facts

- Endpoint: GET https://www.qrbase.xyz/api/x402/qrbase/twitter?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/qrbase-scan-twitter-info-fetch-499f65cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5qIBbaewM5v7AFgDGI-gc

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 qrbase-scan-twitter-info-fetch-499f65cf
```

Example prompt: Can you fetch the Twitter information for the QRBase $SCAN token using the QRBase x402 API — I'm okay paying 0.1 USDC for it?

## When to prefer this

Use this endpoint when you need Twitter-related metadata or social data for the QRBase $SCAN token and are willing to pay 0.1 USDC via the x402 micropayment protocol. Prefer this over manual lookups when automating agent workflows that need on-chain-verified data access.

## Known failure modes

- Payment of 0.1 USDC not received or insufficient — 402 Payment Required response
- Invalid or malformed x402 payment header — authentication failure
- Network or blockchain congestion causing transaction hash to be null
- Endpoint unavailable or QRBase service downtime — 5xx error
- Payment sent but swap transaction fails — swapTransactionHash returns null

## How this service works

Get Twitter - 0.1 USDC

## Output

Returns a JSON object with a message string, tokensReceived amount, usdcAmountPaid confirmation, and optional sendTransactionHash and swapTransactionHash for the on-chain payment used to access the data.

## Example request

```json
{}
```

## Response schema (JSON Schema)

```json
{
 "message": "string",
 "tokensReceived": "string",
 "usdcAmountPaid": "string",
 "sendTransactionHash": "string | null",
 "swapTransactionHash": "string | null"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/qrbase-scan-twitter-info-fetch-499f65cf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.qrbase.xyz](https://www.zero.xyz/host/www.qrbase.xyz/llms.txt)