# x402 Payment Authorization Classification Decision Procedure

> x402 Payment Authorization Classification Decision Procedure is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status down (last checked 2026-10-14).

Returns a blunt AI-generated decision brief classifying payment authorization by separating amount-cap from authority, for agent use in x402 payment flows

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/payment-authorization-classification-separating?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: down
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-payment-authorization-classification-decision-procedure-e0b90a0e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X--nXxPdk3kErVNCkBOq3

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-payment-authorization-classification-decision-procedure-e0b90a0e
```

Example prompt: Give me the blunt decision procedure for classifying payment authorization in x402 — specifically how to separate an amount-cap limit from actual payment authority when my agent is deciding whether to proceed with a transaction.

## When to prefer this

Choose this endpoint when an agent needs a concise, authoritative decision procedure specifically for classifying x402 payment authorization — distinguishing amount-caps from authority constraints — rather than a general payment guide. Useful for agent builders who need blunt, actionable classification logic rather than marketing prose. Particularly relevant if also dealing with Algorand ASA pricing methodology questions in the same context.

## Known failure modes

- Payment not sent or insufficient USDC → 402 Payment Required response
- Invalid method (only GET/HEAD/DELETE accepted) → 405 Method Not Allowed
- Topic override not recognized or too vague → brief may be generic rather than topic-specific
- LLM generation failure → generationSource falls back to deterministic or returns error in result.ok=false
- Network timeout on k2so.wrong.systems → connection error, no response

## How this service works

Decision procedure for autonomous payers. For any proposed x402 payment, it separates two questions that get collapsed into one: how much can this move, and who actually authorized it to move at all. Pay 0.002 USDC to get: (1) amount-cap fit check against the standing envelope, (2) authority-source validation for payee, rail, and context, (3) verdict with three outputs: auto-approve within standing authority, escalate for new authorization, or refuse. Also covers the two failure modes: a cap

## Output

A paid JSON response containing a prose decision-procedure brief (the 'brief' field) that classifies payment authorization concepts — distinguishing amount-caps from authority — for agent consumption. Also includes metadata: service slug, generation source (llm/reasoning/deterministic), model used, ISO-8601 timestamp, and payment confirmation details.

## 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": "x402 authorization-versus-cap classification 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": {
         "type": "string"
… (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": "payment-authorization-classification-separating",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "payment-authorization-classification-separating",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-payment-authorization-classification-decision-procedure-e0b90a0e/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)