# x402.fuchss.app — x402 Payment Trace

> x402.fuchss.app — x402 Payment Trace is a paid API for AI agents from x402.fuchss.app, paid per call via x402, $0.011673/call, status unknown (last checked 2026-09-14).

Traces and decodes an on-chain USDC payment transaction to verify it was a valid x402 protocol settlement, returning compliance and settlement details.

## Facts

- Endpoint: POST https://x402.fuchss.app/v1/x402-payment-trace
- Price: $0.011673/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-fuchss-app-x402-payment-trace-37edc2f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qKgcB2WFe4VOD6-Ux2XBN

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-fuchss-app-x402-payment-trace-37edc2f0 -d '<json body>'
```

Example prompt: Can you trace this x402 payment transaction for me — the hash is 0xabc123...def456 on base-mainnet — and confirm it was a valid settlement for https://api.example.com/my-resource?

## When to prefer this

Use this endpoint when you need to verify or audit a specific on-chain USDC transaction to confirm it was a legitimate x402 protocol payment — for example, to reconcile payments, investigate disputes, or validate that a particular tx hash corresponds to a specific API resource. Prefer this over generic blockchain explorers when you need x402-specific compliance and envelope validation rather than raw transaction data.

## Known failure modes

- Invalid or malformed txHash returns a 4xx error
- Transaction not found on specified network returns not-found error
- Transaction exists but is not an x402 payment returns non-compliant result
- Network slug mismatch causes lookup on wrong chain
- Service itself costs $0.017624 USDC per call via x402 — missing payment returns 402
- hintResource URL mismatch flagged in response but not a hard failure

## How this service works

Know before you pay: deterministic trust scores (0-100) for 100,000+ x402 endpoints, backed by continuous probes and on-chain settlement data.

## Output

Returns a structured object with on-chain payment trace data including x402 envelope compliance status, verified settlement amount in USDC, matched resource URL, network details, and any detected anomalies or protocol violations for the given transaction.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "model": "llama-3.3-70b",
  "route": {
   "knownTo": [
    "cdp"
   ],
   "reseller": "x402.fuchss.app",
   "x402Resource": "https://x402.fuchss.app/v1/x402-trust",
   "ourLedgerMatch": true
  },
  "trace": {
   "txHash": "0x384c5adf64e87fadc0b176005c49051cdc192d5c28b0158c05c3e9251a01d556",
   "gasUsed": "85000",
   "blockNumber": 12345678
  },
  "txHash": "0x384c5adf64e87fadc0b176005c49051cdc192d5c28b0158c05c3e9251a01d556",
  "network": "base-mainnet",
  "payment": {
   "payee": "0xbBECBE90F28632a9d52ed67b33b43767b8c89285",
   "payer": "0x1e82de8B9d2b12b86b2E11EAC29A36140543C451",
   "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "settled": true,
   "amountUsd": "0.005",
   "selectorUsed": "transferWithAuthorization"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-fuchss-app-x402-payment-trace-37edc2f0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.fuchss.app](https://www.zero.xyz/host/x402.fuchss.app/llms.txt)