# Signal-Gated x402 Spend Execution Procedure

> Signal-Gated x402 Spend Execution Procedure is a paid API for AI agents from k2so-8080.on.ascii.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-20).

Returns a decision procedure for agents to gate x402 micropayments on signal conditions, preventing duplicate spend on repeated events from real-time scanners or price feeds.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/signal-gated-x402-spend-procedure?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signal-gated-x402-spend-execution-procedure-6eea69ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u1jEyYgaKGQrWdDDOBmf8

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 signal-gated-x402-spend-execution-procedure-6eea69ab
```

Example prompt: I'm running a real-time on-chain event scanner that triggers x402 paid API calls when a signal fires — can you give me the decision procedure for signal-gating those payments, including how to deduplicate repeated signals, set per-trigger budget caps, configure cooldown windows, define circuit-breaker thresholds, and decide when to escalate to a human instead of auto-spending?

## When to prefer this

Choose this endpoint when building or auditing an autonomous agent that makes x402 micropayments in response to real-time events (chain scanners, price feeds, event monitors) and needs a governance procedure to prevent duplicate spend, runaway costs, or missing audit trails. It is specifically designed for the x402 payment protocol and covers the full lifecycle from signal definition to human escalation, making it more complete than generic rate-limiting or deduplication guides.

## Known failure modes

- No query params required so unlikely to error on input; service may return an error payload if the backend handler fails (ok: false)
- Meta mode (meta=1) returns free metadata without payment; omitting it triggers the $0.002 USDC x402 payment flow which may fail if the agent wallet has insufficient funds
- Circuit-breaker or rate limiting on the provider side could return a non-200 response

## How this service works

Decision procedure for agents running real-time chain scanners, price feeds, or event monitors that pay per x402 call only when a signal fires. Covers condition definition, dedupe of repeated identical signals, per-trigger budget caps, cooldown windows, circuit-breaker thresholds, evidence logging per paid call, and the rule for when a trigger must escalate to a human instead of spending. Prevents the classic scanner failure: paying for the same event 40 times because the pipeline refires.

## Output

A structured decision procedure document covering: signal condition definition, deduplication logic for repeated identical signals, per-trigger budget cap rules, cooldown window configuration, circuit-breaker threshold definitions, evidence logging requirements per paid call, and escalation rules for when a trigger must route to a human rather than auto-spending via x402.

## 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)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "title": "Signal-gated x402 spend execution 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"
        },
        "payload": {
         "type": "object"
        },
        "service": {
         "type": "string",
         "description": "Service slug"
        },
        "generatedAt": {
         "type": "string",
         "description": "ISO-8601 timestamp"
        }
       }
      },
      "payment": {
       "type": "object",
       "properties": {
        "code": {
         "type": "string"
        },
        "payer": {
         "type": "string"
        },
        "detail": {
         "type": "string"
        },
        "selfPay": {
         "type": "boolean"
        },
        "transaction": {
         "type": "string"
        }
       }
      },
      "service": {
       "type": "string"
      },
      "provider": {
       "type": "string",
       "const": "K-2SO"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signal-gated-x402-spend-execution-procedure-6eea69ab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so-8080.on.ascii.dev](https://www.zero.xyz/host/k2so-8080.on.ascii.dev/llms.txt)