Invoket

Invoket documentation

Invoket serves the checks your agent runs before it acts: verify a bank account before paying, a phone number before messaging, a law before advising, the weather before deciding, a vehicle before buying. Each check is computed from official sources, and every response carries its provenance (data + provenance: source, fetch time, freshness).

What your agent can check

  • Before your agent commits — the pre-flight composites: one call runs a whole family of checks and returns a single verdict (ok, review, stop, insufficient_coverage), with every reason attached to the block and the dated source it came from. Because the composite reports its own coverage, an ok is impossible while a check did not happen — see /preflight/payment for a transfer and /preflight/supplier for a counterparty.
  • Before your agent pays — bank-account checks (resolve, repair, screen) backed by national bank registries, the EPC register and the OFAC/EU/UN & FATF lists.
  • Before your agent messages — phone-number checks backed by libphonenumber (offline).
  • Before your agent advises or signs — law-in-force checks (text at a date, history, diff) backed by LEGI (Légifrance) and EUR-Lex.
  • Before your agent plans or insures — weather and climate checks backed by Copernicus ERA5, NOAA GFS/GEFS and the WMO 1991-2020 normals.
  • Before your agent buys a vehicle — vehicle checks backed by NHTSA vPIC, RappelConso and the official Crit’Air tables.

The full, live list — with prices and machine-readable payment details — comes from the gateway’s /catalog. Each endpoint has a reference page under /docs/api.

Who it is for

  • Autonomous agents about to pay, message, advise, plan or buy: they discover an endpoint, run the check and read the provenance — no human onboarding at any step.
  • Developers wiring those checks into an agent or a backend, without creating an account or handling monthly billing.

How access works

Every endpoint is paid per call, in stablecoin, over the x402 standard (HTTP 402 Payment Required) — no account, no API key. Some endpoints offer one free call per day — the catalog says which. And you only pay for answers: a call that fails is never settled.

  • How it works — the 402 → signed payment → response loop.
  • Quickstart — call a paid endpoint end to end.
  • MCP server — the least-friction path: one line of config gives an MCP host (Claude Desktop, Claude Code) paid access.
  • Payments and rails — accepted stablecoins and networks.
  • For agents — discover the endpoints the machine-readable way.

What the site describes (and does not do)

This site is the storefront: it describes, points and references. It processes no payment. The payment logic lives in the gateway, served on api.invoket.com, whose endpoint catalog is read live from /catalog.