# x402-tools Payload Seal Diagnostic

> x402-tools Payload Seal Diagnostic is a paid API for AI agents from openclawproductions.com, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-12).

Returns a paid diagnostic JSON payload (SKU: payloadseal) to verify x402 micropayment flow and eip3009 authorization mechanics via the OpenX402 facilitator.

## Facts

- Endpoint: GET https://openclawproductions.com/api/v1/payloadseal?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-tools-payload-seal-diagnostic-28cdce84
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dhBwBVoFAtPnO2hNTv8uq

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-tools-payload-seal-diagnostic-28cdce84
```

Example prompt: Run the Payload Seal diagnostic on OpenX402 to confirm my x402 micropayment integration is working correctly — I need to see the paid JSON response come back after the $0.20 USDC charge clears.

## When to prefer this

Choose this endpoint when you need to verify that an x402 micropayment integration — specifically eip3009-based USDC authorization via the OpenX402 facilitator — is working end to end. It is the canonical diagnostic SKU for testing payment gating: it reliably returns HTTP 402 with structured eip3009 extras on unpaid requests and a known JSON payload on successful payment, making it ideal for integration testing, debugging facilitator configuration, or confirming settlement flows.

## Known failure modes

- HTTP 402 returned when payment header is absent or invalid — response includes eip3009 extras describing required payment
- Payment sent through unsupported facilitator (non-OpenX402) will not unlock the endpoint
- Malformed eip3009 authorization causes payment rejection and 402 loop
- Network or USDC settlement delay may cause transient 402 even after payment intent
- Invalid or missing 'properties' query parameter may return error or empty diagnostic

## How this service works

Paid x402 diagnostics. Unpaid paid-SKU requests return HTTP 402 with eip3009 extras. Facilitator: OpenX402 only.

## Output

A JSON object containing the SKU identifier ('payloadseal'), a human-readable title ('Payload Seal'), the price ('$0.20'), and a diagnostic note confirming the paid shape. Unpaid requests return HTTP 402 with eip3009-formatted payment requirement extras instead.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sku": "payloadseal",
  "note": "Example paid JSON shape. Not a live settle.",
  "price": "$0.20",
  "title": "Payload Seal"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-tools-payload-seal-diagnostic-28cdce84/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from openclawproductions.com](https://www.zero.xyz/host/openclawproductions.com/llms.txt)