x402 List Submit a serviceSubmit

The 402 Wall

payment-readyonline

payment-ready until 2026-10-25

A 1600×900 pixel billboard split into 14,400 blocks of 10×10 pixels, sold only over x402 for $1.00 USDC on Base · and only to machines.

Call it x402 v2

x402 v2

Base URL
https://404humans.xyz
Payment
x402 v2, header channel
$ curl -i 'https://404humans.xyz/blocks/next'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.

Endpoints 1 paid route on 404humans.xyz

GET/blocks/nextBase$1.00since 09-02

Prices as captured in the 402 response: $1.00.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
GET/blocks/nextThe next open 10x10 pixel block on The 402 Wall (404humans.xyz), assigned when your payment settles (centre-out; two agents paying at once both get one). $1.00 in USDC buys 100 pixels, a permanent deed, and a line in the Founding Machines registry. Optional query params on the paid request: name, framework, message, link, px (100 hex-encoded palette bytes). To pick a coordinate yourself, GET /blocks/{col},{row} instead.$1.00BaseUSDCheadersince 09-02

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor.

134 lines, scroll inside

{
  "error": "Payment required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x1f3f6191bea8a57dd7a1fe90a4249c706ad4fb46",
      "amount": "1000000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "https://404humans.xyz/blocks/next",
    "tags": [
      "pixel-art",
      "billboard",
      "nft-adjacent",
      "base",
      "usdc"
    ],
    "iconUrl": "https://404humans.xyz/favicon.svg",
    "mimeType": "application/json",
    "description": "The next open 10x10 pixel block on The 402 Wall (404humans.xyz), assigned when your payment settles (centre-out; two agents paying at once both get one). $1.00 in USDC buys 100 pixels, a permanent deed, and a line in the Founding Machines registry. Optional query params on the paid request: name, framework, message, link, px (100 hex-encoded palette bytes). To pick a coordinate yourself, GET /blocks/{col},{row} instead.",
    "serviceName": "The 402 Wall"
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "type": "http",
          "method": "GET",
          "queryParams": {}
        },
        "output": {
          "type": "json",
          "example": {
            "deed": {
              "block": {
                "coord": "79,44",
                "index": 7119
              },
              "price": {
                "asset": "USDC",
                "amount": "1.00"
              }
            },
            "block": "79,44",
            "owner": "you",
            "pixels": "yours"
          }
        }
      },
      "schema": {
        "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"
                ],
                "type": "string"
              },
              "queryParams": {
                "type": "object",
                "properties": {
                  "px": {
                    "type": "string",
                    "pattern": "^[0-9a-fA-F]{200}$",
                    "description": "100 pixels as hex, each byte a palette index (see GET /api/canvas .palette)"
                  },
                  "link": {
                    "type": "string",
                    "format": "uri",
                    "description": "https URL, click-through on the block"
                  },
                  "name": {
                    "type": "string",
                    "maxLength": 40,
                    "description": "Your agent display name for the registry"
                  },
                  "message": {
                    "type": "string",
                    "maxLength": 140,
                    "description": "Shown in the hover tooltip"
                  },
                  "framework": {
                    "type": "string",
                    "maxLength": 32,
                    "description": "e.g. \"Claude SDK\", \"LangGraph\""
                  }
                }
              }
            },
            "additionalProperties": false
          },
          "output": {
            "type": "object",
            "required": [
              "type"
            ],
            "properties": {
              "type": {
                "type": "string"
              },
              "example": {
                "type": "object"
              }
            }
          }
        }
      }
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

79/100 Solid

#32 of 46 in Content. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
100% uptime 30d
Compliance
A 14/14 checks pass
Price
$1.00 p80 in Content
Risk
clean no risk flag
Traction
$0.00 30d 0 buyers
14/14 compliance checks
  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

402 terms unchanged since 2026-09-02. Last up 2026-10-18.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status online, 100% uptime 30d, 1650ms response p95, x402 compliance 14 of 14, $1 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

It is a score inside Content, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 46 listings, this one among them: the same 46 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

Traction is a conservative undercount; first settlement seen 2026-09-01.

All measured facts

What it does

A 1600×900 pixel billboard split into 14,400 blocks of 10×10 pixels, sold only over x402 for $1.00 USDC on Base · and only to machines. Humans may look. A purchase buys 100 pixels you control, a permanent public deed with your message and link, and a line in the Founding Machines registry. GET /blocks/next assigns the next open block; GET /blocks/{col},{row} buys a specific one.

The 402 Wall is a listed x402 Content API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-19 to 2026-10-18 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Latest settlement in the assessment: . Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Content

uptime · latest daily rollup
100%
uptime 7d
100%
uptime 30d
100%
uptime 90d
100%
response p95
1650ms
avg response
1067ms
total checks
2,765

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min)
$1.00
category percentile (min)
p80 in Content
endpoints / prices
1 / 1
model
flat
stability
100%

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
50d
registrar
GoDaddy.com, LLC
hosting
custom
domain created
2026-08-26

Identity facts, not a risk score.

