Inventory

The Hermes agent continuously discovers hardware and software on each endpoint and reports it to the server. Inventory is collected in modules, and each module can be streamed individually to the server as it completes — so partial results land without waiting for a full pass.

What's collected#

Hermes organizes collection into discrete inventory modules. Each module targets one area of the endpoint; on Windows the data is read from WMI, the registry, DISM, and performance counters.

Detail fields#

The key fields reported per area:

Derived agent flags#

From the reported inventory, the server derives a set of flags it uses to classify each agent:

• IsServer — the endpoint is running a server OS.
• IsDomainController — derived from the presence of the AD-Domain-Services feature.
• IsVirtualMachine — the endpoint is a virtual machine.
• IsDomainJoined — the endpoint is joined to a domain.
• DomainName — the domain the endpoint belongs to.

How it's stored#

The server persists reported inventory in JSON columns:

Querying inventory#

Inventory for an agent is read from GET api/agents/{agentId}/inventory, with sub-routes for each area:

A refresh can be triggered from the server, optionally scoped to specific modules, with a force_refresh flag. Fetch the hardware inventory for an agent over the API:

# Fetch hardware inventory for one agent
$headers = @{ Authorization = "Bearer $token" }

Invoke-RestMethod `
  -Uri "https://athena.example.com:8443/api/agents/$agentId/inventory/hardware" `
  -Headers $headers `
  -SkipCertificateCheck

Refresh intervals#

Two cadences govern how often the server hears from an agent: