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.

For: Teams building an AI agent, ERP integration or AP/AR workflow that prepares EU e-invoices.

What your AI agent can do

• Check the syntax of a VAT number and verify it against the EU VIES service.
• Look up whether a participant is reachable on the Peppol network.
• Validate the structure of a prepared invoice payload.
• Report the configuration state of your own Jithox workspace, and the next safe step for it.
• Return every answer with the source it came from and the time that source was consulted — so an agent can tell a confirmed result from one where the source simply could not answer.

Exactly what it does not do

• 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.
• It does not tell you whether an invoice is legally valid or fiscally correct.
• A negative answer means one source returned no match at that moment — never that a company is unregistered or non-compliant.

Data sources

• EU VIES (VAT number verification)
• Peppol participant directory
• Belgian KBO/BCE company register

A readiness answer describes what the consulted sources returned at the stated time. It is not a legal, fiscal or compliance statement.

Read-only, and 5 tools

This capability exposes 5 tools. Every one of them reads. There is no tool that writes, sends, files, pays or publishes — not disabled, not permission-gated: absent.

• validate_invoice
• validate_vat_number
• verify_vat_vies
• lookup_peppol_participant
• get_einvoice_readiness

Availability

Live on a public endpoint: https://mcp.jithox.com/mcp. It speaks Streamable HTTP with OAuth 2.1 and PKCE (S256).

A client-neutral acceptance evaluation with external MCP clients is still in progress: no desktop or IDE GUI client is proven end to end yet, and the authorization endpoint requires the RFC 8707 resource parameter, which not every client sends. Ask us before you commit and we will test your client — and tell you honestly if it does not work.

The pilot

• 14 days, starting when your access is issued.
• One invoice or Peppol readiness workflow.
• Up to 200 accepted tool calls, max 50 per day and 10 per minute. A call counts against your budget when it reaches a tool and returns an answer — including a truthful “no match”, a partial result, or a report that a source could not answer. A truthful negative is a real answer and is billed as one. A rejected or malformed request never reaches a tool and is not counted. The daily cap resets at 00:00 UTC, not 24 hours after your first call.
• Scoped to this product only (einvoice:validate, vat:format, vat:vies, peppol:lookup, einvoice:readiness). The credential does not work on any other Jithox capability.
• A signed receipt for every accepted call, verifiable with a published public key.
• Onboarding at the start and a closing review at the end.
• A pilot does not renew automatically and does not become a subscription. When the 14 days end, access ends.

Privacy and security

• The application form asks for business contact details and your use case. It never asks for a card number, a bank credential, an API key or an MCP token, and it rejects a submission that contains one.
• Access uses OAuth 2.1 with PKCE. Hosted client_credentials is not supported.
• Your credential is shown once, to you. It is never written to a log, a receipt or this website’s database.
• Your pilot can be suspended or revoked at any time, by you or by us, and it expires by itself after 14 days.
• A receipt records what was asked and what was answered — as fingerprints, not as your raw query values.

What a signed receipt is

Every successful call produces a small signed document recording which capability answered, which tool ran, which sources were consulted, and when. You can verify the signature yourself with our published public key, off our infrastructure. It is evidence that an answer was given at a moment in time — it is not a statement that the answer was legally correct, and it does not certify anything about the underlying data.

Start a paid pilot →

Submitting the form charges nothing and creates no access. A person at Jithox reviews it and comes back to you.