risk data for machine payments
Endpoint
api.webbersites.com/api/extract/custom
CUSTOM EXTRACTION — POST {content, schema} and get structured JSON back. Define fields as {"company":"string","total":"number","due_date":"date"} (types or plain-language descriptions) and the engine pulls them from any unstructured text: emails, invoices, job posts, resumes, chat logs. Missing fields return null — never invented. Content up to 16,000 chars, 40 fields max. Parsing a PDF/DOCX/CSV by URL first? GET /api/extract ($0.02).
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 |
|---|---|---|---|---|---|---|
| 32m ago | 402 | 108 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
| 7h ago | 402 | 102 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
| 4d ago | 402 | 144 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
| 4d ago | 402 | 160 ms | exact eip155:8453 |
0xdd5f…1ba6 | 0.010000 | clean |
Reference
| URL | https://api.webbersites.com/api/extract/custom |
| 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.