# Device-Originated x402 Payment Claim Verification: Decision Procedure

> Device-Originated x402 Payment Claim Verification: Decision Procedure is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Returns a blunt, actionable decision procedure for AI agents that need to verify and accept x402 payments carrying IoT/telematics device-originated context rather than agent-originated context.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/device-originated-x402-payment-claim-verificatio
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/device-originated-x402-payment-claim-verification-decision-procedure-ab6aec1b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HWMGMgIVIlYFMH9vfZcI6

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 device-originated-x402-payment-claim-verification-decision-procedure-ab6aec1b
```

Example prompt: I need a step-by-step decision procedure for verifying an x402 payment claim that arrived with telematics device context — specifically for a vehicle automation trigger — not from another agent. Walk me through exactly how to decide whether to accept or reject it.

## When to prefer this

Choose this endpoint when your agent needs to handle x402 payments that originate from IoT devices, vehicle automation systems, or telematics triggers rather than from other agents or humans. It is specifically designed for the device-context verification gap — standard x402 agent verification procedures do not cover device-originated claim structures. Use it when payment metadata contains device event identifiers, sensor data, or telematics context instead of agent wallet/identity context.

## Known failure modes

- Payment not provided or insufficient — returns 402 with payment requirements
- Invalid method (only GET/HEAD/DELETE accepted) — returns 405
- Service temporarily unavailable — handler ok=false with empty brief
- Topic override not recognized — may return generic procedure rather than specialized one
- Network timeout on LLM-backed generation — slower response or fallback to deterministic procedure

## How this service works

Paid agent-facing brief on device-originated x402 payment claim verification: decision procedure for agents accepting payments that arrive with IoT/telematics context (vehicle automation, telematics-triggered micro-payments, device event metadata) instead of agent-originated context. Blunt decision procedure, not marketing.

## Output

A paid brief containing a prose decision procedure ('brief' field) with concrete accept/reject steps tailored to device-originated x402 payment claims with IoT/telematics context. Also returns metadata including the topic, service slug, ISO-8601 generation timestamp, and the generation source (llm, reasoning, or deterministic). Payment confirmation details (payer, transaction hash) are included in the payment object.

## 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": "device-originated x402 payment claim verification: decision procedure 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": "device-originated-x402-payment-claim-verificatio",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "device-originated-x402-payment-claim-verificatio",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/device-originated-x402-payment-claim-verification-decision-procedure-ab6aec1b/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)