Documentation Index
Fetch the complete documentation index at: https://quintsecurity.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Events API
The events API handles ingestion of agent activity captured by the Quint daemon, and provides querying capabilities for event data.Endpoints
POST /v1/events/ingest
Daemon event ingestion (rate-limited). Used by the Quint daemon to push captured events.
GET /v1/events
List events with filtering by agent, session, action type, tool name, decision, risk range, and time range.
GET /v1/events/stats
24-hour aggregate statistics across events.
GET /v1/events/{id}
Retrieve a single event by ID.
Event Schema
Events are captured at the OS level by the Quint daemon. Each event represents a single system action performed by (or on behalf of) an AI agent:Action Types
Events are categorized by what the agent did at the OS level:| Action Type | Description |
|---|---|
PROCESS_EXEC | Agent spawned a child process (e.g., git, npm, curl) |
FILE_READ | Agent read a file from disk |
FILE_WRITE | Agent wrote or modified a file |
FILE_DELETE | Agent deleted a file |
NETWORK_CONNECT | Agent made an outbound network connection |
Filtering
TheGET /v1/events endpoint supports query parameters for filtering:
Data Model
Session Linkage
Every event carries asession_id (UUID v5) that links it to an agent session. Sessions are tracked separately via the Sessions API, providing hierarchical grouping of events with parent/child relationships.