risk data for machine payments
Endpoint
api.invoket.com/label/claims/check
Before your agent puts a nutrition or health claim on an EU food label: is the proposed wording an authorised claim (exact legal wording + conditions of use), a non-authorised one (official rejection reason + EFSA opinion), or absent from the EU Register (Regulation (EC) 1924/2006)? Post the label wording (and optionally the nutrient); matching is strict-normalised (case, punctuation, spacing), exact or containment, never fuzzy - zero false positives. The Register carries the REJECTED claims a plain LLM validates by mistake. An absent wording returns the authorised claims for the nutrient plus a limit note (absence is neither authorisation nor prohibition - 'on hold' botanicals are not in the Register).
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 |
|---|---|---|---|---|---|---|
| 2h ago | 402 | 20 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 10h ago | 402 | 17 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 210 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 210 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
Reference
| URL | https://api.invoket.com/label/claims/check |
| Sources | well-known |
| Recipient per catalogue | 0x4465825B0ac713aA2Fa07Ea29023020804A128ee |
| 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.