# x402 Ping

> x402 Ping is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.002/call, status unknown (last checked 2026-11-01).

Returns a timestamped 200 response (with optional echo) to verify end-to-end x402 payment flow in a sub-cent test call

## Facts

- Endpoint: GET https://402.com.tr/api/x402/ping?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-ping-1158aa22
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_seTt8mdJndW_SLJfx0Xd6

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 x402-ping-1158aa22
```

Example prompt: Send a quick ping through x402 to confirm my payment client and USDC settlement path are working — echo back the message 'hello402' so I can verify the response round-trip.

## When to prefer this

Use this endpoint as the very first call when setting up or debugging any x402 client integration — it is the cheapest possible ($0.002 USDC) end-to-end payment test available on the network. Prefer it over testing with a real data endpoint to avoid wasting money on failed integration attempts. Also ideal for uptime monitoring of the x402 payment path itself.

## Known failure modes

- 402 Payment Required if no valid x402 payment header is provided
- Payment rejected if USDC balance is insufficient
- Network timeout if Base chain is congested during settlement
- Malformed payment header results in 400 or 402 error
- Rate limiting if called too frequently from the same wallet

## How this service works

The cheapest possible end-to-end x402 purchase: always returns 200 with a timestamp (and echoes an optional message). Use it to verify your x402 client, the payment path and our settlement in one sub-cent call before wiring up a real endpoint — the pattern crawlers and monitors hit most across the network.

## Output

A JSON response with HTTP 200 status containing the current server timestamp and, if the optional 'echo' query parameter was provided, the echoed message. Confirms that the x402 payment was accepted, routed, and settled successfully.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "echo": {
       "type": "string",
       "description": "Optional message to echo back"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-ping-1158aa22/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)