# Checkout Mandate Boundary Decision Map

> Checkout Mandate Boundary Decision Map 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 choosing between a user-signed open Checkout Mandate and an agent-signed closed Payment Mandate when an agent reprices a cart after the user has left.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/checkout-mandate-boundary-decision-map?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/checkout-mandate-boundary-decision-map-ba46312a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G1E-_l-r1gyf6s4D7JXd4

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 checkout-mandate-boundary-decision-map-ba46312a
```

Example prompt: I need to figure out whether to use an open Checkout Mandate signed by the user or a closed Payment Mandate signed by the agent when I'm repricing a cart after the user has already left — can you pull the decision procedure for that boundary?

## When to prefer this

Use this endpoint when an AI agent needs authoritative guidance on the mandate authorization boundary during agentic checkout flows — specifically when a cart is repriced after user departure and the agent must decide between an open user-signed Checkout Mandate and a closed agent-signed Payment Mandate. Prefer this over generic payment documentation when you need structured, machine-readable decision logic with explicit thresholds and failure modes tailored to x402-based agentic payment scenarios.

## Known failure modes

- Payment required but not provided — returns 402 with payment instructions
- Invalid or unsupported HTTP method — must be GET, HEAD, or DELETE
- topic override parameter ignored if not a recognized slug
- LLM generation unavailable — may fall back to deterministic source
- Malformed query parameters return validation error
- Service temporarily unavailable — no cached fallback

## How this service works

Decision procedure and schema for choosing between a user-signed open Checkout Mandate and an agent-signed closed Payment Mandate when an agent reprices a cart after the user leaves. Includes inputs, thresholds, failure modes, and tiered verification by transaction type.

## Output

A JSON object containing decision procedure prose for agents ('brief' field), the recommended mandate type based on inputs, applicable thresholds, failure modes, tiered verification rules by transaction type, a generation source indicator (llm, reasoning, or deterministic), and an ISO-8601 timestamp of generation.

## 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": "Checkout mandate boundary decision map 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/checkout-mandate-boundary-decision-map-ba46312a/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)