Coretool integration
Coretool is a German e-invoicing service. An agent can create an e-invoice file from seller, buyer, line item and payment data (a ZUGFeRD PDF with embedded XML, XRechnung CII or UBL XML for German public authorities, or Peppol BIS Billing 3.0 XML), validate an e-invoice file with the official KoSIT validator (each finding with its rule code, an explanation and a fix hint), check a Leitweg-ID and read the key's quota. Creating, validating and Leitweg checks each use one call of the account's quota (3 free calls per account at the time of writing, more on request); a test key (ct_test_) costs nothing and produces watermarked samples with TEST- numbers. Invoices carry the names, addresses and bank details of the parties, which can be personal data; Coretool processes them in memory and does not store them. API-key management (it needs a Coretool login session) and the detailed validation step report are not exposed. Authentication is an API key (ct_live_ or ct_test_) created in the Coretool account (Mein Konto, Konto, API-Schluessel) and sent in the X-API-Key header; each key may make 60 calls per minute and 1,000 per day (test keys 20 and 200), file validation at most 30 per minute.
Say what should happen.
The workflow builds itself.
What you can do with Coretool
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Invoice, 2 operations
create_invoiceCreate invoicePOSTAgents: ask firstCreates a German e-invoice file from seller, buyer, line items and payment: a ZUGFeRD PDF (default), XRechnung CII or UBL XML, or Peppol BIS XML. Billed: uses one call of the quota (a test key makes a watermarked sample).validate_invoiceValidate invoicePOSTAgents: ask firstValidates an e-invoice file (XRechnung UBL or CII XML, ZUGFeRD or Factur-X PDF, Peppol BIS XML; max 5 MB) with the official KoSIT validator: valid, result and each error's rule code, explanation and fix hint. Billed: one quota call.
Api key, 1 operation
verify_api_keyVerify api keyGETAgents: ask firstChecks that the connected API key is valid and returns its key id and the account's quota. Free: uses no quota and counts only toward the rate limit.
Leitweg id, 1 operation
validate_leitweg_idValidate leitweg idPOSTAgents: ask firstChecks a German Leitweg-ID (the routing ID of a public-sector buyer for XRechnung): structure and MOD 97-10 check digits. An invalid ID is a normal result (gueltig false), with messages in German and English. Billed: one quota call.
Usage, 1 operation
get_usageGet usageGETAgents: ask firstReturns the plan and the free calls total, used and remaining of the API key's account, with the key id. Free: uses no quota.
Use Coretool from Claude Code, Cursor or Codex
Connect Coretool in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Coretool operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Coretool
- Create your workspace
Sign up free. Nothing to install.
- Connect Coretool once
Add your Coretool connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Coretool integration FAQ
What can you do with the Coretool integration?
LiveContext exposes 5 operations on Coretool, covering invoice, api key, leitweg id and usage.
