# CoreAI Blog

CoreAI updates and articles about AI

- [Language support in CoreAI](https://coreai.no/en/articles/language-support) — 2026-07-01 — CoreAI is multilingual on two levels: customers can ask and get answers in twelve languages even if the knowledge base only exists in one, and administrators work in a panel in Norwegian Bokmål, Nynorsk, English or German. You avoid translating and maintaining the content in several versions – and language is no longer a barrier.
- [Even better answers behind login](https://coreai.no/en/articles/answers-behind-login) — 2026-06-26 — Behind login, CoreAI fetches from internal sources you otherwise can't reach, and shows only what each individual user is actually meant to see – as an employee, member or customer. Same interface, but deeper, more precise and more personal answers.
- [Automating business-critical processes – AI as part of the system](https://coreai.no/en/articles/business-process-automation) — 2026-06-25 — CoreAI automates business-critical processes by plugging directly into the systems you already use – with an API, MCP, ready-made integrations and an automation engine that keeps the knowledge base up to date around the clock, not as yet another standalone tool.
- [A chat that fetches context itself gives better answers](https://coreai.no/en/articles/agentic-context-retrieval) — 2026-06-24 — CoreAI's agentic tool-calling lets the AI decide for itself when it needs more context and how to fetch it – it retrieves again with more precise phrasing until the answer is good enough, and handles complex questions with several criteria at once.
- [Language models on European infrastructure: coreAI now runs AI in the EU](https://coreai.no/en/articles/european-ai-infrastructure) — 2026-06-23 — coreAI now offers language models that run on European hardware and infrastructure, following a deal with OpenRouter. You choose per knowledge base whether a model runs in the EU where available, so requests are processed within the EU/EEA without data being stored or used for training.
- [From AI chat to agentic platform: coreAI reshapes the workflow](https://coreai.no/en/articles/from-chat-to-agentic-platform) — 2026-06-21 — coreAI has moved from AI chat to agentic platform: the assistant pulls fresh real-time data from the business systems via MCP and runs tasks on the user's behalf. Profixio looks up sports data in real time, and a car workshop automates 90% of the customer journey.
- [One knowledge base, both MCP client and MCP server](https://coreai.no/en/articles/mcp) — 2026-06-03 — coreAI is both an MCP client and an MCP server in the same knowledge base. As a client the knowledge base can not only fetch fresh data but also create, update and delete in other systems on the user's behalf – agentic AI that completes tasks, not just answers. As a server you expose the knowledge base so other AI agents, IDEs and internal workflows can query it over an open, vendor-neutral standard.
- [Agentic mode: coreAI builds its own context when the answer is missing](https://coreai.no/en/articles/agentic-mode) — 2026-06-02 — When coreAI cannot find the answer in the context it has already been given, it fetches it itself – in agentic mode the assistant combines semantic search, keyword search and filters against your own knowledge base, and calls external MCP tools if you have connected relevant sources. The result is more complete answers to multi-part questions, with source citations and an honest "I couldn't find it" when the answer genuinely isn't there.
- [The MCP server turns coreAI into a shared retrieval layer for AI agents](https://coreai.no/en/articles/mcp-server-retrieval-layer) — 2026-05-02 — coreAI can expose the assistant's knowledge base as an MCP server, so external AI agents — developer tools, IDEs, and internal workflows — can ask the same questions as the chat via the standard Model Context Protocol. The same curated sources sit behind both the chat widget and the MCP surface, with no copying, no separate vector index, and no scraping.
- [The MCP import in coreAI is a client integration, not a bulk import](https://coreai.no/en/articles/mcp-import-client-integration) — 2026-05-01 — The MCP import connects coreAI to an external MCP server, lists which tools the server offers, and stores the tool schemas as JSON configuration on the assistant. The actual data is only fetched when the assistant needs it during a conversation – nothing is pushed into the knowledge base.
- [How coreAI uses entity types to distinguish products, documents, and contacts](https://coreai.no/en/articles/entity-types) — 2026-04-30 — coreAI indexes your data as typed entities — `products`, `contents`, `documents`, `events`, `educations`, `job_postings`, and `contacts` — so the assistant knows whether the answer should be about a product, a PDF, or a contact person. Each entity can also carry `properties` that are later used as filters in chat and search calls.
- [Protect an assistant with your own login via callbackUrl](https://coreai.no/en/articles/protect-assistant-callbackurl) — 2026-04-29 — Set a `callbackUrl` on the assistant and coreAI calls your own URL with the user's token when the widget initializes — and only lets the user through if the endpoint responds 200. The check runs once per widget load, not per question, and the login stays with you.
- [How to fill a coreAI assistant with data via the API](https://coreai.no/en/articles/api-data-integration) — 2026-04-28 — The coreAI API lets developers fill an assistant with structured products, documents, content, events, educations, job postings, and contacts by upserting entities from their own system. Once the data is in, it can be used in chat and search.
- [How we make coreai.no visible to search, answer engines, and AI agents](https://coreai.no/en/articles/seo-aeo-agent-visibility) — 2026-04-27 — coreai.no ships finished HTML with a complete SEO head, five JSON-LD schemas, and a parallel markdown edition of every page on the same URL — so Google, ChatGPT, and Claude all see exactly what the author wrote. We use Prezet and two Spatie packages for the routine parts, and build the bits that actually move visibility ourselves.