What counts as an AI agent?

Include systems that use a model to interpret context and take or recommend actions in a business workflow. Simple deterministic automations can be tracked too when they share the same access concerns.

How often should the inventory be reviewed?

Review after meaningful access or workflow changes, and set a regular cadence based on impact. High-impact agents deserve more frequent review.

Do I need integrations to use Roxea?

No. Roxea uses a declarative review: you record agents, tools, permissions and safeguards without connecting production accounts.

Is Roxea a compliance tool?

Roxea helps structure and document an internal review. It does not guarantee compliance or replace legal, security or compliance advice.

Know what is running

AI Agent Inventory

A useful inventory goes beyond an agent name. It records why the agent exists, who is responsible for it and what it can do inside real business systems.

Start an agent audit Read the guide

Why you need an AI agent inventory

Agents are often created by different teams with different tools. Some run inside automation platforms, some are embedded in SaaS products and some are scripts maintained by one person.

Without a shared inventory, security and operations cannot tell which workflows touch customer data, source code or payments. Reviews begin from memory instead of evidence.

What should be tracked

Track enough information to answer ownership, access and impact questions. Avoid turning the inventory into a catalogue of model settings nobody uses.

Name, purpose, lifecycle status and department.
Business owner and technical contact.
Connected tools and data categories.
Read, write, send, delete or execute access.
Autonomy level and human approval points.
Logging, monitoring and stop controls.
Last review date and open actions.

Example inventory fields

For a “Support Refund Agent”, the record might show Support as the department, the support lead as owner, Zendesk read/write access, Stripe refund access up to a stated limit and human approval before the refund is submitted.

That is enough context to review the workflow. A vague row saying “GPT support bot — active” is not.

How Roxea structures your inventory

Roxea gives each agent a record linked to tools, permissions, assessment history and action items. The inventory remains readable for business users while preserving the details a reviewer needs.

Because the workflow is declarative, teams can start before an integration project. The owner confirms the setup, the reviewer records findings and both can work from the same scope.

FAQ

Questions people ask before a review

Continue the review

Related guides and product details

Agent inventory

Keep agents, tools, permissions and owners in one place.

Agent permissions checklist

Review read, write, send, code and payment access tool by tool.

AI agent audit checklist

Use a practical checklist to run your first structured review.

Start with the agents your team can name today.

Create a clear record for each agent, then fill the gaps as owners confirm their workflows.

Start an agent audit