Anomaly Detection · Schema

Anomaly

A detected anomaly in a time series or multivariate data stream, including the affected metric, timestamp, severity score, and contextual metadata.

Anomaly DetectionArtificial IntelligenceData ScienceFraud DetectionMachine-LearningMonitoringObservabilityOutlier DetectionPattern RecognitionSecurityTime Series

Properties

Name Type Description
id string Unique identifier for the detected anomaly.
metric_name string Name of the metric or signal in which the anomaly was detected.
timestamp string ISO 8601 timestamp when the anomaly was detected.
value number The observed metric value at the time of the anomaly.
expected_value number The expected metric value based on historical patterns.
anomaly_score number Normalized anomaly severity score between 0 (normal) and 1 (highly anomalous).
severity string Categorical severity level of the anomaly.
direction string Whether the anomaly is a spike above expected, a dip below, or bidirectional.
algorithm string The detection algorithm that identified this anomaly.
status string Current status of the anomaly alert.
series_id string Identifier of the time series or data stream this anomaly belongs to.
dimensions object Key-value pairs providing additional context dimensions for the anomaly (e.g., region, service, host).
related_anomalies array List of related anomaly IDs grouped in the same root cause cluster.
View JSON Schema on GitHub

JSON Schema

anomaly-detection-anomaly-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/anomaly-detection/refs/heads/main/json-schema/anomaly-detection-anomaly-schema.json",
  "title": "Anomaly",
  "description": "A detected anomaly in a time series or multivariate data stream, including the affected metric, timestamp, severity score, and contextual metadata.",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique identifier for the detected anomaly.",
      "example": "anom-500123"
    },
    "metric_name": {
      "type": "string",
      "description": "Name of the metric or signal in which the anomaly was detected.",
      "example": "cpu_utilization"
    },
    "timestamp": {
      "type": "string",
      "format": "date-time",
      "description": "ISO 8601 timestamp when the anomaly was detected.",
      "example": "2026-04-19T14:30:00Z"
    },
    "value": {
      "type": "number",
      "description": "The observed metric value at the time of the anomaly.",
      "example": 98.7
    },
    "expected_value": {
      "type": "number",
      "description": "The expected metric value based on historical patterns.",
      "example": 62.3
    },
    "anomaly_score": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "description": "Normalized anomaly severity score between 0 (normal) and 1 (highly anomalous).",
      "example": 0.94
    },
    "severity": {
      "type": "string",
      "enum": ["low", "medium", "high", "critical"],
      "description": "Categorical severity level of the anomaly.",
      "example": "high"
    },
    "direction": {
      "type": "string",
      "enum": ["above", "below", "both"],
      "description": "Whether the anomaly is a spike above expected, a dip below, or bidirectional.",
      "example": "above"
    },
    "algorithm": {
      "type": "string",
      "description": "The detection algorithm that identified this anomaly.",
      "example": "SARIMA"
    },
    "status": {
      "type": "string",
      "enum": ["active", "resolved", "acknowledged", "suppressed"],
      "description": "Current status of the anomaly alert.",
      "example": "active"
    },
    "series_id": {
      "type": "string",
      "description": "Identifier of the time series or data stream this anomaly belongs to.",
      "example": "ts-prod-cluster-01"
    },
    "dimensions": {
      "type": "object",
      "description": "Key-value pairs providing additional context dimensions for the anomaly (e.g., region, service, host).",
      "additionalProperties": {
        "type": "string"
      },
      "example": {"region": "us-east-1", "host": "web-server-42"}
    },
    "related_anomalies": {
      "type": "array",
      "description": "List of related anomaly IDs grouped in the same root cause cluster.",
      "items": {
        "type": "string"
      }
    }
  },
  "required": ["id", "metric_name", "timestamp", "value", "anomaly_score", "severity", "status"]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/anomaly-detection-anomaly"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.