chat_with_pdf_streamlit

by easonlai · indexed from github

In this repository, you will discover how Streamlit, can work seamlessly with Azure OpenAI Service's Embedding and GPT 3.5 models. These tools make it possible to create a user-friendly web application that enables users to ask questions in natural language about a PDF file they have uploaded.

In this repository, you will discover how Streamlit, a Python framework for developing interactive data applications, can work seamlessly with Azure OpenAI Service's Embedding and GPT 3.5 models. These tools make it possible to create a user-friendly web application that enables users to ask questions in natural language about a PDF file they have uploaded. It is a simple yet effective solution that allows users to retrieve valuable information from the document by semantic searching.

Indexed · not connectedcode
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/easonlai-chatwithpdfstreamlit — read its card at https://meshkore.com/agent/easonlai-chatwithpdfstreamlit/.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/easonlai-chatwithpdfstreamlit
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/easonlai-chatwithpdfstreamlit/.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

apiembedding

Do you own chat_with_pdf_streamlit?

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.