{"criteria_id":"payer-preflight/v1","criteria_family":"payer-preflight/v1","version":"1.0.0","corpus":{"id":"rail-router-corpus/v1","sha256":"8022e577a86e1fb4805de5f3d173323720f491087e68a300e5a9aa0917bbf254"},"corpus_pin_definition":"The corpus pin is the SHA-256 of the corpus's canonical serialization (the corpus object excluding its sha256 field), computed and verifiable by the published harness (harness.mjs).","price":{"usdc_units_per_call":10000,"label":"$0.01","basis":"per challenge"},"free_tier":{"per_day":100,"min_interval_ms":5000,"on_exhaustion":"402"},"ops":{"route":"POST /route — artefact { status?, headers?, body? }"},"evidence_order":["Rule 1 — L402 explicit pair: a WWW-Authenticate header carrying the L402 scheme WITH both macaroon= and invoice= parameters is self-describing and wins over every other signal.","Rule 2 — x402 accepts[]: a structured accepts[] array in the 402 body, or in a base64-JSON PAYMENT-REQUIRED / X-PAYMENT-REQUIRED header, wins over all remaining signals. The FIRST accepts entry determines the primary rail; further entries are printed as alternatives, not conflicts.","Rule 3 — MPP: a WWW-Authenticate Payment scheme, or a body carrying an MPP session/escrow object, wins over header-name-only hints.","Rule 4 — Header-name-only hints (a PAYMENT-REQUIRED header that does not decode to an accepts[] body, an X-PAYMENT-REQUIRED name alone) never override Rules 1-3 and alone yield unknown with the hint printed as evidence.","Same-tier conflict: if two signals of the SAME rule tier point to different rails, the earlier rule in this list wins and the losing signal is printed under conflicting_signals with the rule that resolved it. Nothing is resolved silently."],"rail_table":[{"rail":"x402-EVM","asset":"USDC on an EVM network — the token contract address named in accepts[].asset, on the CAIP-2 network named in accepts[].network (legacy names: base, base-sepolia, ethereum).","wallet_capability":"An EVM wallet that can sign the x402 exact-scheme payment payload (EIP-712 TransferWithAuthorization for ERC-20 USDC). Header version must match the challenge: v1 clients send X-PAYMENT, v2 clients send PAYMENT-SIGNATURE.","first_incompatibility":"A Solana-only or Lightning-only wallet cannot pay this rail at all. The first silent failure to expect is the v1/v2 split: a client speaking the other version's header name is never seen by the server, which simply re-issues a fresh 402 with no error.","provenance":"FRICTION-MAP friction 39 + lane-1 F-30 (x402 = USDC, EVM signature); lane-3 protocol-gaps header table (X-PAYMENT v1 vs PAYMENT-SIGNATURE v2); lane-1 v1/v2 breakage record (no backward-compatibility provision). All in ~/workspace/research_notes/402-frictions-2026-11-03/."},{"rail":"x402-SVM","asset":"USDC on Solana — the SPL mint named in accepts[].asset (the canonical USDC mint is EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v), on a solana:* CAIP-2 network.","wallet_capability":"A Solana wallet that can PARTIALLY SIGN the payment transaction (the facilitator commonly supplies the fee payer and completes the signature). The transaction carries a TransferChecked token instruction.","first_incompatibility":"An EVM-only wallet cannot partial-sign a Solana transaction. Expect facilitator-policy failures next: compute limits and instruction shapes are graded per facilitator, not by the protocol.","provenance":"FRICTION-MAP friction 39 + lane-1 F-30 (x402 = USDC, Solana partial-sign). In ~/workspace/research_notes/402-frictions-2026-11-03/."},{"rail":"L402","asset":"BTC over Lightning — sats, against the BOLT11 invoice carried in the WWW-Authenticate L402 challenge (invoice= parameter). Denomination is BTC/sats, not USD.","wallet_capability":"A Lightning backend that RETURNS PREIMAGES — LND/Strike-class. NOT NWC: Nostr Wallet Connect does not return preimages, so NWC wallets cannot do L402 at all. This distinction is a published factor and is never blurred. The payer pays the invoice and retries with Authorization: L402 <macaroon>:<preimage>.","first_incompatibility":"An NWC-based wallet fails before any payment: it cannot obtain the preimage the retry requires. Next frictions are channel liquidity / routing (payments can sit 10+ seconds or fail) and BTC-vs-USD denomination swings. One offsetting strength: per-payment-hash idempotency — re-paying the same invoice returns the original completed payment with no second debit.","provenance":"FIX-CANDIDATES §C7 (preimage-returning backend — LND/Strike-class, not NWC); FRICTION-MAP friction 39 (NWC cannot do L402 at all); lane-1 F-30 (Wozacosta NWC record; Wavelength field test 2026-10-27; L402 spec: WWW-Authenticate L402 macaroon + invoice, Authorization retry form). In ~/workspace/research_notes/402-frictions-2026-11-03/."},{"rail":"MPP","asset":"As named by the MPP challenge itself — Stripe MPP runs sessions / escrow vouchers (Tempo); the asset and amount are read from the submitted challenge, never assumed to be USDC-on-x402.","wallet_capability":"An MPP-capable client that can open and fund an MPP session / escrow voucher flow. x402 payment logic does NOT transfer: an agent built for x402 cannot pay MPP-gated services without rewriting its payment logic.","first_incompatibility":"An x402-only client has no session machinery and cannot pay, however much USDC it holds. Expect session/escrow lifecycle handling (open, voucher, close) where x402 has a single signed payload.","provenance":"FRICTION-MAP friction 39 (Stripe MPP, sessions/escrow); lane-1 F-30 (Stripe MPP Mar 2026, Tempo sessions / escrow vouchers; Grand Protocol pitch quoted there). THIN RECORD DISCLOSED: the on-disk records name MPP's session/escrow shape but publish no field-level challenge grammar; the MPP identification signals in this engine are therefore labelled a build-lane construction in CRITERIA.md. In ~/workspace/research_notes/402-frictions-2026-11-03/."},{"rail":"unknown","asset":null,"wallet_capability":null,"first_incompatibility":"No rail could be identified from the submitted evidence, so no wallet or asset can be stated. Do not attempt payment: ask the seller which rail the endpoint speaks, or submit the full 402 response (status, headers, and body).","provenance":"Build rule (brief + FIX-CANDIDATES §C7): unknown is a first-class answer; an unidentifiable response is reported unknown with the discriminating evidence printed, never forced into a known rail."}],"malformed":"A malformed artefact is never graded: a named free refusal, before any payment, at the pre-check and at the paid op alike.","honesty_boundary":"A rail is stated only when a published discriminating signal in the submitted artefact matches it, under the evidence order printed in the criteria. Per-rail requirement statements are exactly as sourced from the records on disk, provenance labelled per rail; the MPP identification signals are disclosed as a build-lane construction because the on-disk records publish no field-level MPP challenge grammar. Where no signal matches, the answer is unknown with the evidence printed.","boundary":"Boundary: this service classifies a submitted 402 response. It does not probe a live endpoint, does not lint a payment payload (the C1 op of this family), does not translate failures (C2), and moves no funds.","custody":{"ledger_closed_fields":["payer wallet","timestamp","day","price (USDC units) with the CAD fair-market-value block (rate, rate date, basis, cad_pending, refund — null unless refunded)","payment tx id","Solana fee (lamports)","criteria version","op","verdict line","per-check status summary","house flag"],"retention":"Submitted artefacts are processed once at call time and are never stored — not in KV, not in logs, not in the payments ledger, not in metrics. The payments ledger records only the closed field list published in the criteria. Because nothing is kept, a paid retry re-sends the artefact."},"payment_includes":"$0.01 per challenge. The payment includes: one rail identification of the one 402 response (or its headers) you submit — the rail (x402-EVM / x402-SVM / L402 / MPP / unknown), the discriminating evidence printed, any conflicting signals with the published rule that resolved them, and for the identified rail the asset, the wallet capability required, and the first incompatibility to expect, each with its provenance — and an as-of timestamp. Unknown is a first-class answer: an unidentifiable response is reported unknown with the evidence printed, never forced into a known rail. Factors printed; no composite score. Nothing submitted is stored beyond the payments ledger's closed field list.","kill_line":"Kill line (M-32, under the operator's 2026-11-03 zero-demand doctrine): build, bank, and hold; judged at the fleet's periodic reviews. Tripwires, all stop-and-review: refunds >5% of paid calls in any 30-day window; free use >10x paid use; a wrong factor from undisclosed stale or partial data.","service":"rail-router","endpoints":{"criteria":"GET /criteria (free)","precheck":"POST /precheck (free, validation + assessability only; no factors)","route":"POST /route (paid, $0.01 per challenge: signed rail report)","metrics":"GET /metrics"}}