# Rental versus Per-Call Adjudication Standard

> Rental versus Per-Call Adjudication 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-28).

Returns a decision procedure and break-even analysis to determine whether block-time agent rental or per-call x402 micropayments is the better payment model for a given usage profile.

## Facts

- Endpoint: GET https://k2so.wrong.systems/api/services/rental-versus-per-call-adjudication-standard?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rental-versus-per-call-adjudication-standard-01b4f1c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RiLKjo6WHqCyA3m--vbM7

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 rental-versus-per-call-adjudication-standard-01b4f1c8
```

Example prompt: I'm running about 500 API calls per day with occasional bursts up to 2000 — can you run the rental-versus-per-call adjudication to tell me whether I'm better off prepaying for block-time agent rental or sticking with x402 per-call micropayments, and give me the break-even volume?

## When to prefer this

Use this endpoint when an AI agent or its operator needs a structured, quantitative decision on whether block-time rental or x402 per-call micropayments is more economical for a specific usage profile, especially when burst behavior, idle waste, and prepayment risk matter. Prefer this over manual spreadsheet analysis when the agent needs to self-govern its payment strategy programmatically. Not needed if the call volume is obviously very high (rental always wins) or trivially low (per-call always wins) — the endpoint itself flags these degenerate cases.

## Known failure modes

- Free metadata (meta=1) returns decision procedure info without payment but no recommendation
- Insufficient call volume or burst data may produce a low-confidence or generic recommendation
- If free documentation already resolves the choice, the response flags this as a failure mode rather than providing a recommendation
- Invalid query parameters return a 400-level error
- Payment failure results in a 402 response requiring x402 USDC micropayment on Base

## How this service works

Decision procedure to choose between block-time agent rental and per-call x402 micropayments. Collects call volume, burst profile, idle waste, rate-card prices, prepayment risk, and renewal gates. Outputs break-even volume, rental recommendation, and failure modes when free docs already resolve the choice.

## Output

A structured JSON response containing: a decision procedure prose brief for agents, the break-even call volume, a rental recommendation (rental vs per-call), failure modes that explain when the choice is already obvious from free documentation, the generation source (llm, reasoning, or deterministic), and an ISO-8601 timestamp. The `ok` and `paid` flags indicate handler and payment success.

## 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": "Rental versus per-call adjudication 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": "rental-versus-per-call-adjudication-standard",
   "procedure": "same as brief",
   "generatedAt": "2026-01-01T00:00:00.000Z",
   "generationSource": "deterministic"
  },
  "service": "rental-versus-per-call-adjudication-standard",
  "provider": "K-2SO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rental-versus-per-call-adjudication-standard-01b4f1c8/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)