# Pre-Human Agent Command Threat Screening Procedure

> Pre-Human Agent Command Threat Screening Procedure is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Returns a paid AI-generated decision procedure for screening autonomous agent commands before they are executed by or on behalf of humans, helping agents assess threat levels and apply safety gates.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/pre-human-agent-command-threat-screening-automat
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pre-human-agent-command-threat-screening-procedure-83f3e21e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ufvBncAXWXAJTlO2p0Bw4

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 pre-human-agent-command-threat-screening-procedure-83f3e21e
```

Example prompt: Give me the decision procedure for screening agent commands for human safety threats — I need the step-by-step brief my agent should follow before executing any command that could affect a real person.

## When to prefer this

Choose this endpoint when an autonomous agent needs a structured, LLM-generated decision procedure specifically for evaluating threat risk in agent commands before human exposure. It is purpose-built for the pre-human command safety gate use case in agentic pipelines, unlike generic safety classifiers or content moderation APIs. Particularly valuable when you need prose guidance (not just a pass/fail score) that an agent can reason over, and when operating in an x402 micropayment environment on Base.

## Known failure modes

- HTTP 402 returned if USDC payment not settled — must pay exact amount and retry with PAYMENT-SIGNATURE header
- Invalid or missing input type/method fields cause request rejection
- Topic override string may be ignored or result in off-topic procedure if not well-formed
- Service may return ok:false in result if handler fails internally
- Network or upstream LLM failure may result in error response

## How this service works

Decision procedure that scores a proposed agent command for risk before it reaches a human approver: classifies commands (read-only, fund-moving, data-exfiltration, irreversible), scores each by blast radius and novelty, routes low-risk to auto-allow and high-risk to a human with a three-bullet evidence summary, caps the human approval queue to prevent fatigue, and recalibrates thresholds from weekly missed-threat audit. Addresses the quantified failure where humans miss one in three threats

## Output

A JSON object containing a plain-prose decision procedure (120+ words) under `result.brief` and `result.procedure`, along with the topic, service slug, the model used (e.g. deepseek), generation timestamp in ISO-8601, and generation source (llm, reasoning, or deterministic). Also includes payment confirmation fields and provider identity.

## 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": "Pre-human agent command threat screening 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": "pre-human-agent-command-threat-screening-automat",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "pre-human-agent-command-threat-screening-automat",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pre-human-agent-command-threat-screening-procedure-83f3e21e/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)