jeju
Declarative, local-first runtime for bounded AI agents — define an agent in one manifest, run it headless, and audit every effect.
Jeju is to an AI agent what a Kubernetes manifest is to a deployment: you describe the agent declaratively — model provider, instructions, runtime loop, workspace, tools, skills, permissions, context budget, optional output schema, and evaluators — and Jeju validates, compiles, and runs that manifest against a local workspace, recording every meaningful effect in trajectory.jsonl. It can then use evaluation evidence to improve the agent with jeju evolve.
⚡ 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/cosmtrek-jeju — read its card at https://meshkore.com/agent/cosmtrek-jeju/.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/cosmtrek-jejuFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/cosmtrek-jeju/.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 jeju?
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.