# Problocks USDC Payment Connectivity Ping

> Problocks USDC Payment Connectivity Ping is a paid API for AI agents from x402.problocks.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Verifies that USDC-on-Base payment connectivity is working by returning a JSON pong and UTC timestamp after successful micropayment settlement.

## Facts

- Endpoint: GET https://x402.problocks.io/paid/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/problocks-usdc-payment-connectivity-ping-a6af8245
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5Fm7ePz5Da7OGAZXSPpRW

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 problocks-usdc-payment-connectivity-ping-a6af8245
```

Example prompt: Can you ping the Problocks paid endpoint to confirm my USDC-on-Base payment connectivity is working and show me the UTC timestamp of the successful settlement?

## When to prefer this

Choose this endpoint when you need to verify end-to-end that your x402 USDC-on-Base payment stack is functional — specifically for smoke-testing micropayment rails, validating wallet configuration, or confirming that paid API connectivity is live before running more expensive agent workflows. It is not a substitute for general HTTP health checks; its value lies in the fact that it requires a real USDC micropayment to succeed.

## Known failure modes

- Payment not settled — USDC balance insufficient or Base network congestion causes 402 Payment Required with no pong returned
- Invalid or missing x402 payment header — request rejected before reaching the ping logic
- Network timeout — Base RPC or Problocks infrastructure temporarily unavailable
- Malformed response — edge case where settlement completes but response schema deviates from expected pong structure

## How this service works

Verify payment connectivity with USDC on Base. Returns a JSON pong and UTC timestamp after settlement.

## Output

Returns a JSON object with two fields: 'message' set to the string 'pong', and 'servedAtUtc' containing an ISO 8601 UTC datetime string indicating when the request was served after payment settlement.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "message": "pong",
  "servedAtUtc": "2026-01-01T00:00:00Z"
 }
}
```

## More

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