# Agent-to-Owner Escalation and Control Handoff Procedure

> Agent-to-Owner Escalation and Control Handoff 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-09-15).

Returns a decision procedure for x402 agents to escalate to their human owner or operator when hitting spend caps, kill switches, sanctions holds, identity verification requirements, or disputes beyond agent authority.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/agent-to-owner-escalation-control-handoff-proced
- Price: $0.002/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-to-owner-escalation-and-control-handoff-procedure-fc638500
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fa8UMWDcxBGNo4O0ODlGU

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 agent-to-owner-escalation-and-control-handoff-procedure-fc638500
```

Example prompt: I'm building a holder-controlled x402 agent on Base and need to know the exact procedure it should follow to escalate to me when it hits a spend cap — including how to package evidence, what timeout rules apply, and how control transfer semantics work so I get full context and clear authority boundaries.

## When to prefer this

Choose this endpoint when building or operating a holder-controlled x402 agent on Base that needs a structured, authoritative escalation protocol — specifically covering spend cap breaches, kill switch events, sanctions holds, identity verification requirements, or out-of-scope disputes. Prefer this over generic agent governance documentation when you need machine-readable, agent-facing procedural briefs with evidence packaging and timeout semantics tailored to the x402 protocol context.

## Known failure modes

- Endpoint returns generic or empty procedure if topic override is unrecognized
- LLM generation failure may return ok:false with no brief field
- Payment not confirmed may result in 402 response blocking access to paid content
- Timeout on generation may return stale or null generatedAt timestamp
- Malformed queryParams may cause schema validation errors

## How this service works

Decision procedure for a holder-controlled x402 agent to escalate to its owner or a human operator when it hits a limit: spend cap reached, kill switch triggered, sanctions hold, identity verification required, or dispute beyond agent authority. Covers evidence packaging, timeout rules, and control transfer semantics so the human takes over with full context and clear authority boundaries.

## Output

A prose decision procedure brief for agents, including step-by-step escalation logic, evidence packaging instructions, timeout rules, and control transfer semantics. The response includes a service slug, ISO-8601 generation timestamp, generation source (llm/reasoning/deterministic), and a free-text 'brief' and 'procedure' field describing exactly how the agent should behave and what the human operator receives upon handoff.

## 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": "Agent-to-owner escalation and control handoff 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": "agent-to-owner-escalation-control-handoff-proced",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "agent-to-owner-escalation-control-handoff-proced",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-to-owner-escalation-and-control-handoff-procedure-fc638500/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)