Integration in a browser tab
The browser app offers optional action integration only in the open tab. It is available by default after accepting current terms, with the same company, client, scope and action approvals. You can disable it in Settings. A compatible extension of your choice is required; we do not currently provide an extension installation package. This is not a remote MCP server.
- Open proRēķins in your browser and accept the current terms.
- Open AI assistants in Settings and review the data disclosure. You can disable the integration.
- Select a specific own company. The app does not select it automatically.
- On the first request, review the client name, company and requested permissions in the app.
What do you approve?
Permission is bound to the session, account and selected company. The partner directory has a separate scope. The assistant cannot enable automation, accept terms, read VID keys or make a purchase. The connecting program supplies its client name; it is not a certified identity.
- Searching and reading facts: the access you grant.
- Issuing, edits, deletion and status changes: fresh confirmation of the concrete action.
- File delivery, backup merge and VID: separate confirmation.
- Issuing through an assistant does not automatically send to VID. Submission is a separate action.
Try a draft first
- “Prepare a consulting invoice draft and show the VAT totals.”
- “Find unpaid invoices for this company.”
- “Validate this incoming XML and explain discrepancies.”
- “Preview this invoice in a different PDF style without exporting it.”
The same allowances as the app
An assistant does not bypass the subscription. Issuing a new bill counts once. Each new confirmed PDF delivery uses the PDF allowance, including incoming invoices and new styles. Reading chunks of the same approved file does not count again. XML and PNG previews remain free.
Free: 3 bills and 3 PDFs per month on the device. Pro: 20 bills, 20 PDFs and 10 EDS imports per month per account. Max: unlimited. Subscription explanation.
Where does the data go?
The integration runs in the open tab. CORE has no MCP endpoint receiving invoice content. However, facts, XML or previews you share with an AI client may be sent to that client’s external AI service under its settings and policies. Review them before granting access.
Files use temporary, session-owned identifiers. The integration does not accept arbitrary file paths or expose credentials. Do not retry an uncertain VID or issuing result before checking the app history.
Machine-readable description
- mcp.json: integration description; there is no remote MCP server
- llms.txt · llms-full.txt: product summary for language models