RagWiser

Created By
RobertoDurea year ago
RagWiser is a Retrieval Augmented Generation (RAG) system built with Spring Boot that enables users to upload PDF documents, process them, and ask questions about their content using natural language.
Overview

what is RagWiser?

RagWiser is a Retrieval Augmented Generation (RAG) system built with Spring Boot that allows users to upload PDF documents, process them, and ask questions about their content using natural language.

how to use RagWiser?

To use RagWiser, clone the repository, configure your OpenAI API key, start the PostgreSQL database, and run the application. You can upload PDF documents and ask questions through the provided API endpoints.

key features of RagWiser?

  • PDF Document Upload via REST API
  • Automatic Document Vectorization
  • Semantic Search using natural language
  • RAG-powered Response Generation
  • Integration with Spring AI and Docker support

use cases of RagWiser?

  1. Extracting information from legal documents
  2. Answering questions based on academic papers
  3. Assisting users in retrieving data from large PDF reports

FAQ from RagWiser?

  • Can RagWiser process any PDF document?

Yes, RagWiser can process various PDF documents as long as they are properly formatted.

  • Is there a limit to the size of the PDF that can be uploaded?

Yes, the maximum file size for uploads is set to 100MB.

  • Do I need an OpenAI API key to use RagWiser?

Yes, an OpenAI API key is required for generating responses.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RobertoDure
Star
0
Language
Java
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago