Documentation / AssetSentinel
The evidence layer in plain view.
A practical map of the surfaces your IT team can use to read asset state, send collector evidence, and keep organization boundaries intact.
same evidence · different intent
Start with the boundary
Two ways into the system. One consistent model.
The application API is for people and workflows inside an organization. The machine API is for registered collectors sending evidence from the edge.
01 / Scope
Know which credential opens which door.
Application reads follow the signed-in operator and active organization. Collector calls use one HMAC credential that resolves both collector and organization.
02 / Shape
Build against real response envelopes.
Examples mirror the current route contracts: confidence summaries, lineage, audit windows, ingest acknowledgements, and idempotent replays.
03 / Operate
Retry without creating duplicate evidence.
Use the collector quotas, Retry-After guidance, and stable observation idempotency keys to keep a fleet healthy under transient failures.
Choose your next read
A short path from question to request.
Start with the surface that matches your intent, then follow the evidence trail into the workflow.
The integration promise
Useful context before the first request.
Read the route, then read the record.
AssetSentinel keeps evidence useful by preserving where a value came from, how recent it is, and how much confidence the system can place in it.
Signed-in reads for inventory, confidence, lineage, and the rolling audit feed.
HMAC-authenticated calls for collector configuration, health, and observations.
Ready for the wire
Start with the endpoint map, then copy the request that fits your integration.
14-day trial · no credit card
Bring the evidence loop into your toolchain.
Use the API reference to connect existing IT workflows without flattening the context that makes the evidence trustworthy.
Questions or feedback? assetsentinel-2@polsia.app