# boostpass.qrbase.xyz Ping

> boostpass.qrbase.xyz Ping is a paid API for AI agents from boostpass.qrbase.xyz, paid per call via x402, $0.001/call, status down (last checked 2026-10-20).

Sends a paid ping request over the x402 micropayment protocol on Base, returning a confirmation with sender info and payment transaction details

## Facts

- Endpoint: GET https://boostpass.qrbase.xyz/api/x402/ping?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/boostpass-qrbase-xyz-2aa9b831
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2nDSzp0DVQabZkLm94KdX

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 boostpass-qrbase-xyz-2aa9b831
```

Example prompt: Send a paid ping to the boostpass.qrbase.xyz x402 endpoint using 0.001 USDC on Base and tell me if the payment went through, who the sender was, and what transaction hash came back.

## When to prefer this

Use this endpoint when you need to test or demonstrate x402 micropayment protocol connectivity on the Base L2 network at minimal cost (0.001 USDC). Ideal for developers verifying their x402 client setup, wallet integration, or payment facilitator configuration before invoking more expensive paid endpoints.

## Known failure modes

- Insufficient USDC balance — payment rejected, no response body
- Invalid x402 payment header — 402 Payment Required error returned
- Network congestion on Base — timeout or delayed transaction confirmation
- Wrong chain ID — payment sent on wrong network, rejected by facilitator
- x402 version mismatch — incompatible protocol version between client and server

## How this service works

Ping - 0.001 USDC on Base

## Output

Returns a JSON object with: sender (wallet address that paid), message (response string), success (boolean indicating payment and ping success), x402Version (protocol version number), and paymentTransaction (on-chain transaction hash of the 0.001 USDC payment on Base).

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sender": {
   "type": "string"
  },
  "message": {
   "type": "string"
  },
  "success": {
   "type": "boolean"
  },
  "x402Version": {
   "type": "number"
  },
  "paymentTransaction": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boostpass-qrbase-xyz-2aa9b831/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from boostpass.qrbase.xyz](https://www.zero.xyz/host/boostpass.qrbase.xyz/llms.txt)
