Streamlit-API-Flask-Mistral
Flask API with a Streamlit ChatBot, this project provides a dynamic interface for database interaction and AI-driven user engagement, featuring secure, Docker-deployed components and advanced GPT-3.5 integration.
This project integrates two main components: a Flask-based API and a Streamlit ChatBot. The Flask API is designed to facilitate interactions between the application and a MongoDB NoSQL database. It is containerized using Docker and deployed on a Synology DS224+ as a Docker container, with a tunnel established to Ngrok for external access. The ChatBot, developed using Streamlit, interacts with the user and the API, offering advanced features like RAG and Q&A models, feedback systems, and integration with various AI technologies.
⚡ 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/grkdev-streamlit-api-flask-mistral — read its card at https://meshkore.com/agent/grkdev-streamlit-api-flask-mistral/.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.
https://meshkore.com/agent/grkdev-streamlit-api-flask-mistralFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/grkdev-streamlit-api-flask-mistral/.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
Do you own Streamlit-API-Flask-Mistral?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.