Install Jentic One Beta

Connect the QR Invoice REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the QR Invoice REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fqr-invoice.cloud%2Fqr-invoice" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fqr-invoice.cloud%2Fqr-invoice" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with QR Invoice REST API.

Render a Swiss QR bill Payment Part & Receipt from creditorInformation, paymentAmountInformation, ultimateDebtor, and paymentReference

Merge the payment slip into an existing PDF invoice or append it on a new page

Create complete QR invoice documents from the available templates, with language set via Accept-Language

Parse and validate the Swiss QR Code in a received PDF or image, including all codes in a document

GET STARTED

Start building with QR Invoice REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use QR Invoice REST API for, with concrete tasks.

★ Agent-issued Swiss QR bills through Jentic

A bookkeeping agent issues invoices for a Swiss business: it builds a QR reference, then calls the Payment Part & Receipt operation and merges the slip into the invoice PDF. Through Jentic the X-API-Key is injected by the developer's own Jentic One instance, so the agent never holds the key.

POST /v2/qr-reference/create for customer reference '1234', then POST /v2/payment-part-receipt/merge with the invoice PDF and a QrInvoice carrying creditorInformation, paymentAmountInformation of CHF 450, and the new paymentReference

Accounts payable QR code intake

Incoming supplier bills carry a Swiss QR Code with the payee, amount, and reference. POST /v2/swiss-qr-code/parse extracts the first code from a document and /v2/swiss-qr-code/parseAll returns every code, so an agent can prefill payments without retyping IBANs.

POST the supplier PDF to /v2/swiss-qr-code/parse and return the creditor IBAN, amount, currency, and reference

Bulk payment slip generation

Monthly membership or rent runs need hundreds of slips. POST /v2/payment-part-receipt/bulk/file accepts a CSV or XLSX input and returns a multi-page PDF or a ZIP of files, while /v2/payment-part-receipt/bulk/list takes a JSON list of invoices.

POST the member CSV to /v2/payment-part-receipt/bulk/file and save the returned PDF

Payment data validation

Bad references and IBANs make bills unpayable. The API validates IBANs and QR-IBANs, QR references with modulo 10 recursive check digits, and RF creditor references with modulo 97, so an agent can check data before an invoice is sent.

POST the IBAN to /v2/qr-iban/validate and the reference to /v2/qr-reference/validate, and report whether both are valid

Key Endpoints

81 endpoints — the qr invoice rest api creates and processes swiss qr bills: it renders the payment part & receipt slip as pdf or image, generates full qr invoice documents from templates, and merges or appends the slip onto your own pdf invoices.

METHOD

PATH

DESCRIPTION

POST

/v2/payment-part-receipt

Create Payment Part & Receipt

POST

/v2/payment-part-receipt/merge

Create a slip and merge it with a PDF

POST

/v2/invoice-document

Create a QR invoice document

POST

/v2/swiss-qr-code/parse

Parse a Swiss QR Code from a document

POST

/v2/qr-reference/create

Create a QR reference

POST

/v2/qr-iban/validate

Validate a QR-IBAN

POST

/v2/payment-part-receipt/bulk/file

Bulk slips from CSV or XLSX

POST

/v2/payment-part-receipt

Create Payment Part & Receipt

POST

/v2/payment-part-receipt/merge

Create a slip and merge it with a PDF

POST

/v2/invoice-document

Create a QR invoice document

POST

/v2/swiss-qr-code/parse

Parse a Swiss QR Code from a document

POST

/v2/qr-reference/create

Create a QR reference

POST

/v2/qr-iban/validate

Validate a QR-IBAN

POST

/v2/payment-part-receipt/bulk/file

Bulk slips from CSV or XLSX

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring QR Invoice by hand means picking between its X-API-Key header and api_key query parameter, building the nested QrInvoice payload, and handling PDF and image responses yourself. Through Jentic you install once, import QR Invoice from the API Directory, store the key once, and your agent calls it.

Permission scoping

QR Invoice carries invoice data in the request body rather than in resource paths, so rules bound which operations your agent may call, not which invoice. You choose the operations it may call, so bill generation, bulk runs, or customer resource uploads are not included unless you add them.

Credential isolation

Your QR Invoice API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Swiss QR bill' or 'parse a QR code from an invoice', and Jentic returns the matching QR Invoice operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using QR Invoice REST API through Jentic.

What authentication does the QR Invoice REST API use?

The QR Invoice REST API declares two API key schemes in its OpenAPI spec: the X-API-Key header and the api_key query parameter, either of which is accepted. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I add a Swiss QR bill to an invoice PDF I already have?

Yes. POST /v2/payment-part-receipt/merge creates the Payment Part & Receipt and merges it with your PDF, and POST /v2/payment-part-receipt/append adds it on a new page instead. Query parameters such as pageSize and fontFamily control the output.

What are the rate limits for the QR Invoice REST API?

The OpenAPI spec does not specify rate limits; it notes that the demo key carries restrictions. Check the vendor site at https://www.qr-invoice.ch for the limits that apply to your key.

How do I create a QR bill payment slip through Jentic?

Install Jentic One, import the QR Invoice REST API from the Jentic API Directory, and store your API key. Your agent searches for 'create a Swiss QR bill', Jentic returns POST /v2/payment-part-receipt with its QrInvoice schema, and the agent calls it with creditorInformation, paymentAmountInformation, and paymentReference. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a QR Invoice MCP server?

You don't need an MCP server to give your agent the QR Invoice REST API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context.

Can I limit what my agent is allowed to do with the QR Invoice REST API?

Yes. For an accounts-payable agent, write a rule that allows only POST /v2/swiss-qr-code/parse, /v2/swiss-qr-code/validate, and /v2/qr-iban/validate, so it can read and check incoming bills but cannot generate bills or upload customer resources. Every call it makes is logged.

Can the QR Invoice REST API parse QR codes from received invoices?

Yes. POST /v2/swiss-qr-code/parse returns the first Swiss QR Code found in a document, and POST /v2/swiss-qr-code/parseAll returns all of them in an array. Use /v2/swiss-qr-code/validate to check a file containing a single code.

QR Invoice REST API

AI ReadinessFoundational (C-)52/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey81 EndpointsREST

For Agents

Generate Swiss QR bill payment slips and invoice documents, attach them to existing PDFs, parse QR codes from received invoices, and validate IBANs, QR-IBANs, and payment references.

Use for: I need to create a Swiss QR bill for an invoice of CHF 450, Add a QR payment slip to the bottom of my PDF invoice, Read the payment details from the QR code on this supplier invoice, Check whether this IBAN is a valid QR-IBAN

Not supported: Does not send invoices, collect payments, or keep accounting records. Use for generating, parsing, and validating Swiss QR bills and their payment references only.

The QR Invoice REST API creates and processes Swiss QR bills: it renders the Payment Part & Receipt slip as PDF or image, generates full QR invoice documents from templates, and merges or appends the slip onto your own PDF invoices. It also parses and validates Swiss QR Codes found in documents, builds and checks QR references and creditor references, and validates and formats IBANs and QR-IBANs. Bulk operations turn a list or a CSV or XLSX file into many payment slips at once.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

13%

Example Density

How richly the API is illustrated with examples.

94%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

61%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

41%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

33%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1

46%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the QR Invoice REST API to your agent

Capabilities

Start building with QR Invoice REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

QR Invoice REST API

Jentic AI Readiness Score

QR Invoice REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness