# Cross-chain Capability Routing Standard

> Cross-chain Capability Routing Standard is a paid API for AI agents from k2so.wrong.systems, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-17).

Returns a decision procedure for AI agents that must select tools, payment rails, and settlement paths when operating across multiple blockchains.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/cross-chain-agent-capability-selection-procedure?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cross-chain-capability-routing-standard-69bf7424
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-fnAxAW3WSVO_OZWUq7Y4

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-chain-capability-routing-standard-69bf7424
```

Example prompt: I need a decision procedure for routing my agent's tasks across blockchains — specifically how to choose between x402 Base for micropayments, MPP/Tempo for session spend, and native rails when settlement finality matters; use the cross-chain capability routing topic.

## When to prefer this

Choose this endpoint when an AI agent must dynamically decide how to route tasks, payments, or settlement across multiple blockchains and lacks a built-in cross-chain decision framework. It is especially useful when the agent's home-chain tooling is insufficient and it needs a structured procedure covering tool availability, liquidity, bridge latency, and rail selection. Prefer it over static documentation or single-chain payment guides when the agent must reason about tradeoffs across x402 Base, MPP/Tempo, and native rails in a single coherent framework.

## Known failure modes

- Missing or invalid 'type' or 'method' fields returns a validation error
- Payment not provided results in a 402 Payment Required response before content is served
- Invalid topic override may result in a generic or misaligned procedure
- LLM-generated briefs may be non-deterministic across calls for the same topic
- Network or provider downtime returns a 5xx error with no procedure content

## How this service works

Decision procedure for agents that must operate across blockchains: how to select tools, payment rails, and settlement paths per task when home-chain tooling is insufficient. Covers (1) task decomposition into chain-agnostic vs chain-bound subtasks, (2) capability inventory per candidate chain (tool availability, liquidity depth, bridge latency), (3) rail selection: x402 Base for micropayments, MPP/Tempo for sessionized spend, native rails where settlement finality matters, (4) the

## Output

A prose decision procedure (the 'brief' field) guiding the agent through: (1) decomposing tasks into chain-agnostic vs chain-bound subtasks, (2) inventorying capabilities and liquidity depth per candidate chain, (3) selecting the appropriate payment rail (x402 Base, MPP/Tempo, or native), and (4) choosing a settlement path. Also returns metadata including the generation source (llm/reasoning/deterministic), ISO-8601 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": "Cross-chain capability routing standard 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": "cross-chain-agent-capability-selection-procedure",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "cross-chain-agent-capability-selection-procedure",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cross-chain-capability-routing-standard-69bf7424/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)