# QRBase $SCAN Boostpass NFT Purchase

> QRBase $SCAN Boostpass NFT Purchase is a paid API for AI agents from www.qrbase.xyz, paid per call via x402, $69/call, status unknown (last checked 2026-09-15).

Purchases a Boostpass NFT on the QRBase $SCAN platform for 69 USDC via x402 payment protocol

## Facts

- Endpoint: GET https://www.qrbase.xyz/api/x402/buy-boostpass
- Price: $69/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/qrbase-scan-boostpass-nft-purchase-0f6e10a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_p-4g9sLoZd60ph0_TLvlU

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-boostpass-nft-purchase-0f6e10a0
```

Example prompt: Buy me the $SCAN Boostpass NFT on QRBase — pay the 69 USDC and confirm once the transaction goes through.

## When to prefer this

Use this endpoint when you specifically need to purchase the QRBase $SCAN Boostpass NFT, which grants elevated or boosted access within the QRBase $SCAN ecosystem. This is the only endpoint for acquiring this specific NFT asset for 69 USDC via x402 on Base chain.

## Known failure modes

- Insufficient USDC balance — payment fails with transaction error
- Invalid or missing x402 payment header — 402 Payment Required response
- Network congestion on Base chain causing transaction timeout
- Wallet not authorized or payment facilitator rejects the transaction
- Boostpass already owned — duplicate purchase attempt may fail or be rejected
- Swap transaction failure if USDC routing requires an intermediate swap

## How this service works

Purchase boostpass NFT - 69 USDC

## Output

Returns a confirmation message, the number of tokens received, the USDC amount paid, a send transaction hash, and optionally a swap transaction hash if a token swap was involved in the payment process.

## 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-boostpass-nft-purchase-0f6e10a0/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)