# DataSieve x402 Payment Ping

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

Smoke-tests an agent's x402 payment stack end-to-end for $0.001, returning payer address, network, and server time with the settlement transaction in the response header.

## Facts

- Endpoint: GET https://api.datasieve.xyz/utils/x402-ping
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/datasieve-x402-payment-ping-cbf38dca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QI1e7MToDh9WLEbuwTlmT

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 datasieve-x402-payment-ping-cbf38dca
```

Example prompt: Run a quick x402 payment smoke test — send a $0.001 USDC ping to the DataSieve test endpoint so I can confirm my wallet and payment client are working before I call anything expensive.

## When to prefer this

Use this endpoint when you need to verify an x402 payment pipeline end-to-end at minimal cost ($0.001) before invoking any expensive paid API. Ideal for onboarding a new wallet, testing a newly integrated x402 client library, or confirming an AI agent's payment stack works in production. Since failed calls are never billed, it is safe for repeated debugging iterations.

## Known failure modes

- Invalid or missing x402 payment header — call is rejected with 402 and no charge
- Insufficient USDC balance — payment fails before settling, no charge
- Malformed wallet address in payment header — server rejects the request
- Network mismatch (wrong chain) — settlement fails, no charge
- Client library misconfiguration — 402 response returned with payment requirements for debugging

## How this service works

Standing infrastructure for ephemeral AI agents, paid per call over x402. Watches, dead-man switches, and multi-agent coordination. No account; wallet as identity.

## Output

Returns a JSON body with the payer wallet address, network name (e.g. base), and server timestamp. The settlement transaction hash is delivered in the X-PAYMENT-RESPONSE header. Failed calls (e.g. bad payment headers) are never billed.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true,
  "payer": "0xabc…",
  "amount": "$0.001",
  "scheme": "exact",
  "network": "eip155:8453",
  "serverTime": "2026-07-12T00:00:00.000Z"
 }
}
```

## More

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