Case study · Agent control plane
Giving agents their own identity at work.
As I built Offworld, I needed to know which agent was doing what, what it could access, and how to stop it if I had to. Owyhee grew out of that need.
The problem
Agents borrow your identity.
Most agents today run on someone's computer and use that person's logins. To every system they touch, the agent looks like you. That makes it hard for a business to see what its agents are doing, tell an agent's actions apart from a person's, or shut one down in a single place.
The approach
Pull identity, credentials, and enforcement into one layer.
Owyhee sits between agents and the tools they use. Agents never hold passwords or keys themselves. They ask Owyhee for access, and Owyhee checks who the agent is, who stands behind it, and what it's allowed to do, every time.
AI gateway
Routes one or more agents across multiple model providers.
MCP server manager
Centralizes tools and their credentials instead of handing them to each agent.
Credential storage
Encrypted, and never exposed to the agents that use it.
Agent roster and operators
Every agent tied to the accountable human operators behind it, with full role-based access control.
The result
Visibility a borrowed login can't give you.
With every tool and credential running through one place, it becomes easy to watch activity, see usage, spot unusual behavior, and change or revoke an agent's permissions. Owyhee runs today as that layer for Kiger. It started as something the newsroom needed and grew into a product of its own.
Part of the Kipple Labs stack
Offworld is the publication. Kiger runs its agents and picks their models. Owyhee holds their credentials and enforces what each one may do. AXIS gives them an identity any company can verify.