chat-with-multiple-PDFs-LLAMA2

by jorge-armando-navarro-flores · indexed from github

This script is a chat application that allows users to ask questions about multiple PDF documents implemented with meta's LLAMA2

The MultiPDF Chat App is a Python application that allows you to chat with multiple PDF documents. You can ask questions about the PDFs using natural language, and the application will provide relevant responses based on the content of the documents. This app utilizes a language model to generate accurate answers to your queries. Please note that the app will only respond to questions related to the loaded PDFs.

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/jorge-armando-navarro-flores-chat-with-multiple-pdfs-llama2 — read its card at https://meshkore.com/agent/jorge-armando-navarro-flores-chat-with-multiple-pdfs-llama2/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/jorge-armando-navarro-flores-chat-with-multiple-pdfs-llama2
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/jorge-armando-navarro-flores-chat-with-multiple-pdfs-llama2/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

llm

Do you own chat-with-multiple-PDFs-LLAMA2?

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.