AWS Amazon Lookout for Metrics
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentAI/MLMl Inferencehmac30 EndpointsREST
For Agents
Detect anomalies in metric time series, manage anomaly detectors, and route findings to alert channels for automated response.
Use for: I need to create an anomaly detector for daily revenue metrics, Find all anomaly groups detected in the last 24 hours, Set up an alert that publishes severe anomalies to an SNS topic, Retrieve the anomaly contributors for a specific anomaly group
Not supported: Does not handle log analytics, root cause analysis across distributed traces, or general-purpose forecasting — use for time-series metric anomaly detection only.
Jentic publishes the only available OpenAPI specification for Amazon Lookout for Metrics, keeping it validated and agent-ready. Amazon Lookout for Metrics uses machine learning to detect anomalies in business and operational metrics — sales drops, conversion changes, traffic spikes — without requiring data science expertise. Anomaly detectors ingest data from sources such as Amazon S3, Amazon Redshift, Amazon CloudWatch, and Amazon RDS, then surface deviations along with severity scores and grouped contributing dimensions. Alerts route findings to channels like Amazon SNS or AWS Lambda so downstream systems can respond automatically.
Install Jentic One Beta
Connect the Amazon Lookout for Metrics to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Lookout for Metrics, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Amazon Lookout for Metrics API.
Create anomaly detectors that monitor metric sets sourced from S3, Redshift, CloudWatch, or RDS
Activate, deactivate, or back-test anomaly detectors against historical metric data
Configure metric sets with measure and dimension fields for grouped anomaly analysis
Surface anomaly groups ranked by severity and inspect contributing dimensions
Provide human feedback on detected anomalies to refine detector accuracy
Route detected anomalies to SNS topics or Lambda functions through alert configurations
Tag detectors and metric sets for cost allocation and access control
Use Cases
Patterns agents use Amazon Lookout for Metrics API for, with concrete tasks.
★ Revenue and Conversion Anomaly Detection
E-commerce and SaaS teams use Lookout for Metrics to spot unexpected drops in revenue, sign-ups, or conversion rates without writing forecasting code. The service builds models per metric set, learns seasonality, and surfaces anomalies grouped by contributing dimensions such as product, region, or channel. Setup is point-and-click against an S3 or Redshift data source and produces results within hours of activation.
Create an anomaly detector for daily revenue with a one-day frequency, attach an S3-backed metric set with dimensions product_category and region, and activate the detector
Operational Telemetry Monitoring
DevOps and SRE teams attach Lookout for Metrics to CloudWatch metrics to find anomalies in latency, error rates, and throughput across services. Detectors group anomalies by service or instance dimension, helping engineers locate root causes faster than fixed-threshold alarms. The CloudWatch source connector ingests metrics directly so no ETL is required.
Configure a metric set sourced from CloudWatch latency metrics, attach it to an existing detector, and create an alert that triggers a Lambda function for anomalies above severity 70
Marketing Campaign Performance Tracking
Marketing analytics teams monitor click-through rates, ad spend, and acquisition costs across campaigns. Lookout for Metrics groups anomalies by campaign and channel dimensions, flagging when a single ad creative collapses while overall metrics stay healthy. Feedback loops let analysts mark false positives so the model adapts.
List anomaly groups for the marketing detector created in the last 7 days, then post user feedback marking the top result as anomaly type relevant
AI Agent Anomaly Triage Workflows
AI agents call Lookout for Metrics through Jentic to retrieve fresh anomaly groups, fetch contributing dimensions, and decide whether to open a ticket, page an on-call engineer, or annotate a dashboard. Jentic isolates the AWS Signature v4 credentials and exposes the detector and metric-set operations as discoverable tools so the agent can act without learning the SDK.
Search Jentic for 'detect a metric anomaly', load the ListAnomalyGroupSummaries operation for detector arn:aws:lookoutmetrics:..., and execute it for the last 6 hours
Key Endpoints
30 endpoints — jentic publishes the only available openapi specification for amazon lookout for metrics, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/CreateAnomalyDetector
Create a new anomaly detector
POST
/CreateMetricSet
Attach a metric set to a detector
POST
/ActivateAnomalyDetector
Activate a detector to begin training and ingestion
POST
/BackTestAnomalyDetector
Run a detector against historical data
POST
/ListAnomalyGroupSummaries
List detected anomaly groups for a detector
POST
/CreateAlert
Create an alert that routes anomalies to SNS or Lambda
POST
/PutFeedback
Submit human feedback on a detected anomaly
POST
/CreateAnomalyDetector
Create a new anomaly detector
POST
/CreateMetricSet
Attach a metric set to a detector
POST
/ActivateAnomalyDetector
Activate a detector to begin training and ingestion
POST
/BackTestAnomalyDetector
Run a detector against historical data
POST
/ListAnomalyGroupSummaries
List detected anomaly groups for a detector
POST
/CreateAlert
Create an alert that routes anomalies to SNS or Lambda
POST
/PutFeedback
Submit human feedback on a detected anomaly
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access key ID and secret access key are stored encrypted in the Jentic vault. Agents receive a scoped session — Jentic signs each request with Signature Version 4 so raw long-lived keys never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g. 'detect a metric anomaly') and Jentic returns matching Lookout for Metrics operations such as ListAnomalyGroupSummaries, with their input schemas, so the agent can call the right endpoint without browsing the AWS docs.
Time to first call
Direct integration: 1-2 days to wire up Signature v4, IAM policies, and SDK error handling. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon Lookout for Metrics API through Jentic.
Why is there no official OpenAPI spec for Amazon Lookout for Metrics?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Lookout for Metrics via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Amazon Lookout for Metrics API use?
The API uses AWS HMAC request signing (Signature Version 4) with an access key ID and secret access key scoped via IAM. Through Jentic, AWS credentials are stored encrypted in the vault and never enter the agent's prompt context — the agent receives a scoped session that signs each call.
Can I create and activate an anomaly detector with the Amazon Lookout for Metrics API?
Yes. POST /CreateAnomalyDetector defines a detector with frequency and KMS settings, POST /CreateMetricSet attaches the data source and metric definitions, and POST /ActivateAnomalyDetector starts model training and ingestion. Back-testing against historical data is available via POST /BackTestAnomalyDetector.
What are the rate limits for the Amazon Lookout for Metrics API?
AWS does not document hard request-per-second limits for Lookout for Metrics control-plane endpoints in the public spec. Quotas apply to detectors per account, metric sets per detector, and ingested data volume — see the AWS service quotas console for current values for your region.
How do I retrieve recent anomaly groups through Jentic?
Search Jentic for 'list anomaly groups' to discover POST /ListAnomalyGroupSummaries, load its schema with the Jentic Python SDK (pip install jentic), and execute it with the detector ARN and the desired time range. The MCP tool name is aws_list_anomaly_groups.
Is Amazon Lookout for Metrics free?
No. Lookout for Metrics charges per metric analyzed per month with a free tier for new accounts in the first month. Detector creation and metric-set configuration are free; you pay for the metrics actively monitored. See the AWS pricing page for the current rate per metric.
GET STARTED