Desk model · 14 Oct 2026 · not a model log

05 · Briefs

Five prompts with the thinnest quote.

Lowest brand echo, highest intent. Three of the five URLs already exist — those briefs are rebuilds. One title does not exist and should. The comparison page is deliberately not in this set: it is already good enough to stop rewriting.

New URL · /a-402-challenge-is-not-payment

An HTTP 402 challenge is not proof of payment

Highest on-page ceiling on the desk because the sentence is not currently a title, and the incumbent does not say it.

An HTTP 402 challenge is not proof of payment: a signature is not settlement, and settlement is not accepted delivery.

Meta · 114 characters

An HTTP 402 challenge is not proof of payment. A signature is not settlement. Settlement is not accepted delivery.

Structure

  1. What HTTP 402 means

    Mirror MDN’s definition, then stop. Do not re-teach status codes.

  2. What an x402 challenge contains

    Price, network, asset, payTo, resource. Fresh challenge only.

  3. What a signature proves

    The caller authorized that challenge. It does not prove a transfer.

  4. What PAYMENT-RESPONSE proves

    Settlement evidence. Still not accepted delivery.

  5. What accepted delivery adds

    The paid result was usable. Name the boundary in one line.

  6. A production example

    URL-to-Markdown, 0.001 USDC, Base, evidence URL. No buyer-identity claim.

  7. What this page will not say

    No volume, no ranking, no ‘trusted by’.

Who gets the citation now

  • developer.mozilla.org — Owns the status-code definition and will keep it.
  • docs.cdp.coinbase.com — Owns the happy-path implementation.
  • x402.org — Owns the protocol name. Link, don’t rival.

Winning domain categories

  • Standards pages (MDN, IETF) win the bare definition
  • Protocol docs (Coinbase CDP, x402.org) win the flow
  • Nobody owns the four-state distinction — that is the opening

Internal links

  • x402 payment protocol /x402-payment-protocol

    Canonical protocol essay. This page is the sentence; that page is the context.

  • URL to Markdown API /url-to-markdown-api

    The one job with published settlement evidence.

  • x402 Gateway /x402-gateway

    Inspection without spend. Keeps the reader from treating discovery as checkout.

Prompt this brief answers: Is an HTTP 402 challenge proof that an x402 payment settled?

Truth boundary. Queue weights sort this desk. They are not measured demand, citations, visits, or buyers. Citation-to-opportunity is left blank because the numerator was not observed. Crawl rows update only after a live fetch. A 402 challenge is not a sale. The MCP figures are dated file counts, not a live-server census. A Google Play list price is not an x402 price and not a sale.