# CoreAI Blog

CoreAI updates and articles about AI

- [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 coreAI uses entity types to distinguish products, documents, and contacts](https://coreai.no/en/articles/entity-types) — 2026-04-29 — 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.
- [The MCP import in coreAI is a client integration, not a bulk import](https://coreai.no/en/articles/mcp-import-client-integration) — 2026-04-29 — 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.
- [The MCP server turns coreAI into a shared retrieval layer for AI agents](https://coreai.no/en/articles/mcp-server-retrieval-layer) — 2026-04-29 — 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.
- [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.