risk data for machine payments
Endpoint
api.webbersites.com/api/a11y/check
WCAG accessibility check (static analysis): findings mapped to WCAG success criteria with A/AA/AAA levels — alt text, page title, lang, form labels, heading structure, table headers, link purpose, accessible names, duplicate IDs, ARIA role validity, zoom blocking, meta refresh, skip links. Filter with ?level=A|AA|AAA. Honestly reports what static analysis cannot check (contrast, focus, keyboard).
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 4h ago | 402 | 161 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
| 4d ago | 402 | 137 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
| 4d ago | 402 | 149 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
Reference
| URL | https://api.webbersites.com/api/a11y/check |
| Sources | well-known |
| Recipient per catalogue | 0xdd5fcEa81CA6f1EB39FEd5B973DE794293B81ba6 |
| Price per catalogue | 0.010000 |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.