Viktor.comAn AI coworker that actually does the work
Promoted
Chancery
The identity provider for AI agents
13 followers
The identity provider for AI agents
13 followers
Orchestrators create agents at runtime, and tool servers hand them every key you own. Chancery gives each agent its own identity, access that can only narrow, safe runtime spawning, verified tool servers, instant revocation, and a provable audit trail.
Identity is becoming a much bigger problem for AI agents than for traditional apps. Curious what part of that problem you believe is still most underestimated.
@aryan787544 the underestimated would the callee side. Everyone is busy giving the agent an identity, but the tool it calls is usually unsigned code running with your keys in its environment. You can scope the agent perfectly and still hand everything to a poisoned dependency. That's why Chancery pin tool servers to exact digests and inject credentials server side so the agent never holds them.
@anee769 That's a really interesting way to frame it. It suggests the identity problem isn't just "who is the agent?" but "can every dependency in the execution chain be trusted?" I'll be curious whether, over time, people think about Chancery as an identity layer or as the system that makes AI execution auditable end-to-end. Those feel like very different categories.
@aryan787544 I'd push back on them being different categories at all. Identity without enforcement is just labels, and audit without identity is just logs you can't trust. They only work as one thing: every action carries who did it, what they were allowed to do, and what code actually ran, checked in the execution path itself. Chancery treats that as a single security property, not a stack of separate products.
@anee769 That's a helpful distinction, and I think I understand the thesis much better now.
Treating identity and audit as a single security property instead of separate product categories is a much stronger framing than I initially assumed.
I've got a couple of thoughts on how that framing could influence positioning as AI infrastructure matures. What's the best email to send them to?
A nice dashboard showing each agent's real-time permissions tree would be super helpful. Something where you can see what tools an agent currently has access to and visually tighten or revoke scopes with one click. Right now the audit trail sounds great after the fact, but I'd love a live view to catch drift before it becomes a problem.
@mer1045076 the dashboard ships today: run chancery serve and open /ui, and you get the live audit timeline with a permanent integrity badge, the agent roster, and each writ's delegation chain drawn as an actual tree. "see what an agent currently has access to" and "watch it live" both exist right now. It's a read-only dashboard for security.
A sandbox mode for testing agents before they get real credentials would be huge, especially for evaluating how narrowly they scope access in practice. Maybe a one click "dry run" that simulates the full identity and tool flow but uses throwaway keys, so you can audit behavior safely before going live.
@boran0uq6 half of this exists today. Wrap has a dry run that runs the full identity and policy flow, shows exactly what the agent would be allowed to call and what gets denied, and spawns nothing. Fastest way to see how narrowly an agent is scoped before it goes live.
The throwaway keys part is the gap. Right now you'd point it at a test server with fake secrets yourself. An sandbox identity with auto generated dummy creds is a genuinely good idea, adding it to the roadmap. Thanks for this.