xrio

View saved version →

---
name: xrio
description: Check, create and read German e-invoices (XRechnung, ZUGFeRD / Factur-X) with the xrio MCP server. Use when the user wants to validate an e-invoice file, create an e-invoice from invoice data, a document or free text, turn an e-invoice XML into a readable PDF, get a download link for a file xrio created, or keep the company data, bank accounts and logo of the user's invoices.
---

# xrio — German e-invoices

xrio is a processing API with an MCP server named `xrio`. Its tools describe themselves; this
skill adds the order of the steps and the rules around them.

## Rules

- **Never handle the API key.** Do not ask for it, do not accept it in the chat, never write it
  into a file, a command or a tool argument. The user creates it in the xrio portal
  („API-Schlüssel“) and sets it themselves — as the environment variable `XRIO_API_KEY` or in
  the prompt of their client. A client that signs in to xrio through the browser (OAuth — Claude,
  ChatGPT, Claude Code without a key) needs no key at all.
- **Files never travel through the chat.** No file content and no base64 in a tool argument. A
  file to check goes to an upload link with `curl`; created files come back as download links
  on `api.xrio.de` — `curl -o <name> <downloadUrl>` fetches them. In claude.ai an attached file
  sits in your sandbox; sending it needs the user's setting „Ausgehenden Netzwerkverkehr
  erlauben“ (Einstellungen → Funktionen → Codeausführung und Dateierstellung) with `api.xrio.de`
  among the additionally allowed domains — a 403 from the sandbox proxy means it is missing: ask
  the user to add it. A chat
  without a shell, or without that setting, sends the user to the xrio portal instead: the page
  Testen checks a file or makes its PDF view, the page Firmendaten takes the logo. Never ask
  for the file's content.
- **Official sources, no tax advice.** Report findings with rule, wording and source as xrio
  returns them. Which invoice type, tax category or exemption applies is the user's decision —
  say so instead of choosing.
- **Never guess invoice values.** VAT IDs, tax numbers, IBANs, addresses, dates, amounts and the
  Leitweg-ID come from the user or their documents. Ask for anything missing.

## Check an e-invoice

1. Call `validate_invoice`. It returns `uploadLink` — single use, valid 10 minutes.
2. Send the file as the raw request body: `curl --data-binary @<file> <uploadLink>`.
3. Report the `verdict`: `valid`, `invalid` or `notEInvoice` (a PDF without embedded invoice
   XML). For `invalid`, list each finding with `rule`, `requirement` and `source`; call
   `lookup_rule` with the rule ids when the user wants the full official wording of a rule.
4. A used or expired link answers 404 — call `validate_invoice` again. Files over 10 MB are
   refused (413).

Checking costs the account's validation price from its prepaid credit (the tool description
names the default) for a verdict `valid` or `invalid`; a file xrio created for the account, a
PDF without an e-invoice and errors are free — `costCents` in the answer says what it cost. xrio
keeps nothing of the file.

## Turn an XML into a readable PDF

1. Before the paid call, tell the user the price: one document from the prepaid credit.
2. Call `render_invoice`. It returns `uploadLink` — single use, valid 10 minutes. Send the XML as
   the raw request body: `curl --data-binary @<file> <uploadLink>`.
3. A PDF view comes back in `files` — give the user its `downloadUrl` and pass on every entry
   of `notices`: the PDF view is not an e-invoice, the XML stays legally authoritative. With
   `verdict` `invalid` (the account renders invalid XML by setting) also say that the XML is no
   valid e-invoice and list its findings.
4. An invalid XML without that setting returns its `findings`, the notice `RENDER_NEEDS_CONSENT`
   and costs nothing. Report the findings like a check, then ask the user: a PDF view of the
   invalid XML costs one document and is marked invalid on every 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.