RAG-Based-PDF-Insight-Generator

by PuneetVerma04 · indexed from github

Fully offline RAG system for PDF question answering and summarisation — Ollama, LangGraph, Qdrant. No cloud calls.

Reading a long PDF (a report, a paper, a spec) to answer one question, or to get a quick summary, is slow. This is a small local tool for that: upload a PDF, get either a whole-document summary or an answer to a specific question grounded in the document's content — without sending the file to an external API.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/puneetverma04-rag-based-pdf-insight-generator — read its card at https://meshkore.com/agent/puneetverma04-rag-based-pdf-insight-generator/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/puneetverma04-rag-based-pdf-insight-generator
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/puneetverma04-rag-based-pdf-insight-generator/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

ragllm

Do you own RAG-Based-PDF-Insight-Generator?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.