risk data for machine payments
Endpoint
api.invoket.com/invoice/generate
Before your agent bills a customer: get the invoice document itself, ready to send and archive - not a verdict on someone else's file. Post simple business JSON (parties, lines, VAT), receive XML already cleared by the full official EN 16931 rule set, totals computed, inconsistent input refused field by field. CII by default (Factur-X EN 16931 URN), syntax=ubl for UBL 2.1, ruleset=peppol for Peppol BIS Billing 3.0. vat_treatment writes the reverse charge or intra-Community exemption mention.
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 |
|---|---|---|---|---|---|---|
| 6h ago | 402 | 29 ms | exact eip155:8453 |
0x4465…28ee | 0.100000 | clean |
| 4d ago | 402 | 410 ms | exact eip155:8453 |
0x4465…28ee | 0.100000 | clean |
| 4d ago | 402 | 207 ms | exact eip155:8453 |
0x4465…28ee | 0.100000 | clean |
Reference
| URL | https://api.invoket.com/invoice/generate |
| 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.