# CoreAI API (/docs/coreai/components/coreai-api)



Component Category [#component-category]

API backend for GenAI and agents

Component Description [#component-description]

CoreAI API is the main backend service layer for CoreAI. It hosts application logic and integrates with identity, retrieval, model access, storage, and observability services while presenting a stable product-facing API to developers and clients.

Why It Is Used [#why-it-is-used]

It gives the platform a central application service for orchestrating AI features, retrieval flows, and backend operations in a controlled way. It also protects clients from direct dependence on lower-level internal components, which means the platform can evolve its internal AI stack without changing the main developer integration surface.

Learn More [#learn-more]

* [API Reference](/docs/api-reference)
* [CoreAI Reference Architecture](/docs/coreai/reference-architecture)

Developer Guidance [#developer-guidance]

Developers should generally integrate with the CoreAI API rather than depending directly on LiteLLM, Docling, or other internal services. This keeps application integrations aligned with the platform contract and gives BullSequana AI freedom to evolve the internal implementation over time.

Interacts With [#interacts-with]

* `Keycloak` for authentication and protected API access
* `LiteLLM` behind the scenes for LLM calls and model gateway behavior
* `Milvus` for vector storage and semantic retrieval
* `Docling` for document parsing workflows
* `MLflow` for model lifecycle metadata and GenAI observability traces
* `MinIO` for object storage and document artifacts
* `PostgreSQL` for application state and transactional data
* `OpenTelemetry` for trace instrumentation and telemetry export
* `ToolHive` for MCP-oriented integrations
* Runtime ingress services that expose the API