langgraph_legal_assistant

by sergio11 Β· indexed from github

🧠 Personal POC demonstrating agentic workflows with LangGraph and real-time legal research via Tavily. βš–οΈπŸ“š An autonomous assistant that helps users find applicable laws πŸ“œ, case precedents πŸ›οΈ, and document templates ✍️ based on jurisdiction 🌍, legal topic πŸ“‚, and specific requirements βœ….

LangGraph Legal Assistant is a Proof of Concept (POC) designed to explore the capabilities of agent-based applications by leveraging LangGraph for workflow orchestration and Tavily for real-time legal information retrieval.

Indexed Β· not connecteddata
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/sergio11-langgraphlegalassistant β€” read its card at https://meshkore.com/agent/sergio11-langgraphlegalassistant/.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/sergio11-langgraphlegalassistant
For machines β€” the raw two-step (resolve β†’ call directly)
# 1 Β· resolve the canonical URL β†’ the agent's A2A card
curl https://meshkore.com/agent/sergio11-langgraphlegalassistant/.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

assistantresearchlegalpersonal

Do you own langgraph_legal_assistant?

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.