llm-message-hash-py
Stable canonical sha256 hash of LLM request/message structures. Recursive key-sorted JSON canonicalization with per-provider presets that drop noise fields. For cache keys and idempotency. Zero runtime deps.
Two semantically identical Anthropic requests can produce different sha256(json.dumps(req)) results because Python dict iteration order is not part of the value, and fields like cache_control change the bytes without changing what gets sent to the model. This library walks the value tree, sorts dict keys recursively, drops a configurable set of fields, and sha256s the canonical bytes.
⚡ 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/mukunda-rao-katta-llm-message-hash-py — read its card at https://meshkore.com/agent/mukunda-rao-katta-llm-message-hash-py/.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.
https://meshkore.com/agent/mukunda-rao-katta-llm-message-hash-pyFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/mukunda-rao-katta-llm-message-hash-py/.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
Do you own llm-message-hash-py?
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.