Developers

Tools for developers and AI agents.

Connect Jithox tools to your AI client. Find MCP servers, supported connections, documentation and machine-readable contracts. Each tool has its own scope, availability, access requirements and price source.

Connect Kit: Published on npm as `jithox` (0.2.4). Install: npm install -g jithox@0.2.4. Commands in the published version: auth, call, connect, disconnect, discover, doctor, init, status, test. Not yet installable (0.3.0, approved artefact): --version, file-to-data, run. Setup availability and alternatives.

Free access, right now

25 accepted tool calls, 14 days, no card. Activation is automatic — there is no form to fill in, nobody to email and nothing to wait for.

Activate free access

Three ways in. Pick one.

Each one below is a whole journey: connect, find a task, run it, hold the result. The first call costs nothing and needs no account.

MCP client

Claude, Cursor, or anything else that speaks MCP.

Access: No credential for the free tools on https://jithox.com/api/mcp — discovery is open and a free tool answers straight away. A priced tool on that same endpoint needs a bearer token. This is not the OAuth endpoint; do not bring a credential from elsewhere.

1 · Point your client at the endpoint

https://jithox.com/api/mcp

2 · Ask what it has

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

3 · Run one

{"jsonrpc":"2.0","id":2,"method":"tools/call",
 "params":{"name":"check_payment_change",
  "arguments":{"newIban":"DE89370400440532013000",
               "ibanOnFile":"BE68539007547034",
               "supplierCountry":"BE"}}}

4 · What comes back

"verdict": "stop"
"flags": [ "account moved to another country" ]
"requiredSteps": [ "Call the supplier on the number you already had" ]

Terminal

One command, a real answer, and a receipt you keep.

Access: None for a free tool. The credential, when you need one, is read from a file or your OAuth login — never from a command argument, because arguments end up in shell history.

1 · Install the published version

npm install -g jithox@0.2.4

2 · See what is reachable

jithox discover

3 · Make one real call

jithox call verify_iban --input '{"iban":"BE68539007547034"}'

That line is written for bash. JSON on the command line is quoted differently per shell, so on PowerShell use jithox call verify_iban --input '{\"iban\":\"BE68539007547034\"}' and on cmd.exe use jithox call verify_iban --input "{\"iban\":\"BE68539007547034\"}".

4 · What comes back

status   valid
country  BE — matches the supplier
receipt  written to ~/.jithox/receipts

These are the commands version 0.2.4 actually has. Newer commands exist in the repository and are not shown here until the registry serves them. What is published, and what is not.

Plain HTTP

Anything that can post JSON — .NET, Python, a spreadsheet macro, a webhook.

Access: None for this route. It reads no session, stores nothing, and makes no network call of its own.

1 · Post an invoice

curl -X POST https://jithox.com/api/invoice/review \
  -H "content-type: application/json" \
  -d '{"invoice":{ … }}'

2 · What comes back

"checks":   structure, arithmetic, payment details, Peppol
"findings": [ { "what": …, "fix": … } ]
"export":   a Peppol BIS 3.0 document

3 · Measured

HTTP 200 in 0.18 s, from a cold client, 2026-09-19

The structural and arithmetic checks are free and anonymous. Checking both VAT numbers against the EU register needs a signed-in workspace with credits, and is charged only when the register actually answered.

Checking a list of EU VAT numbers from a .NET or other backend, with a key? REST API: curl and C#

What is publicly available

Jithox E-Invoice Readiness
Before you send a structured e-invoice you need to know whether the counterparty's VAT number resolves and whether they can actually receive one on the Peppol network — two checks that are easy to get wrong by hand and expensive to get wrong at scale.
5 read-only tools: validate_invoice, validate_vat_number, verify_vat_vies, lookup_peppol_participant, get_einvoice_readiness
Jithox EU Energy Label Preflight
A product listing that shows the wrong energy class or a missing EPREL registration is a listing that gets pulled, and checking a catalogue against the official EPREL database by hand does not scale past a handful of models.
5 read-only tools: search_eprel_products, get_eprel_product_record, get_eprel_energy_label_data, compare_eprel_product_metrics, prepare_energy_label_preflight_receipt
Jithox EU Import Preflight
Before goods are ordered from outside the EU, somebody has to find the right commodity code, check which import measures attach to it, and confirm the counterparty's EORI number — usually by hand, across several official portals.
5 read-only tools: validate_eori, search_taric_codes, check_eu_import_measures, estimate_low_value_import_cost, prepare_import_preflight_receipt
Jithox EU Counterparty Sanctions Preflight
Onboarding a new supplier or counterparty means screening them against the EU sanctions list, and the screening is only worth anything if you can show afterwards exactly what was checked, against which list version, and when.
5 read-only tools: screen_sanctioned_name, screen_sanctioned_identifier, get_sanctions_listing, list_sanctions_regimes, prepare_screening_receipt

Machine-readable sources

If you are an agent rather than a person, start at the agent context. It names every document below and says what each one is authoritative for, so you never have to guess which answer is current.

Agent context /api/agent-context/v1: Start here if you are a machine. Names every document below and what each one is authoritative for.
Gateway bootstrap v2 /api/agent-bootstrap/v2: Gateway endpoints, native client setup and the verified availability of Connect Kit distribution.
Capabilities /api/capabilities/v1: What Jithox can do, which endpoints answer publicly (publicly_available), and which capabilities are offered for sale (release_state, access_mode).
Pricing /api/pricing/v1: What access costs and what the free tier includes.
Changelog /api/changelog/v1: What changed, and how well each change is known.
llms.txt /llms.txt: A compact overview of Jithox as a whole.
Agent skill /SKILL.md: Instructions an agent can load: every endpoint, the three access routes, and what each error means.
Quickstart /docs/quickstart: Copyable terminal commands from discovery to a first call and its receipt.

Honest limits

A readiness answer describes what the consulted sources returned at the stated time. It is not a legal, fiscal or compliance statement.
It does not combine the VAT, company and Peppol checks into a single counterparty verdict. Each check is its own tool, and your agent decides what the combination means.
It does not send an invoice, to Peppol or anywhere else.
It does not create, book or file an invoice.
There is no SLA, and no independent penetration test has been performed.

Three different things called paying

Paying for Jithox use — an agent does this on its own. A priced tool deducts from your balance per answer, and the remaining balance comes back on every call. No human is in that loop.

Adding to the balance — a person, once, on the top-up page. An agent cannot buy credits, and nothing on this page is a purchase.

Buying something from a third party for your customer — Jithox does not do this at all, in any route.