Applications
Every AI application this control plane governs, across the four classes. A chatbot or RAG app connects by pointing its OpenAI SDK at the gateway with the key minted here; the gateway screens every prompt and response, journals every completion and enforces the policy on the row. Agents and multi-agent systems are listed from the Workflows register and the attached agents.
Chatbots…through the gateway
RAG apps…gateway and retrieval door
Agents…workflows and attached agents
Multi-agent systems…workflows with sub-runs or peers
Blocked…every door refuses
Controls fired…last 30 days, from the journals
Spend…last 30 days
Registerreading the register… · last seen, cost and firings are read from each row’s journalled completions over the last 30 days
| Application | Class | Autonomy | Owner | Identity | Policy | Last seen | Cost | Controls fired | State |
|---|
Agents and multi-agent systemslisted here, governed where they are built
A workflow built here is an agent (or a multi-agent system, when it runs sub-runs or peers) the moment it is deployed. A third-party agent is attached on the Configuration page, where its grants, gate risk and injection mode are set; the SDK and A2A doors keep serving it.WorkflowsAttached agents
The gateway is https://agentfactory.autogrc.cloud/api/gateway/v1; the retrieval door is https://agentfactory.autogrc.cloud/api/retrieval. A key is shown once, when the application is connected.