# Agent Wallet Control Precedence Schema

> Agent Wallet Control Precedence Schema 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-22).

Returns a deterministic decision procedure for resolving conflicting wallet control limits (merchant caps, per-period caps, fleet policy, transaction ceilings, category limits) on a single agent payment.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/agent-wallet-control-precedence-schema?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-wallet-control-precedence-schema-01ff33ae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ybEYJhMpAf6EJnb12Q1QG

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-wallet-control-precedence-schema-01ff33ae
```

Example prompt: I need the decision procedure for figuring out which spending control takes precedence when a fleet policy limit and a per-agent per-period cap are both active on the same payment — can you pull the agent wallet control precedence schema?

## When to prefer this

Use this endpoint when an AI agent must autonomously resolve competing wallet spending controls before authorizing or rejecting a payment, especially in multi-policy environments (fleet + merchant + category + period caps all active). Prefer this over manual policy lookup when the agent needs a single authoritative ranked procedure rather than raw policy documents.

## Known failure modes

- Ambiguous precedence rank when two controls have equal priority — procedure may return an unresolvable conflict state
- Conflicting fleet and per-agent limits with no defined override authority — escalation path undefined
- Stale cap values provided — procedure may return outdated thresholds that don't reflect current authorization state
- Invalid or missing topic override — falls back to default decision procedure scope
- Payment metadata flag misuse — calling without ?meta=1 incurs charge even for schema-only queries

## How this service works

Deterministic procedure for resolving simultaneous bindings of merchant caps, per-period caps, fleet policy, single-transaction ceilings and category limits on one agent payment. Inputs include effective control set, limit values, binding scope, authorization authority, and transaction amount. Thresholds define when a control is exhausted, when overrides escalate, and when payment is rejected. Failure modes include ambiguous precedence rank, conflicting fleet and per-agent limits, stale cap

## Output

A structured decision procedure document (prose brief plus optional procedure text) describing exactly how to rank and resolve simultaneous wallet control bindings — including threshold rules for control exhaustion, escalation triggers, and payment rejection criteria — along with metadata like generation source, timestamp, topic, and service slug.

## 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 wallet control precedence schema 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)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-wallet-control-precedence-schema-01ff33ae/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)