Workforce management for autonomous agents.
Set each agent's identity, authority, budget, tools, and skills. Inspect its recorded work in Oxagen. These docs cover the CLI, REST API, and MCP surfaces whose capability calls pass through the invoke() boundary.
Give agents the business context their work requires.
Request workspace entities, relationships, and memories through scoped retrieval capabilities. Choose context relevant to the task within the agent's permitted scope and context budget.
- Typed knowledge graph. Search entities and relationships stored in Neo4j.
- Scoped by the mandate. Governed graph reads check the caller's authority and workspace scope.
- Recorded usage. Inspect the usage and timing recorded for the retrieval and model calls your agent makes.
Free, not full. Oxagen retrieves only the slice of your typed knowledge graph the task needs and the agent's mandate lets it read, so the window stays open and the model stays sharp.
What the control plane holds.
Wrap
Enroll the machine that runs your agent. Harness hooks send recorded steps to your workspace. Hook-based evidence is client-attested, and observe mode records activity without enforcing it.
Wrap a machineGovern
Give each agent an identity and a mandate. For actions routed through Oxagen, the control plane checks its authority and records the decision. Credentials for mediated connections stay in Oxagen.
Roles and RBACRecord
Inspect recorded steps, decisions, and cost on a run. Query security events in Postgres and IAM decisions in ClickHouse. The audit guide explains what each store records and where evidence can be missing.
Audit loggingSpend
Review recorded usage by agent, operator, workspace, and run. Set organization and workspace ceilings for governed consumption. Check whether each cost was measured, reported, or estimated.
Billing and budgetsChoose an interface.
Each capability declares which surfaces expose it. Read its contract and the interface guide before connecting your client.
Getting started
Sign up, create your organization and workspace, wrap one machine.
CLI
Query the graph, cap spend, read a run, and manage credentials from the terminal. Stella runs the agent. Oxagen governs the run.
REST API
/v1 endpoints, API-key authentication, the capability registry, and the chat streaming transport.
MCP server
Reach /mcp over streamable HTTP. Your Oxagen API key carries the organization and workspace scope.
In-app agent
A governed turn loop over the fleet record and the knowledge graph: what your agents did, what context they had, what it cost, and what is waiting on a person.
Plugins
Browse the plugin catalog through API or MCP. Inspect installation, credential, entitlement, and role requirements.
See which agent spent what, and on whose behalf.
Install the CLI and wrap one machine, or read the getting-started guide to create an organization and workspace. Run a task in the wrapped harness, then inspect the record that arrived.