API endpoint for sending messages within an agent session, accessed via POST /api/v1/agent/sessions/{id}/message. The POST /api/v1/agent/sessions/{id}/message endpoint handles requests by executing the agent.py event_generator() function.

The frontend page at /frontend/src/routes/projects/[id]/analyze/+page.svelte uses the POST /api/v1/analysis/ask-stream endpoint for streaming analysis queries.

Apply schema to file endpoint, status unspecified.

The non-streaming and streaming versions of the /ask endpoint are related endpoints in analysis.py to handle questions. The /ask and /query endpoints are both used in analysis.py to handle user queries and SQL execution respectively. The /ask endpoint uses the Question router to classify and route user questions.

The non-streaming and streaming versions of the /ask endpoint are related endpoints in analysis.py to handle questions.

Schema detection endpoint, status unspecified.

API endpoint /export for exporting data, status unknown.

XLSX file uploaded successfully via POST /files/upload?project_id=4 endpoint POST /files/upload?project_id=4 endpoint stores uploaded files in PostgreSQL database

Generate project goal endpoint in backend/api/projects.py, status unspecified.

List tables API in backend/api/discovery.py, status unspecified.

User registration and login endpoints exist in auth.py to handle user onboarding and authentication.

Schema mapping suggestions endpoint, status unspecified.

Run GDPR PII detection scan on a project's data at POST /projects/{project_id}/gdpr-scan. The message sending endpoint for sessions and the GDPR scanning endpoint are related agent functionalities within the agent backend. Running a GDPR scan on a project may use findings data as part of its process.

Endpoint in backend/app/api/agent.py. Initiates insight generation for a project, returning a job ID for progress tracking.

Generate a report from selected findings via POST /projects/{project_id}/report. Generating a report from selected findings uses the list of findings available for the project.

The /ask and /query endpoints are both used in analysis.py to handle user queries and SQL execution respectively. Query history retrieval and SQL query execution are related analytical functions exposed by analysis.py.

Query from budget data, status unspecified.

Query budget files API, status unspecified.

Deprecated SQL query endpoint, status unspecified.

User registration and login endpoints exist in auth.py to handle user onboarding and authentication.

The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent.py module, together handling agent session creation and messaging. The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent_openclaw.py module, together handling agent session creation and messaging. The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent_pydantic.py module, together handling agent session creation and messaging. The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent_vanna.py module, together handling agent session creation and messaging. Health check endpoint monitors the overall availability of the agent service which includes session creation functionality.

Endpoint to end an agent session through POST /sessions/{session_id}/end.

The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent.py module, together handling agent session creation and messaging. The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent_openclaw.py module, together handling agent session creation and messaging. The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent_pydantic.py module, together handling agent session creation and messaging. The endpoint POST /sessions and POST /sessions/{session_id}/message are part of the same agent_vanna.py module, together handling agent session creation and messaging. The message sending endpoint for sessions and the retrieval of project findings are related agent functionalities within the same backend context. The message sending endpoint for sessions and the GDPR scanning endpoint are related agent functionalities within the agent backend. Within the agent backend, the message sending for sessions and model switching for sessions operate on the same session resource. Sending a message in a session and retrieving skill execution logs both relate to the same session in agent backend.

Uploading a file and extracting data from the uploaded file are sequential operations in files.py for data ingestion. The upload-batch endpoint extends the functionality of single file upload by handling multiple files asynchronously.

The upload-batch endpoint extends the functionality of single file upload by handling multiple files asynchronously.

API /validate in backend/api/discovery.py for validating convalidations, status unspecified.

Uploading a file and extracting data from the uploaded file are sequential operations in files.py for data ingestion.

Generate analysis recommendations, status unspecified.

Backend API uses PostgreSQL 16 database service as its metadata store. The DataLens Platform backend depends on PostgreSQL 16 as the database technology. PostgreSQL 16 database server is integrated within the Coolify deployment environment for DataLens Development.

A React/Vue component enabling chat interface, embedding the system's question-answering features. Vanna 2.0 provides a pre-built web component for embedding the chat interface in various frontend frameworks.