# Stripe MPP vs Native x402 Rail Decision Procedure

> Stripe MPP vs Native x402 Rail Decision Procedure 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 deterministic decision brief telling merchants whether to accept agent payments via Stripe's MPP or a native x402 rail, based on their infrastructure and requirements.

## Facts

- Endpoint: GET https://k2so-8080.on.ascii.dev/api/services/stripe-mpp-acceptance-vs-native-x402-rail-decisi?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/stripe-mpp-vs-native-x402-rail-decision-procedure-82ebfc87
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LUHlm1NpL6eguOr0c67Qp

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 stripe-mpp-vs-native-x402-rail-decision-procedure-82ebfc87
```

Example prompt: We run about 800 agent transactions a month on our existing Stripe setup, need settlement within 2 days, and have a $0.05 per-transaction fee ceiling — should we stick with Stripe MPP or switch to a native x402 rail?

## When to prefer this

Use this endpoint when a merchant or platform operator needs a structured, reproducible recommendation for which payment rail to adopt for AI agent transactions — especially when balancing Stripe's existing infrastructure against x402's lower fees or faster settlement. Prefer this over general payment consulting or generic comparison tools when the specific tradeoffs of Stripe MPP vs native x402 are the decision axis.

## Known failure modes

- Missing or malformed query parameters may return a generic or incomplete decision brief
- LLM-backed generation source may produce non-deterministic output on ambiguous inputs
- Payment required (HTTP 402) if the x402 micropayment is not included in the request
- Service unavailable if the ascii.dev host is unreachable

## How this service works

Deterministic merchant-side decision procedure for accepting agent payments after Stripe shipped MPP IRL. Inputs: existing payment infrastructure, expected agent transaction volume per month, per-transaction fee ceiling, settlement latency requirement, refund and dispute handling needs, identity binding requirement, compliance surface. Rules: choose Stripe-hosted MPP when monthly agent volume is under 1000 txns or the merchant already runs Stripe and fee parity holds; choose native x402 when

## Output

A decision brief with a clear recommendation (Stripe-hosted MPP or native x402), prose explanation of the reasoning, metadata about the model or logic used, and an ISO-8601 timestamp indicating when the procedure was generated.

## 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": "Stripe MPP acceptance vs native x402 rail 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": "s
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stripe-mpp-vs-native-x402-rail-decision-procedure-82ebfc87/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)