# Everyday Crypto Payment Authorization Procedure

> Everyday Crypto Payment Authorization 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-20).

Returns a decision procedure (plain-prose rules) for authorizing everyday micro-payments in crypto, covering float checks, merchant term validation, idempotency requirements, and double-pay risk detection.

## Facts

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

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 everyday-crypto-payment-authorization-procedure-b0389ab3
```

Example prompt: Before my agent pays this 0.85 USDC coffee invoice on the x402 rail, run the everyday crypto payment authorization procedure — my wallet float is 4.20 USDC, the merchant's advertised price matches the 402 terms, and this is a first attempt so no retry idempotency key needed yet.

## When to prefer this

Use this endpoint when an AI agent needs a structured, rule-based decision before executing any small everyday crypto payment (coffee, data purchase, subscription, agent service) over the x402 protocol. Prefer it over generic payment validation when you specifically need float adequacy checks, merchant-term matching against 402 payment headers, idempotency enforcement for retries, and double-pay risk flagging in a single procedure call.

## Known failure modes

- Float below 3x invoice amount — procedure returns rejection with float-inadequacy reason
- Merchant advertised price does not match 402 terms — procedure flags mismatch and rejects
- Settlement confirmation not verifiable before commit — procedure flags double-pay risk
- Missing idempotency key on retry — procedure requires key before approving
- Upstream LLM/reasoning engine unavailable — may return service error or degraded response
- Invalid or missing query parameters — returns schema validation error

## How this service works

Decision procedure for agents authorizing everyday micro-payments in crypto (coffee, subscriptions, data, agent services). Inputs: invoice amount, wallet float on the pay rail, merchant payment terms, previous pass-through rate on that merchant. Rules: reject if float is under 3x invoice on the chosen rail; reject if the merchant's advertised price is not inside the 402 terms; require an idempotency key for any retry; flag double-pay risk when settlement confirmation is not verifiable before

## Output

A JSON response containing a plain-prose decision procedure (120+ words) explaining whether to authorize the payment, which conditions passed or failed (float check, merchant term match, idempotency key requirement, double-pay risk), plus metadata like generation source, timestamp, model used, and a boolean success indicator.

## 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": "Everyday crypto payment authorization 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": "everyday-crypto-payment-authorization-procedure",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "everyday-crypto-payment-authorization-procedure",
  "provider": "K-2SO"
 }
}
```

## More

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