agenttune
AgentTune: build agentic workflows, then train, evaluate, distill, and self-heal them through one trajectory schema. A TRL-backed alignment + fine-tuning library (full RL coverage — DPO, PPO, GRPO) with an agentic integration spine on top: agent-design / memory-design / harness-design pillars, a Project lifecycle, and a FastAPI service.
Most agent tooling covers running an agent design, a memory system, or a harness. AgentTune also trains, evaluates, distills, and self-heals that design, and every stage reads and writes one normalized trajectory schema (EventLog), so you don't need a separate tool per stage. It sits on top of whatever agent framework built the design.
⚡ 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/abhivansh-gupta-vidushee-vats-ram-mohan-rao-kadiyala-vina-agenttune — read its card at https://meshkore.com/agent/abhivansh-gupta-vidushee-vats-ram-mohan-rao-kadiyala-vina-agenttune/.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.
https://meshkore.com/agent/abhivansh-gupta-vidushee-vats-ram-mohan-rao-kadiyala-vina-agenttuneFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/abhivansh-gupta-vidushee-vats-ram-mohan-rao-kadiyala-vina-agenttune/.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
Do you own agenttune?
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.