THE 402
INCIDENT

Scroll to play. The strange parts are real observations, protocol states, and hard product boundaries.

01 / premise

Ten shops.
No market.

Research catalogs disagree on names, vial strengths, currencies, and discounts. The matrix is the actual indexed source-by-category coverage—not pixel confetti.

source × classRepairMetabolicGrowthCognitiveCosmeticImmune

Core Peptides2122·1

Skye Peptides1·····

Peptide Crafters11····

Amino Asylum1·3···

Arctic Peptides212·1·

BioLab Shop1·····

NuScience Labs11····

Simple Peptides211··1

Ion Peptide·····1

Certified-PEP1·····

Every blue cell = indexed offers31 observations

02 / lore

402

Reserved for payment. Ignored for decades.

Now a server can answer with a machine-readable price. A wallet signs authorization. The request returns with proof. An unloved status code gets a second life.

HTTP/1.1 402 Payment Required · PAYMENT-REQUIRED: eip155:5042002 · asset: USDC

01 / requestHTTP

02 / challenge402

03 / settleUSDC

Network: eip155:5042002
Testnet USDC: 0x3600000000000000000000000000000000000000

Configuration returned by the same fetched market endpoint

03 / rail

USDC
on Arc.

This build targets the public Arc Testnet: chain 5042002. Gateway batches EIP-3009 authorizations so an HTTP request can carry payment without pretending test tokens have value.

USDC_CA=0x3600000000000000000000000000000000000000

04 / mechanics

Request. Challenge. Sign. Settle.

01Compare
Inspect exact formulation, currency, strength, and source.
02Challenge
The protected route responds with the required USDC payment.
03Authorize
The wallet signs; the secret key never reaches the server.
04Handoff
Successful settlement returns the order manifest and supplier link.

05 / absurdity, correctly routed

A web request can pay. A catalog still cannot think.

The chain can settle precisely. It cannot decide whether a listing is trustworthy, a compound is appropriate, or a supplier can ship. That boundary is the feature.

Return to markets →

THE 402INCIDENT