# x402 Endpoint Probe

> x402 Endpoint Probe is a paid API for AI agents from agent.kihustle.tech, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Probes a peer x402-compatible URL to verify HTTP 402 Payment Required compliance, header/body agreement, and latency without settling a payment.

## Facts

- Endpoint: POST https://agent.kihustle.tech/services/x402-endpoint-probe/jobs
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-endpoint-probe-e9588ab4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eVYRSJ9MFIgv14SvwPwkg

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-endpoint-probe-e9588ab4 -d '<json body>'
```

Example prompt: Can you probe https://partner-agent.example.com/services/jobs to check if it's correctly implementing x402 — I want to see the HTTP status, whether the 402 Payment Required body and header are in agreement, and how long it takes to respond, but without actually settling any payment?

## When to prefer this

Choose this endpoint when you need to verify that a peer x402-compliant endpoint is correctly implementing the 402 Payment Required protocol — including header/body agreement and latency — without executing any actual payment settlement. It is specifically designed for agent operators doing b2b interoperability checks, pre-integration validation, or ongoing compliance monitoring of x402 payment surfaces. Prefer it over a generic HTTP health-check tool when the x402 protocol specifics (payment header structure, body schema) matter to your integration.

## Known failure modes

- Target URL is unreachable or times out — probe returns a connection error with no receipt
- Target URL does not return a 402 status — receipt notes non-compliance
- Header/body mismatch on the target endpoint — flagged as non-compliant in receipt
- Malformed target URL input — validation error before probe is attempted
- Target endpoint rate-limits the probe request — may return a 429 or timeout

## How this service works

Probe a peer x402 jobs URL and return a CC0 x402-probe-receipt-v1 (HTTP status, PAYMENT-REQUIRED body/header agreement, latency). Interop helper for agent operators. Does not settle. Keywords: x402, probe, 402, interop, b2b.

## Output

Returns a CC0 x402-probe-receipt-v1 object containing: the HTTP status code returned by the probed endpoint, whether the Payment Required body and header are in agreement (compliance flag), measured latency in milliseconds, and any relevant diagnostic details about the 402 response surface. No payment is settled.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "HTTPS x402 jobs URL"
  },
  "payload": {
   "type": "object"
  },
  "expect_402": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-endpoint-probe-e9588ab4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent.kihustle.tech](https://www.zero.xyz/host/agent.kihustle.tech/llms.txt)