Summary
The European e-invoice formats, without learning their XML.
Factur-X, XRechnung and Peppol are the kind of standards where the specification is long and the acceptance rules are unforgiving. This puts the format work behind an API call, and the same server runs on your infrastructure or InvoiceXML's depending on how you want the credentials held.
What it is
The InvoiceXML API exposed to agents. The same build runs two ways: on your own machine against a single API key, or hosted by InvoiceXML with OAuth and dynamic client registration.
What you get
- The Factur-X and ZUGFeRD hybrid invoice formats
- XRechnung, the German public-sector invoice standard
- UBL and CII, the two underlying XML syntaxes
- Peppol BIS Billing 3.0, the profile used for cross-border exchange
- One deployment shape you choose at startup — self-hosted with a key, or hosted with OAuth
Requirements
Self-hosted, an InvoiceXML API key placed in the environment or in appsettings.json; hosted, an account authorized over OAuth. The host serves the MCP endpoint over HTTP, with a health check beside it.