Service health check endpoint at GET /health.

Query history retrieval and SQL query execution are related analytical functions exposed by analysis.py.

Endpoint /insights/{project_id} in backend/api/analysis.py for obtaining project insights, status unspecified.

Lists recent background jobs via backend/app/api/jobs.py. Getting the status of a specific job is part of the overall job listing and monitoring endpoints in jobs.py.

API endpoint in backend/app/api/jobs.py. Retrieves status, progress, and results of a background job. Getting the status of a specific job is part of the overall job listing and monitoring endpoints in jobs.py.

Getting and updating the current user's information are related operations in auth.py.

Endpoint to list all findings for a project at /projects/{project_id}/findings. The message sending endpoint for sessions and the retrieval of project findings are related agent functionalities within the same backend context. Listing findings for a project and updating individual findings are related operations for managing findings. Generating a report from selected findings uses the list of findings available for the project. Running a GDPR scan on a project may use findings data as part of its process.

Returns a snapshot of current processing status in backend/app/api/progress.py. Streaming real-time processing progress and returning a snapshot of progress status are complementary progress reporting endpoints.

Streams real-time progress updates for project processing via backend/app/api/progress.py. Streaming real-time processing progress and returning a snapshot of progress status are complementary progress reporting endpoints.

List all agent sessions for a project at GET /projects/{project_id}/sessions.

Endpoint /projects/{project_id}/tables in backend/api/discovery.py for listing project tables, status unspecified.

API endpoint to retrieve session details and message history at /sessions/{session_id}.

Retrieve skill execution logs for a session at GET /sessions/{session_id}/logs. Sending a message in a session and retrieving skill execution logs both relate to the same session in agent backend.

/visualizations/{query_id} endpoint in backend/api/analysis.py for retrieving visualizations, currently no status available.

Endpoint /{file_id} in backend/api/files.py for retrieving file details, status unspecified.

Catalog retrieval endpoint in backend/api/files.py, status unspecified.

Download endpoint in backend/api/files.py, status unspecified.

Get project details endpoint, status unspecified.

List project files endpoint, status unspecified.

Get schema details, status unspecified.

Coolify server deployment method references Git repository for code or uploads files directly.

The Backend integrates with GitHub as the source repository system.

The Coolify daemon integrates with the GitHub API to fetch repository source code during deployment builds.

The DataLens Project exposes a high-level API through lib/datalens.py. lib/datalens.py API interacts with DuckDB for data storage and querying.

DataLens Agent Mode communicates with IronClaw via HTTP webhooks and WebSocket for integration.

DataLens is deployed to and runs live at https://datalens.exerun.com after Ops Engineer approval.

The IronClaw agent feature is now accessible via UI buttons on project and analysis pages, deployed from commit e383323, with full functionality including chat, findings, and GDPR features. It is production-ready and live for user interaction. IronClaw Agent Feature relies on PostgreSQL database with 6 new tables created to function correctly. IronClaw Agent Feature uses FastAPI for backend API implementation including asynchronous generators. IronClaw Agent Feature was verified and validated by the comprehensive E2E test suite. IronClaw Agent Feature deployment depends on Coolify for container build and deployment orchestration. E2E test suite tests IronClaw Agent Feature for functionality and stability. IronClaw Agent Feature integrates with Datalens platform for agent-driven data analysis. LocalAgentClient is used by IronClaw Agent Feature to maintain session state across API calls. IronClaw Agent uses IronClawClient to connect and send messages to the remote IronClaw service. IronClaw Agent uses FindingsGenerator to generate findings from query results including handling PostgreSQL Decimal types. IronClaw Agent falls back to using LocalAgentClient when IronClaw environment variables are missing, resulting in local message processing and inability to complete queries successfully. IronClaw Agent requires IronClaw database to be configured and operational to persist sessions and support agent session creation. IronClaw Agent depends on QuestionRouter.route() to route queries and execute them correctly as part of the async processing pipeline. IronClaw Agent Findings Visualization uses the Live Backend to process and visualize data.

IronClaw backend endpoints expose API functionality required by the IronClaw agent feature. IronClaw Agent backend endpoints are integrated within the DataLens backend API services. IronClaw session creation endpoint is part of the IronClaw Gateway API that manages agent session lifecycle.

IronClawClient integrates with IronClaw Gateway API hosted on external system elin for remote operation. IronClaw Gateway integration backend on elin calls Anthropic Claude model for processing queries and generating results. theo Backend communicates via HTTP with IronClaw Gateway at elin:9876 to manage agent sessions and relay user requests. IronClaw Gateway integrates with Claude to provide natural language clarification and execute analysis steps in Danish. IronClaw Gateway uses Anthropic Claude as the large language model backend to process user queries with improved speed and privacy. User interacts with IronClaw Gateway as part of the platform to ask Danish budget questions and receive clarified and executed results. IronClaw Gateway integrates with Claude, connecting users to LLM for clarifications and execution phases. IronClaw Gateway depends on OpenClaw Skill API on the agent server to run ringfenced executor skills safely. theo Backend depends on IronClaw Gateway running on elin server to manage agent sessions and route requests. IronClaw service includes the IronClaw Gateway component responsible for agent orchestration and Claude connectivity. IronClaw Gateway uses Ollama with the Qwen3-coder-next model as fallback for local inference when Anthropic Claude not available.

Connects theo backend to elin IronClaw service via HTTP for autonomous agent analysis. Uses REST protocols. Integrated after setting IRONCLAW environment variables, with deployment a pending step. IronClawClient integrates with the IronClaw Gateway API for sending and receiving agent messages. IronClaw session creation endpoint is part of the IronClaw Gateway API that manages agent session lifecycle.