Backend API

DataLens Platform provides a Backend API to support frontend and other clients. The frontend /ask-stream switch uses the backend /ask-stream endpoint to enable streaming query responses and prevent client timeout errors. The frontend /ask-stream switch uses the backend /ask-stream endpoint to enable streaming query responses and prevent client timeout errors. The Backend API interacts with the RQ worker to manage extraction job queues and status for SVGV files. The backend container hosts the Backend API which is functional and ready to handle requests for DataLens. The Data Discovery Feature uses Backend API endpoints including /discovery, /tables, and /validate for functionality. RQ Worker extraction processing uses Backend API endpoints for extraction tasks coordination. The Data Discovery System uses Backend API endpoints to support entity extraction, ranking, and join discovery services. The Backend API integrates with the Discovery backend service via the defined routes. Backend API queries DuckDB tables produced from the SVGV extraction for budget data Backend API queries DuckDB tables produced from the SVGV extraction for budget data Backend API queries DuckDB tables produced from the SVGV extraction for budget data The Backend API uses the /ask-stream endpoint to handle long-running queries with streaming responses to prevent client timeouts. The Backend API integrates with the Ollama GPU service to run LLM models qwen3-coder-next and nomic-embed-text for query classification and embeddings generation. Backend API exposes the Extraction API endpoints to trigger extraction of individual SVGV files. Backend API uses OpenClaw Gateway WebSocket client to communicate with OpenClaw Gateway for agent chat operations. Backend API exposes the Extraction API endpoints to trigger extraction of individual SVGV files. Backend API uses OpenClaw Gateway WebSocket client to communicate with OpenClaw Gateway for agent chat operations.