Developer documentation
Jithox MCP servers return one machine-readable decision with the evidence behind it and a signed receipt you can verify offline. Read-only: they never send anything on your behalf.
Free to start
Quickstart
Zero to a verified tool call with a signed receipt: credential, OAuth, initialize, tools/list, first call, and what happens when the free calls run out.
Products and endpoints
What each MCP server does, its canonical tools, its price per accepted call, and its live availability.
Pricing and credit
One shared balance across products, prepaid packages, what is chargeable and what is always free.
Billing and receipts
Your balance, your usage, your signed receipts and how a refund behaves.
What you can rely on
These are properties of the implementation, not promises in a brochure — each one is enforced server-side and covered by tests.
You pay only for an answer
A call is charged when it produces an accepted, usable result. Errors, refusals, rate limits, kill switches and upstream outages settle at €0,00.
Prices are server-side
The price comes from one catalog at reserve time. A client cannot name an amount, and a retry replays instead of charging twice.
Money is reserved before execution
The balance is held, the call runs, then it captures or releases. A lost response cannot double-charge you.
Truthful source states
When an official source is unavailable, you get a typed unavailable — never a guess dressed as an answer, and never a stale list presented as current.
Signed receipts
Every accepted call produces a receipt signed with the product's own key, verifiable offline against a published key.
One balance, scoped credentials
Credit lives on the workspace, never in a token or a credential; rotating a credential leaves your balance and free calls untouched.
What we do not claim
We tested whether routing these checks through Jithox produces safer conclusions than calling EU VIES and the Peppol SMP directly. Across 360 blinded paired runs the unsafe decision rate was zero on both sides — a capable model already tells “the source could not answer” apart from “the answer is no” without us.
So we do not claim better answers, and we do not price on answer quality. What is genuinely different is the evidence: an explicit source state, a budget you set, an accounting trail, and a signed receipt that verifies offline. A direct API call produces none of that.
- It never sends an invoice, to Peppol or anywhere else.
- It does not combine the checks into one counterparty verdict. Each check is its own tool, and your agent decides what the combination means.
- It is not legal or tax approval, and it is not a compliance statement.
- It has not been independently penetration-tested.
Who can use it
Anyone, anywhere. You do not have to be an EU business to call these servers — the capabilities are about European rules, not about where you are registered. Nothing in the trial asks for a Belgian postcode, a phone number or a company registration; an e-mail address and a client are enough.
Start
The quickstart takes a few minutes and needs no card.
Designed to support workflows and auditability, not to replace professional legal or tax judgment.