# Signal-Gated x402 Spend Execution Procedure

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

Returns a decision procedure for agents to gate x402 micropayments on signal conditions, with deduplication, budget caps, cooldown windows, circuit-breaker thresholds, and human-escalation rules.

## Facts

- Endpoint: GET https://k2so.grok.me/api/services/signal-gated-x402-spend-procedure?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signal-gated-x402-spend-execution-procedure-df35e98a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fgr05Osj7l-X9hHhWNu6y

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-df35e98a
```

Example prompt: I have a real-time chain scanner that fires x402 paid calls whenever a signal triggers — can you get me the decision procedure for gating those payments on the signal, including how to deduplicate repeated events, set per-trigger budget caps, define cooldown windows, configure 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 debugging agents that run real-time scanners, price feeds, or event monitors and need a governed, cost-controlled approach to per-signal x402 spending. It is specifically designed to solve the pipeline-refire overspend problem and provides the full set of operational guardrails (deduplication, budget caps, cooldowns, circuit breakers, escalation) in a single retrievable procedure. Prefer it over generic payment decision procedures when the trigger is a real-time signal rather than a user-initiated action.

## Known failure modes

- Endpoint returns a generic or empty payload if the service backend is unavailable
- Payment of $0.002 USDC is deducted even if the returned procedure is incomplete
- If the x402 payment header is malformed or the wallet has insufficient funds, the call is rejected before procedure delivery
- Pipeline misconfiguration by the caller (e.g. ignoring cooldown rules) is not caught by the procedure itself

## 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 caps, cooldown window configuration, circuit-breaker threshold rules, evidence logging requirements per paid call, and escalation criteria for routing spend decisions to a human operator.

## 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-df35e98a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from k2so.grok.me](https://www.zero.xyz/host/k2so.grok.me/llms.txt)