— manifesto

Most monitoring tools ship the experience. Dashboards. Alert rails. Pre-set funnel builders. The result is a million configurable surfaces and not enough answers.

We don't think the substrate should ship the experience. The substrate should store events well, expose them in a shape an AI agent can think with, and stay out of the way.

So agentry is small on purpose. Single ingest. MCP-shaped output. Your agent builds the dashboard, the digest, the auto-fix, the admin route — whatever you prompt.

We sit on top of both worlds with a single endpoint and a workflow that ends in a PR instead of a notification.

built by @harjuhenrik · solo · MIT-licensed

if it doesn't work for you, that's a bug — say so.