The /api/v1/discovery endpoints include the search endpoint. The /api/v1/discovery endpoints include the consolidate endpoint. The /api/v1/discovery endpoints include the preview endpoint. Intelligent consolidation is supported via the /api/v1/discovery endpoints (search, consolidate, preview). The Data Discovery feature provides /api/v1/discovery endpoints for search, consolidate, and preview functionalities. The Data Discovery feature provides /api/v1/discovery endpoints for search, consolidate, and preview functionalities.

The /api/v1/files/list endpoint originally made synchronous LLM calls causing timeout issues which were resolved by depending on progress tracking and async summary generation.

The /api/v1/files/list endpoint originally made synchronous LLM calls causing timeout issues which were resolved by depending on progress tracking and async summary generation.

The Frontend uses the /api/v1/projects/{project_id}/files endpoint to retrieve all project files along with their AI summaries.

The Frontend uses the /ask-stream endpoint to stream query responses and prevent HTTP timeout perception. The Backend API uses the /ask-stream endpoint to handle long-running queries with streaming responses to prevent client timeouts.

Provides REST API access to database tables for querying and analysis, supporting outbound HTTP protocol.

Validation endpoint tests data processing and analysis workflow correctness; currently in development.

Sends prompt to Ollama API for model inference, retrieves generated text.

Agent Skills Integration modifies _run_query to generate findings from query results and stream them as insights. The process_message function is expected to call the _run_query function to execute queries, but current data flow problem stops execution before _run_query is reached. In agent_skills.py, the process_message() function calls _run_query asynchronously to generate query results. _run_query method is modified as part of Agent Skills Integration to generate findings from query results _run_query generates findings streamed as 'insight' messages, each rendered as a separate IronClawMessage The process_message() method in agent_skills.py calls the _run_query() function asynchronously to execute queries.

The Backend exposes an analysis API The Backend implements the Analysis API requirement supporting Text-to-SQL and query history.

API endpoint facilitating SQL query execution against extracted data, integral for structured data analysis. The file backend/app/api/analysis.py contains the /analysis/query endpoint.

Provides suggested actions or insights based on analysis, aiding strategic decision-making, with full API deployment in progress.

OpenClaw Gateway integrates with the Anthropic API for language model processing Agent Gateway integrates with Anthropic API to provide cloud LLM model backend services.

IronClaw Service uses Anthropic Claude as the cloud LLM provider backend option. Claude is used to power the AI-assisted project goal generation feature. IronClaw Gateway integration backend on elin calls Anthropic Claude model for processing queries and generating results. IronClaw Gateway uses Anthropic Claude as the large language model backend to process user queries with improved speed and privacy. IronClaw service on elin uses Anthropic Claude model for large language processing and SQL generation. Claude in the architecture is the Anthropic Claude large language model used remotely.

The Anthropic API key is obtained from the Anthropic Console by user registration and key creation.

DataLens validates features by ensuring API endpoints respond to actual requests. The file backend/app/api/analysis.py is part of the API LAYER. The frontend service uses the Backend API endpoint, configured via the PUBLIC_API_URL environment variable, to communicate with the backend. The Backend API is implemented using FastAPI framework. Backend API depends on PostgreSQL 16 service for metadata storage. Backend API depends on Redis 7 service for job queue management. The frontend service uses the Backend API endpoint, configured via the PUBLIC_API_URL environment variable, to communicate with the backend. The Backend API is implemented using FastAPI framework. Backend API depends on PostgreSQL 16 service for metadata storage. Backend API depends on Redis 7 service for job queue management. DataLens agent requires API endpoints to validate features before claiming success.

The User Language Preference capability uses the API auth endpoint for language preference to update and retrieve user language settings. The Multilingual Support (Danish) epic uses the API auth endpoint for language preference to enable user language selection.

The Frontend includes an API client integrating all 11 backend endpoints.

The system has 11 API endpoints for various functions, all fully tested with all 60 tests passing, supporting authentication, file management, data extraction, and querying. The Complete E2E Flow Milestone utilizes several API Endpoints as part of the full user journey. KeyError:0 bug in API endpoint causes blocking issues for Phase 1 batch processing API endpoint is likely affected by uvicorn module cache causing KeyError:0 bug The Data Discovery feature provides API endpoints such as /discovery, /tables, and /validate. The Data Discovery feature provides API endpoints such as /discovery, /tables, and /validate. The Discovery backend service uses defined API endpoints for its operation. The Backend Service uses the defined API endpoints including the discovery endpoints. Database session management integrates with API endpoints to provide backend data operations for the agent. API endpoints are governed by authentication constraints to ensure secure access. The DataLens platform backend exposes 11 API endpoints. The Discovery backend service implements the Discovery API endpoints. The DataLens platform backend contains 11 API endpoints.

The Data Discovery system uses the API endpoints /discovery, /tables, and /validate. The backend service discovery.py implements the API endpoints for the Data Discovery system.

The Backend supports API Integration covering all 11 API endpoints including analysis query and history.

FindingsGenerator includes findings in the API response for all structured queries. FindingsGenerator results are included in the API response

Coolify Integration includes deployment for api.datalens.exerun.com domain.

API interface for user settings, including language preference updates.