# Agent-Side Network-Degradation Triage for x402 Calls

> Agent-Side Network-Degradation Triage for x402 Calls is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status down (last checked 2026-09-15).

Returns an execute/defer/abort verdict with concrete thresholds after running multi-signal network health checks (RPC reachability, settlement latency, DNS, 402 challenge latency, price drift) before an agent pays via x402.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/agent-side-network-degradation-triage-before-a-p
- Price: $0.002/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-side-network-degradation-triage-for-x402-calls-bfd01299
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EzGUwn1Lsmk4t3RMmU5Q4

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 agent-side-network-degradation-triage-for-x402-calls-bfd01299
```

Example prompt: Before I make this x402 micropayment, run a network-degradation triage check — look at RPC reachability, settlement latency, DNS, 402 challenge latency, and price drift — and tell me whether I should execute, defer, or abort the payment.

## When to prefer this

Use this endpoint when an autonomous agent is about to make an x402 micropayment and needs a pre-flight multi-signal health check to avoid paying through a degraded network path, a broken merchant challenge, or a price-drifted rail. Prefer this over manual checks or simple ping tests when you need a blunt, structured execute/defer/abort decision with concrete thresholds across RPC reachability, settlement latency, DNS, 402 challenge latency, and price drift simultaneously.

## Known failure modes

- Network checks themselves may fail if RPC endpoints are unreachable, returning an error verdict rather than a health signal
- Stale or cached health data could produce an inaccurate verdict if the service has not refreshed recently
- Price drift thresholds may not reflect current on-chain conditions if oracle data is delayed
- LLM-generated briefs may vary in specificity; deterministic generation source is more reliable for strict threshold enforcement
- Payment of $0.002 USDC is required; if the x402 challenge itself is broken, the triage call cannot be completed

## How this service works

Paid agent-facing brief on Agent-side network-degradation triage before a paid x402 call: multi-signal health procedure (RPC reachability, rail settlement latency, DNS resolution, 402 challenge latency, price drift) that returns an execute/defer/abort verdict with concrete thresholds, so an agent does not pay through a degraded path or a broken merchant challenge-0. Blunt decision procedure, not marketing.

## Output

A structured response containing an execute/defer/abort verdict, a prose decision-procedure brief with concrete thresholds, individual health-signal results (RPC reachability, settlement latency, DNS resolution, 402 challenge latency, price drift), a generation source indicator (llm/reasoning/deterministic), an ISO-8601 timestamp, and the service/topic identifiers.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "meta": {
       "enum": [
        "0",
        "1"
       ],
       "type": "string",
       "description": "Set to 1 for free metadata JSON (no payment required)"
      },
      "topic": {
       "type": "string",
       "description": "Optional topic override for the decision procedure"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "Agent-side network-degradation triage before a paid x402 call: multi-s paid response",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "required": [
      "ok",
      "paid",
      "service",
      "provider",
      "result"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "paid": {
       "type": "boolean"
      },
      "result": {
       "type": "object",
       "required": [
        "ok",
        "service"
       ],
       "properties": {
        "ok": {
         "type": "boolean",
         "description": "Handler success"
        },
        "brief": {
         "type": "string",
         "description": "Decision procedure prose for agents"
        },
        "model": {
         "type": "string"
        },
        "topic": {
         "type": "string"
        },
        "service": {
         "type": "string",
         "description": "Service slug"
        },
        "procedure": {
         "type": "string"
        },
        "generatedAt": {
         "type": "string",
         "description": "ISO-8601 timestamp"
        },
        "generationSource": {
         "enum": [
          "llm",
          "reasoning",
          "deterministic"
         ],
         "type": "string"
        }
       }
      },
      "payment": {
       "type": "object",
       "properties": {
        "code": {
         "type": "string"
        },
        "payer": {
         "type": "string"
        },
        "detail": {
         
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true,
  "result": {
   "ok": true,
   "brief": "plain prose decision procedure (120+ words)",
   "model": "deepseek/deepseek-v4-flash-0731",
   "topic": "string topic",
   "service": "agent-side-network-degradation-triage-before-a-p",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "agent-side-network-degradation-triage-before-a-p",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-side-network-degradation-triage-for-x402-calls-bfd01299/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so.wrong.systems](https://www.zero.xyz/host/k2so.wrong.systems/llms.txt)