About Invoket

Who operates it

Invoket is built and operated by Matthias Begot, an independent developer. There is no team behind the byline: the same person builds the gateway, the microservices that answer behind it, and publishes this documentation and every article on the blog — and is accountable for what they claim.

The first line of the gateway was written in June 2026, and the endpoints have been publicly payable since. The project is young, and this page will say so for as long as it is true: prefer the dated provenance in each response over any claim made here.

Questions, a bug, or a source that looks wrong: contact, or matthias.begot@gmail.com.

What the gateway does

One HTTP call, one check, one payment. The gateway on api.invoket.com answers 402 Payment Required with a price, verifies the signed stablecoin payment, then runs the check and returns the result — no account, no API key, no subscription, and no human in the loop. A payment is settled only when the call actually succeeds: a malformed request, an unanswerable query or an internal error costs nothing.

The live list of endpoints, with prices and payment details, is served by the gateway's /catalog — this site reads it, it never restates it. See how it works for the payment loop and endpoints for what is currently served.

What it does not do

• It does not advise. An endpoint returns what an official source states — an article of law in force at a date, a harmonised classification, a documented drug interaction. It is not legal, medical or financial advice, and it produces no opinion on your situation.
• It invents no verdict. When a source does not cover a case, the answer says so — an unknown value, an incomplete coverage flag — rather than guessing. Absence of data is reported as absence of data.
• It is not a data reseller. Checks are answered one question at a time; the underlying datasets are public and are not redistributed in bulk here.
• This site handles no money. It describes, points and references. Every payment happens between your client and the gateway.

Where the answers come from

Every check is computed from official, publicly available sources. Most of them are ingested, dated and served from our own copy, so that an answer does not depend on a third party being up at the moment your agent asks; a few endpoints do query an official service on the spot, and their response says so. Nothing here is scraped from a competitor's API, and no proprietary dataset is resold.

Before your agent commits — every check in one call

national bank registries · OFAC/EU/UN & FATF lists · INSEE Sirene · BODACC gazette · VIES · GLEIF LEI reference

Before your agent pays

national bank registries · EPC register · OFAC/EU/UN & FATF lists

Before your agent trusts a name or an address

OFAC SDN & Consolidated · EU financial sanctions list · UN Security Council list

Before your agent messages

libphonenumber (offline)

Before your agent advises or signs

LEGI (Légifrance) · EUR-Lex · official public-holiday calendars

Before your agent plans or insures

Copernicus ERA5 · NOAA GFS/GEFS · WMO 1991-2020 normals

Before your agent buys a vehicle

NHTSA vPIC · RappelConso · EU CO2 monitoring dataset (Regulation (EU) 2019/631) · French registration-tax schedules (Légifrance) · official Crit'Air tables

Before your agent books an invoice

EN 16931 semantic model · Factur-X / CII D16B / UBL 2.1 specifications · Directive 2006/112/EC and the Commission's TEDB rate database · Directive 2011/7/EU and its national transpositions

Before your agent onboards a counterparty

INSEE Sirene register · BODACC gazette · VIES · Peppol directory · GLEIF LEI reference

Before your agent acts on a prescription

BDPM (ANSM/HAS) · openFDA · RxNorm

Before your agent ships an EU label

ECHA Annex VI (CLP) · Regulation (EC) No 1223/2009, Annexes II to VI (EUR-Lex) · Regulation (EC) No 1333/2008, Annexes II and III (EUR-Lex)

Provenance in every response

A verdict you cannot audit is worth nothing to an agent. Every response carries a provenance block next to its data: which source answered, when it was fetched, and how fresh it is — live for a call made to an official service on the spot, cached for a recent copy, snapshot for a dated ingest, with the date of that ingest attached.

That block is the honest part of the product: it lets your agent decide whether an answer is fresh enough to act on, and it lets you check ours against the source. When a snapshot ages past what an answer can support, the endpoint says so in the response — it does not fail, and it does not pretend.

The machine-readable side of all this: for agents, llms.txt and the x402 manifest.