healthmate-ai-voice-agent-backend

by Manojkumar2806 · indexed from github

HealthMate is an AI-powered voice agent that helps users get clear, reliable answers to health-related questions in real time. It combines FastAPI, AssemblyAI, and React with Retrieval-Augmented Generation (RAG) and VectorDB Cloud (Native) for fast and relevant responses.

HealthMate is more than a voice assistant—it’s your trusted health confidant that thinks and reasons like a clinician to deliver safe, reliable medical knowledge. Designed to empower everyone, especially underserved communities, it provides instant, ethical health guidance through voice interaction, bridging gaps in health literacy and accessibility.

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

apiragvoice

Do you own healthmate-ai-voice-agent-backend?

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.