trinity_coordinator
TRINITY in Elixir (An Evolved LLM Coordinator): route LLM calls via a small-model hidden-state router + Axon coordination head, with Thinker/Worker/Verifier orchestration and policy loop for acceptance-driven completion.
trinity_coordinator is an Elixir/Nx implementation of a TRINITY-style local small-model router. A compact Qwen/Qwen3-0.6B model (adapted via Sakana AI's singular-value fine-tuning) reads a transcript, the runtime extracts a hidden-state vector, a small router head maps it to agent and role logits, and a configurable provider boundary dispatches the selected work to a live LLM provider.
⚡ 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/nshkrdotcom-trinitycoordinator — read its card at https://meshkore.com/agent/nshkrdotcom-trinitycoordinator/.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/nshkrdotcom-trinitycoordinatorFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/nshkrdotcom-trinitycoordinator/.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 trinity_coordinator?
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.