---
title: "Explain Asset"
method: POST
path: "/api/v1/sdk/alerts/investigations/explain"
tags: ["public-api", "public-investigations"]
---

# Explain Asset

`POST /api/v1/sdk/alerts/investigations/explain`

## Request

- Base URL: `http://localhost:8000`
- URL: `http://localhost:8000/api/v1/sdk/alerts/investigations/explain`
- Auth: none declared

TECH-982: synchronous asset investigation returning an EvidenceCapsule.

Runs the same correlator pipeline as alert-driven investigations but
does not persist an AlertInvestigation row. Use when you have an
asset and a question but no firing alert.

## Headers

- `Authorization` string

## Request body

- ExplainAssetRequest: TECH-982: request body for `POST /alerts/investigations/explain`. Run a synchronous investigation against an asset without persisting a row. Used by the `armor-investigate` skill.
  - `asset_id` string, required: Asset public UUID
  - `question` string, nullable: Natural-language question to anchor the capsule
  - `event_type` string: One of: anomaly, freshness, schema_change, validity

## Response `200`

Successful Response

- StandardResponse: Standard API response wrapper.
  - `success` boolean, required
  - `data` unknown
  - `message` string, nullable
  - `error` string, nullable
  - `meta` object, nullable

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api.md) · [All operations](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api/llms.txt) · [OpenAPI document](https://skmtc.dev/anomalyarmor/apis/anomalyarmor-api/revisions/51c755fb5d0b?raw)