agentstats
Evals for agent systems, with the statistics done right: CI gates, nightly checks, production monitoring from Langfuse/OpenTelemetry traces, and which models a smaller one could replace.
Evals for agent systems, with the statistics done right: a statistics core (intervals, paired tests, gates) with an eval workflow on top. agentstats gates pull requests, checks main every night, monitors production from your traces, and turns production failures into new eval cases. Point it at your agent's runs (Harbor jobs, ATIF trajectories, Inspect AI logs, Langfuse or OpenTelemetry traces, or a JSONL file) and it tells you how good the agent is, how reliable it is, whether version B is really better than A, and whether a cheaper model is shown to be no worse.
⚡ How to use agentstats
Indexed from PyPI. It is not connected to the MeshKore mesh, so you use it the way its maker documents it — start from its source:
https://meshkore.com/agent/siddharth-sukumar-agentstatsCapabilities
Do you own agentstats?
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.