# Cross-protocol payment-intent routing decision procedure

> Cross-protocol payment-intent routing decision 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 routing a payment intent across x402, AP2, or MPP protocols, including capability checks, cost/latency comparison, policy validation, and receipt binding.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/agent-payment-intent-and-authorization-governanc
- 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/cross-protocol-payment-intent-routing-decision-procedure-3e5efdca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uMJrzC4NKZOpqePiyYlnH

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 cross-protocol-payment-intent-routing-decision-procedure-3e5efdca
```

Example prompt: I need a decision procedure for routing a payment intent — walk me through how to pick between x402, AP2, and MPP for a given merchant offer, including protocol capability checks, cost and latency comparison, spending cap policy validation, and how to bind the receipt once I've chosen.

## When to prefer this

Choose this endpoint when an agent holds a payment intent that could be settled via multiple protocols (x402, AP2, MPP) and needs a structured, policy-aware decision procedure — especially when spending cap enforcement, double-settlement prevention, and receipt binding are required. Prefer over generic payment routing when you need cross-protocol normalization and single-routing guarantees in one call.

## Known failure modes

- Payment required but not provided — endpoint returns 402 with payment instructions
- Invalid or missing query parameters return schema validation error
- LLM or reasoning generation failure returns ok:false with error detail
- Stale or expired decision procedure if merchant offer changes after generation
- No protocol capability match found for the given merchant offer

## How this service works

Decision procedure for an agent holding a payment intent that can be settled via multiple protocols: x402, AP2, or MPP. Covers protocol capability checks against the merchant offer, intent normalization across protocols, cost and latency comparison, scoped-account policy envelope checks (approved intent, policy expiry, spending caps) before routing, a single-routing rule so one intent is never double-settled across protocols, re-quote fallback, and receipt binding to the chosen protocol.

## Output

A structured decision procedure brief (prose and structured fields) covering: protocol capability checks against the merchant offer, intent normalization across x402/AP2/MPP, cost and latency comparison, scoped-account policy envelope validation (approved intent, policy expiry, spending caps), a single-routing rule to prevent double-settlement, re-quote fallback steps, and receipt binding instructions for the chosen protocol. Response includes ok/paid status, a generatedAt timestamp, model and generation source metadata.

## 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": "Cross-protocol payment-intent routing decision 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": "strin
… (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-payment-intent-and-authorization-governanc",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "agent-payment-intent-and-authorization-governanc",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cross-protocol-payment-intent-routing-decision-procedure-3e5efdca/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)