payment-ready 2026-08-23, probe currently failing
Two machine-payable HTTP APIs over x402 (USDC on Base, PayAI keyless facilitator — no account, no API key). POST /api/seo-audit fetches a URL and returns a weighted on-page technical SEO audit (title, meta, canonical, Open Graph, headings, alt text, structured data, word count) with a 0–100 score. POST /api/extract fetches a URL and returns clean markdown + plain text with boilerplate stripped, for LLM ingestion pipelines. Flat $0.01 per call, pay-per-request, no sign-up. A paid MCP surface at /mcp exposes the same tools; tools/list is free and tools/call is x402-gated per call. Machine-readable manifest at /.well-known/x402.
Pay from $0.01 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.
listed 2026-07-30 · no on-chain settlement recorded yet
VERDICT
ranking generation 3mixed 68/100 #274 of 283 in Data by measured score
What the score read on this service: status offline, 89.2% uptime 30d, 637ms response p95, x402 compliance 13 of 14, $0.01 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.
It is a score inside Data, 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 283 listings, this one among them. That set is wider than the 283 the position above is counted against, 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.
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.
ALTERNATIVES IN DATA
Other Data services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).
| SERVICE | BAND | SCORE | UPTIME 30D | VOL 30D |
|---|---|---|---|---|
| StableEnrich | strong | 96 | 100% | $2.0k |
| glim.sh | strong | 95 | 100% | $52.46 |
| SniperX•x402 | strong | 95 | 100% | $538.47 |
| cn402 | strong | 94 | 100% | $39.15 |
| API Acre | solid | 92 | 99.8% | $34.05 |
ASSESSMENT
updated 2h agoThe parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.
reliability 89.2%
- uptime 24h
- 0%
- uptime 7d
- 0%
- uptime 30d
- 89.2%
- uptime 90d
- 95.8%
- response p95
- 637ms
- avg response
- 372ms
- total checks
- 941
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
compliance A (13/14): declares the current x402 version (2), stale (probe failing)
13 of 14 x402 conformance checks pass; failing: declares the current x402 version (2). Full checklist below.
price $0.01 (p59 in Data)
- price (min)
- $0.01
- category percentile (min)
- p59 in Data
- endpoints / prices
- 2 / 1
- model
- flat
- stability
- 100%
risk clean
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
- -
- registrar
- -
- hosting
- custom
- domain created
- ---
Identity facts, not a risk score.
traction $0.00 30d · 0 buyers
- volume 30d
- $0.00
- buyers 30d
- 0
- settlements 30d
- 0
- measured since
- --- (start of our harvest window)
- last settlement
- ---
- top buyer share
- -
- trend 7d vs 30d
- -
- networks
- eip155:8453
- volume all-time
- $0
- settlements all-time
- 0
- median settlement 30d
- -
- max settlement 30d
- -
- settled via
- -
Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.
Top buyer share is a concentration signal, not part of the ranking score.
WHAT IT DOES
ai-derivedNo AI synthesis has been produced for this service yet.
ENDPOINTS
| METHOD | PATH | DESCRIPTION | PRICE | NETWORK | ASSET | 402 CHANNEL |
|---|---|---|---|---|---|---|
| POST | /api/extract | Fetch a URL and return readable content as clean markdown and plain text (boilerplate stripped). Useful for LLM ingestion pipelines. | $0.01 | Base | USDC | body (v1 style) |
| POST | /api/seo-audit | Fetch a URL and return a weighted on-page SEO audit (title, meta, canonical, OG, headings, alt text, structured data, word count) with a 0–100 score. Signal tool, not a spec validator. | $0.01 | Base | USDC | body (v1 style) |
REQUEST / RESPONSE EXAMPLE
An unpaid request to POST /api/extract returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
curl -i -X POST 'https://cyberdyne.linuxlabs.dk/api/extract'
// 402 response (captured by monitor) · 2 payloads · click to expand
[
{
"error": "payment required: resend with X-PAYMENT header",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xbeeA850484e1cC673e62065d93c8E84C809c4E60",
"scheme": "exact",
"network": "base",
"mimeType": "application/json",
"resource": "https://cyberdyne.linuxlabs.dk/api/extract",
"description": "Fetch a URL and return readable content as clean markdown and plain text (boilerplate stripped). Useful for LLM ingestion pipelines.",
"maxAmountRequired": "10000",
"maxTimeoutSeconds": 120
}
],
"x402Version": 1
},
{
"error": "payment required: resend with X-PAYMENT header",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xbeeA850484e1cC673e62065d93c8E84C809c4E60",
"scheme": "exact",
"network": "base",
"mimeType": "application/json",
"resource": "https://cyberdyne.linuxlabs.dk/api/seo-audit",
"description": "Fetch a URL and return a weighted on-page SEO audit (title, meta, canonical, OG, headings, alt text, structured data, word count) with a 0–100 score. Signal tool, not a spec validator.",
"maxAmountRequired": "10000",
"maxTimeoutSeconds": 120
}
],
"x402Version": 1
}
] OVER TIME
All charts use the 24h selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/cyberdyne-x402-services/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.
Median across 2 endpoints. Use the selector to isolate one.
checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression
Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.
COMPLIANCE
13/14 checks pass · grade A · failing: declares the current x402 version (2) · stale (probe failing)last 402 captured 2026-07-30 · last up 2026-08-23
- 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
SITE PILLARS
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
recent checks (18) live · click to expand
EMBED THIS BADGE
<a href="https://x402-list.com/services/cyberdyne-x402-services?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/cyberdyne-x402-services.svg" alt="CyberDyne x402 Services listed on x402-list" height="28"> </a>
[](https://x402-list.com/services/cyberdyne-x402-services?utm_source=badge&utm_medium=referral&utm_campaign=embed)
<a href="https://x402-list.com/services/cyberdyne-x402-services?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/cyberdyne-x402-services.svg?data=uptime" alt="CyberDyne x402 Services uptime on x402-list" height="28"> </a>