Discover / readiness-linter.46-224-157-88.sslip.io

x402/MPP Buyer-Readiness Linter

■ Challenge detected

Score the buyer readiness of an x402/MPP-listed OpenAPI document and list concrete fixes for payment metadata, missing examples, and HTTP 422 traps.

Challenge detected
3 of the last 3 checks
Median response
366 ms
Last checked
9 Oct, 15:20 UTC
In our index since
7 Oct 2026

Endpoint

curl -i https://readiness-linter.46-224-157-88.sslip.io/mpp/v1/lint
# 402 Payment Required: pay with a MPP client, then send the request again.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/readiness-linter.46-224-157-88.sslip.io

Recent checks

7 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.9 Oct 2026
All 3 checks
When (UTC)ResultHTTPResponse
9 Oct, 15:20 UTCChallenge detected402366ms
8 Oct, 09:20 UTCChallenge detected402365ms
7 Oct, 03:20 UTCChallenge detected402372ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 9 Oct, 15:20 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does x402/MPP Buyer-Readiness Linter advertise?

The listing advertises MPP, Tempo and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is x402/MPP Buyer-Readiness Linter listed?

In mppscan. Superstables first indexed it on 7 Oct 2026.

Something wrong on this page? Tell us.