risk data for machine payments
Endpoint
api.invoket.com/label/cosmetic/ingredient/batch
Before your agent clears a cosmetic formulation for the EU market: screen a whole INCI list - up to 200 ingredients in one call - against Annexes II to VI of Regulation (EC) No 1223/2009. One verdict per item (prohibited, restricted, authorised colorant/preservative/UV filter, or not listed) with the published entries, maximum concentrations, conditions and MANDATORY label wording served word for word, plus a summary count per verdict. A malformed item or an unresolved identity is flagged at its position instead of failing the batch; the input order is preserved but no conclusion is drawn from it (an INCI list's descending-concentration order is not exploited). This is not a formulation compliance verdict: no concentration in the finished product is computed.
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 |
|---|---|---|---|---|---|---|
| 5h ago | 402 | 18 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 212 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/cosmetic/ingredient/batch |
| 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.