A2A Agent Card · jithox-com

Jithox

Provider: jithox-com Card identifies: Jithox (Victor-Emmanuel Charlier, KBO 1039.898.594) Conformance: Conformant Protocol: 1.0 Transport: Version: 1.0.0 Host: app.jithox.com Skills: 5
Discovery

An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.

https://app.jithox.com/.well-known/agent-card.json
Interfaces
https://jithox.com/api/mcp · transport · protocol https://modelcontextprotocol.io/specification/2025-11-25/basic/transports#streamable-http
Skills (5)

Check a payment before an agent makes it preflight_payment

For a structured invoice, call review_invoice first. Leave approved out when no human approval was supplied: the checks still run, but the verdict is at least review_required. Call this once before you move money for a person: it compares what the person approved (payee, amount, currency) with what is about to be paid and runs the checks for the payment rail — IBAN and a changed bank account for an invoice. Returns stop, review_required or no_blockers_found, with every check, what it does not prove, how long it took and a signed evidence token. It never pays and never says safe: a check that did not run or did not answer is listed as such and is never a pass.

paymentibanfraudaccounts-payable

Check an IBAN verify_iban

Check a payment account number (IBAN) before paying or before sending an invoice: ISO 13616 structure and ISO 7064 check digits, for 70+ countries, offline and free. Catches the single mistyped character a format check cannot. Optionally reports whether the account is issued in the country of the party being paid — as an observation, not a fraud verdict. It never claims the account exists or who owns it.

paymentiban

Check an e-invoice against Peppol rules check_peppol_ready

Before you send an e-invoice: will the Peppol network accept it? Checks the invoice against 21 published Peppol BIS Billing 3.0 rules — the ones that actually fail in practice: a missing buyer or order reference, a missing electronic address for either party, an address stated under a scheme code that does not exist, totals that do not add up, a date in the wrong format. It ALSO looks the customer's address up in the Peppol SML, so a verdict of 'ready' means the receiver is really on the network; a receiver that is not registered is reported as will_be_rejected, and one that could not be looked up is 'unverified', never a pass. Every finding names the official rule (PEPPOL-EN16931-R003, BR-CO-15 …), quotes its text and says what to change. Free. It checks a listed subset of a much larger rule set and is not the official validator: a clean result means nothing among these rules is wrong and the receiver exists, never that the network will accept the document.

e-invoicepeppol

Can this company receive a Peppol e-invoice? lookup_peppol_participant

Not a VAT or company-register check; use kbo_company_search (one company) or check_vat_list (a list). Can this customer receive an e-invoice over Peppol today — and if the send still fails, is it his problem, yours, or your software's? Asks the live Peppol registers about a THIRD PARTY: the public directory, the lookup the network uses today, and the lookup Peppol retired. Returns whether he is reachable, which document types his access point accepts, and — the part nobody else answers — who to call when it still does not work. A customer found by the current lookup but not by the retired one is reachable, and software reporting him as absent is asking the question Peppol retired: a message for the software vendor, not for the customer. Free, read-only, nothing stored. Do not confuse it with check_peppol_ready, which checks YOUR OWN invoice against the rules and only asks whether the address on it is registered. It is never a promise that an invoice will arrive, be accepted or be paid — every answer says so.

e-invoicepeppolregistry

Check a changed supplier bank account check_payment_change

A supplier says their bank details changed: check the request before the vendor record is touched. Validates the new IBAN (structure and check digits, 70+ countries), compares it with the account on file, and flags an account that moved to another country or sits outside the supplier's country. Returns no_change, verify_first, stop or invalid_new_account, with the call-back steps a person must still take. Offline and free. It never says an account is safe, and never claims who owns it.

paymentibanfraudaccounts-payablepay invoice safelyinvoice fraudsupplier bank changepayment verification
Documentation
Evidence. Fetched 2026-10-29 from https://app.jithox.com/.well-known/agent-card.json, HTTP 200. The body was saved verbatim and is the sole source for everything on this page — no field is inferred. View the captured card. Providers change what they serve; if this card has moved or changed shape, the provider profile carries the current state as of the last build.

Work with this as data

Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for a2a agent cards

3 MCP tools reach this
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
Search the catalog
curl "https://apis.io/api/v1/search?q=jithox-com&limit=10"
Everything under a tag
curl "https://apis.io/api/v1/tags/jithox-com"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.