risk data for machine payments
Endpoint
api.invoket.com/invoice/vat-treatment
Before your agent issues or books a cross-border invoice: who charges the VAT, under which mechanism, where the supply is taxed and with which compulsory wording. Post one transaction (countries, goods or services, business or consumer customer, supply kind, date, optional amount) and get a determination sourced article by article under Directive 2006/112/EC: place of supply, person liable, standard VAT, reverse charge, intra-Community exemption or out of scope, the rate in force at that date, and the exact invoice mentions to print. An invoice missing its reverse-charge mention passes the EN 16931 rules and is still refused by the tax authority - the check /invoice/validate cannot make. The customer's VAT number is taken AS DECLARED (zero network): verify it live with /company/vat. Uncovered regimes (OSS/IOSS, import VAT, margin schemes, triangulars) come back as a motivated undetermined, never a plausible default.
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 | 44 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 9h ago | 402 | 29 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 211 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
| 4d ago | 402 | 415 ms | exact eip155:8453 |
0x4465…28ee | 0.010000 | clean |
Reference
| URL | https://api.invoket.com/invoice/vat-treatment |
| 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.