# CoinOpSelect Agent Data API — Ping (x402)

> CoinOpSelect Agent Data API — Ping (x402) is a paid API for AI agents from coinop.publicvm.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-21).

Health-check and payment-metadata ping endpoint that confirms the x402 payment gateway is live and returns transaction metadata for a $0.003 USDC on-chain micropayment on Base.

## Facts

- Endpoint: GET https://coinop.publicvm.com/api/v1/ping?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coinopselect-agent-data-api-ping-x402-45ee6ecb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ezlmGUVc6uyeYKy2Kt7tR

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 coinopselect-agent-data-api-ping-x402-45ee6ecb
```

Example prompt: Ping the CoinOpSelect x402 API and confirm it's live — I want to see the payment metadata including the price, recipient wallet, and network before I start making paid data calls.

## When to prefer this

Use this endpoint to verify that the CoinOpSelect x402 API is live and that your on-chain payment credentials are correctly configured before making more expensive or complex paid data calls. It is the lowest-cost way ($0.003 USDC) to validate your wallet setup, payment address, and network configuration on Base. Prefer this over other health-check methods when you specifically need to confirm the x402 micropayment flow end-to-end, not just TCP connectivity.

## Known failure modes

- Service unavailable — no response or non-200 status if the server is down
- Payment not processed — x402 payment header missing or malformed, returns 402 with payment requirements
- Insufficient USDC balance — payment rejected if payer wallet lacks funds
- Wrong network — payment attempted on non-Base network, rejected by gateway
- Rate limiting — too many pings in rapid succession may be throttled

## How this service works

Paid on-chain token, wallet, contract and research data over x402 on Base.

## Output

A JSON object containing the payment transaction ID, asset contract address, payTo wallet address, payer address, the route that was called (/api/v1/ping), a status field ('ok' if healthy), the network ('base'), the price in USD ($0.003), a UTC timestamp, and the atomic USDC amount (3000 units).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "0x0123456789abcdef",
  "asset": "0x..",
  "payTo": "0x..",
  "payer": "0x..",
  "route": "/api/v1/ping",
  "status": "ok",
  "network": "base",
  "priceUsd": "0.003",
  "timestamp": "2026-01-01T00:00:00.000Z",
  "amountAtomic": "3000"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coinopselect-agent-data-api-ping-x402-45ee6ecb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from coinop.publicvm.com](https://www.zero.xyz/host/coinop.publicvm.com/llms.txt)