# Agent Data Bench Health Ping

> Agent Data Bench Health Ping is a paid API for AI agents from x402.deepsense.stream, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-20).

Returns a health-check response with service name, ISO timestamp, and epoch milliseconds to verify x402 client connectivity end-to-end.

## Facts

- Endpoint: GET https://x402.deepsense.stream/api/v1/ping?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-data-bench-health-ping-16c437c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wGq25hWj0Eni7tZYhZPYl

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 agent-data-bench-health-ping-16c437c0
```

Example prompt: Ping the Agent Data Bench service to confirm my x402 client is wired up correctly — just give me the health status, service name, and current timestamp.

## When to prefer this

Choose this endpoint when you need the absolute fastest, cheapest way to verify an x402 client is correctly configured end-to-end, or when you need a liveness check with no side effects and no external dependencies. It is not a substitute for a full integration test but is ideal as a smoke test or pipeline gate.

## Known failure modes

- x402 payment failure if client is misconfigured — returns 402 Payment Required before the ping logic runs
- Network timeout if the host is unreachable
- Malformed request if HTTP method is not GET — returns 405 Method Not Allowed

## How this service works

Zero-dependency health ping for agents: returns ok, service name, ISO timestamp and epoch milliseconds. Use it to verify an x402 client end to end in under a millisecond. No upstream, no storage.

## Output

A JSON object containing: a status field set to 'ok', the service name string, the current server time as an ISO 8601 timestamp, and the current epoch time in milliseconds. No upstream dependencies means the response is always sub-millisecond.

## 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"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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/agent-data-bench-health-ping-16c437c0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.deepsense.stream](https://www.zero.xyz/host/x402.deepsense.stream/llms.txt)