# x402 Endpoint Validator

> x402 Endpoint Validator is a paid API for AI agents from jp-data-api-production.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Validates that a URL correctly implements the x402 payment protocol by checking HTTP 402 response, payment requirements, and response time

## Facts

- Endpoint: GET https://jp-data-api-production.up.railway.app/verify/x402
- Price: $0.005/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-validator-72eb0b54
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h8cC8-EEAVv5AXgcBMe6u

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-validator-72eb0b54
```

Example prompt: Can you check whether https://api.myservice.com/data is correctly set up as an x402 endpoint — I want to make sure it returns HTTP 402 with valid payment requirements before I list it for sale.

## When to prefer this

Use this endpoint when you need to programmatically verify that a URL is correctly implementing the x402 payment protocol before listing it as a seller, or before committing to pay for it as a buyer. Prefer this over manual inspection when you need measurable response time data and structured validation of all required x402 fields in one call.

## Known failure modes

- URL does not return HTTP 402 (returns 200, 404, 500, etc.) — validation fails with status mismatch
- Missing or malformed payment fields (scheme, network, price, payTo) — partial validation failure with details on which fields are invalid
- URL is unreachable or times out — network error reported
- Non-HTTPS URL provided — rejected by schema validation
- x402 payment structure present but semantically invalid — flagged as not ready

## How this service works

Validate an x402 endpoint: checks that a URL correctly returns HTTP 402 with valid payment requirements (scheme, network, price, payTo), measures response time, and reports readiness. For sellers pre-listing checks and buyers vetting endpoints before paying.

## Output

Returns a validation report confirming whether the URL correctly returns HTTP 402, the parsed payment requirements (scheme, network, price, payTo address), measured response time, and an overall readiness assessment indicating whether the endpoint is correctly configured for x402 payments.

## 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",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "description": "https URL to check"
      }
     }
    }
   },
   "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/x402-endpoint-validator-72eb0b54/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jp-data-api-production.up.railway.app](https://www.zero.xyz/host/jp-data-api-production.up.railway.app/llms.txt)