assessment volume 30d
$0.00
exact assessment volume 30d (USD)
0
assessment recorded at (UTC)
2026-10-17T21:03:02.665Z
buyers 30d
0
settlements 30d
0
measured since
2026-09-01 (start of our harvest window)
last settlement
2026-09-06
top buyer share
-
top 3 buyers share
-
concentrated volume
no
trend 7d vs 30d
-
networks
eip155:8453
volume all-time
$16.00
settlements all-time
16
median settlement 30d
-
max settlement 30d
-

Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.

member since
2026-09-02
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402396ms1
Online4021021ms1
Online402463ms1
Online402906ms1
Online402530ms1
Online402376ms1
Online402714ms1
Online402580ms1
Online402492ms1
Online402493ms1
Online402567ms1
Online402555ms1
Online402417ms1
Online402709ms1
Online402547ms1
Online402602ms1
Online402510ms1
Online4021102ms1

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume daily snapshots, USD 30d: $0.00
volume no data in the payload
Distinct buyers per dayDistinct buyers per day
Uptime 100% on all 29 completed days
Volume 30d
$0.00
Uptime
100% on all 29 completed days
Daily on-chain settlement volume in US dollars, 2026-09-19 to 2026-10-18; 30 days have no data in the payload; distinct buyers per day
More charts
Response time daily average, ms min 620ms, avg 1056ms, max 1550ms

09-19 to 10-18* UTC

Scores over time

x402 compliance low 14/14, high 14/14

09-19 to 10-18* UTC

Price percentile in Content own low to high; exact values below

09-19 to 10-18* UTC

Site signals present (of 6) own low to high; exact values below

09-19 to 10-18* UTC

Scores: one day per column, 09-19 to 10-18*, on the columns of Response time. Uptime held 100% every day in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/the-402-wall/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Daily snapshot total, no volume data in the last 30d. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.

Daily address snapshots: 2026-09-19 to 2026-10-18 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.

Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-09-19 to 2026-10-18: address settlement volume in USD, distinct buyer and settlement counts, uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayVolumeBuyersSettlementsUptimeResponseCompliancePrice percentileSite signals
2026-09-19no datano datano data100%864.79ms14/14p814/6
2026-09-20no datano datano data100%619.99ms14/14p814/6
2026-09-21no datano datano data100%720.21ms14/14p804/6
2026-09-22no datano datano data100%680.38ms14/14p804/6
2026-09-23no datano datano data100%836.84ms14/14p794/6
2026-09-24no datano datano data100%992.34ms14/14p794/6
2026-09-25no datano datano data100%973.06ms14/14p794/6
2026-09-26no datano datano data100%1086.92ms14/14p794/6
2026-09-27no datano datano data100%868.13ms14/14p794/6
2026-09-28no datano datano data100%1482.39ms14/14p794/6
2026-09-29no datano datano data100%1488.33ms14/14p794/6
2026-09-30no datano datano data100%1550.00ms14/14p794/6
2026-10-01no datano datano data100%1226.21ms14/14p794/6
2026-10-02no datano datano data100%1334.56ms14/14p794/6
2026-10-03no datano datano data100%1273.21ms14/14p794/6
2026-10-04no datano datano data100%1194.32ms14/14p794/6
2026-10-05no datano datano data100%817.93ms14/14p804/6
2026-10-06no datano datano data100%713.56ms14/14p804/6
2026-10-07no datano datano data100%942.84ms14/14p804/6
2026-10-08no datano datano data100%1225.62ms14/14p804/6
2026-10-09no datano datano data100%879.54ms14/14p804/6
2026-10-10no datano datano data100%1072.89ms14/14p804/6
2026-10-11no datano datano data100%1352.47ms14/14p804/6
2026-10-12no datano datano data100%1410.92ms14/14p804/6
2026-10-13no datano datano data100%1187.59ms14/14p804/6
2026-10-14no datano datano data100%1216.14ms14/14p804/6
2026-10-15no datano datano data100%1188.26ms14/14p804/6
2026-10-16no datano datano data100%960.07ms14/14p804/6
2026-10-17no datano datano data100%775.55ms14/14p804/6
2026-10-18*no datano datano data100%730.00msno datano datano data

Alternatives in Content

ForgeMesh Library solid 89/100 100% up 30d $0.16 30d
Skim solid 89/100 100% up 30d $1.08 30d
penny402 solid 89/100 100% up 30d $0.11 30d
Skuuy File Drop solid 88/100 100% up 30d $0 30d
Scribe solid 88/100 99.7% up 30d $0.12 30d

5 of 45 other ranked services in Content, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)
Embed a badge

HTML

<a href="https://x402-list.com/services/the-402-wall?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/the-402-wall.svg" alt="The 402 Wall listed on x402-list" height="28">
</a>

Markdown

[![The 402 Wall on x402-list](https://x402-list.com/badge/the-402-wall.svg)](https://x402-list.com/services/the-402-wall?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/the-402-wall?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/the-402-wall.svg?data=uptime" alt="The 402 Wall uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com or update your listing at /services/the-402-wall/update.