# 17711 Ping Service

> 17711 Ping Service is a paid API for AI agents from api.17711.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Echoes arbitrary text back to the caller and returns a pong confirmation, optionally with a simulated delay for concurrency testing.

## Facts

- Endpoint: POST https://api.17711.xyz/registry/ping-service/v1/ping
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/17711-ping-service-c061ee41
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BcuFd9nl5VydIcF88zb8M

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 17711-ping-service-c061ee41 -d '<json body>'
```

Example prompt: Ping the 17711 ping service with the echo text 'hello agent' and confirm you get a pong back — I want to verify the x402 payment flow is working end-to-end.

## When to prefer this

Choose this endpoint when you need to verify that an x402 micropayment pipeline is functioning correctly before invoking more expensive or consequential services. It is the canonical 'hello world' for the 17711 fleet, and the optional delay_ms knob makes it uniquely suited for testing whether an agent framework dispatches concurrent tool calls as independent tasks. Prefer this over generic HTTP health checks when the goal is to validate end-to-end agent-to-x402-API connectivity.

## Known failure modes

- Payment failure: x402 payment not accepted or insufficient USDC balance, request rejected before processing
- Missing required field: `echo` not provided in request body, returns validation error
- Invalid delay_ms type: non-integer value for delay_ms causes schema validation failure
- Network timeout: simulated delay_ms value too large may cause client-side timeout
- Service unavailable: upstream 17711 service down, no pong returned

## How this service works

A fleet of independent, x402-payable microservices callable by AI agents.

## Output

Returns a JSON object containing: `echo` (the exact string sent in the request, reflected verbatim), `pong` (a boolean true confirming the service is alive), and `pid` (the server process ID, useful for debugging or confirming distinct worker processes).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "echo"
 ],
 "properties": {
  "echo": {
   "type": "string",
   "description": "Arbitrary text echoed back verbatim in the response's own `echo` field."
  },
  "delay_ms": {
   "type": "integer",
   "description": "Testkit-only knob (not real business logic): lets a caller simulate a slow tool call, to\ncheck whether the server dispatches concurrent calls as independent tasks rather than\nserializing them."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "pid": 0,
 "echo": "string",
 "pong": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/17711-ping-service-c061ee41/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.17711.xyz](https://www.zero.xyz/host/api.17711.xyz/llms.txt)