odylith
Odylith stops coding agents from confidently doing the wrong thing
Without Odylith, every agent session starts from scratch. Reading the repo, inferring the architecture, guessing intent and constraints, discovering what went wrong last time. With Odylith, the agent starts from governed truth: the right slice, the real component boundaries, the live blockers, the invariants, the historical learnings from past failures, and the full execution history. It gets to the actual work faster, makes fewer wrong moves, and leaves durable evidence behind for the next session. The more you use Odylith, the better it gets.
⚡ 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/odylith-odylith — read its card at https://meshkore.com/agent/odylith-odylith/.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/odylith-odylithFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/odylith-odylith/.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 odylith?
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.