API Endpoints
Overview
Cerbera AI exposes API endpoints so you can integrate it into your own systems instead of clicking through the UI. This supports teams that prefer to automate and want traceability over their configuration, rather than making changes by hand in a portal.
What You Can Do
Read
Pull the AI tool inventory, alerts, and rule matches into your own systems.
Manage
Create and update rules, default policies, and exceptions programmatically.
Read
- Inventory of AI tools, models, agents, and MCP servers detected across the fleet.
- Alerts and rule matches, with the same privacy rules that apply in the app (metrics by default; bodies only where logging is enabled).
Manage
- Rules: create, update, and remove monitor, redact, and block rules.
- Default policies: set allow-by-default or deny-by-default behavior.
- Exceptions: grant or revoke exceptions for blocked tools and MCP servers.
Authentication
Requests authenticate with your Cerbera account, and every action respects the role-based permissions configured in the platform (for example cerbera_user versus employee). See Connect to Cerbera for how roles map to capabilities.
For the exact endpoint reference, request and response shapes, and authentication details, see the API reference in the Cerbera app or ask your Cerbera security engineer. The capabilities above describe what the API covers; the in-app reference is the source of truth for specific routes.
Infrastructure as Code
Driving configuration through the API is the foundation for managing Cerbera AI as code, with the traceability that brings.
Full infrastructure-as-code support (declarative, version-controlled configuration) is on the roadmap. Design-partner input shapes which resources are exposed first, so tell us what you need.