For Agents
Query Amazon Forecast predictors for point and quantile forecasts, including baseline and what-if scenarios for a specific item.
Get started with Amazon Forecast Query Service in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"query an Amazon Forecast for an item"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Amazon Forecast Query Service API.
Query a deployed Forecast predictor for a single item across the prediction horizon
Retrieve quantile values such as p10, p50, and p90 alongside point forecasts
Filter forecasts by item identifier and additional dataset dimensions
Query what-if forecasts that compare a baseline against scenario adjustments
GET STARTED
Use for: I need to retrieve next-week demand forecast for SKU 12345, Get the p90 forecast for store-region pair 42-eu, Query the latest forecast for item ABC and date range, Compare a baseline forecast against a what-if scenario
Not supported: Does not train predictors, manage datasets, or evaluate models — use for runtime queries against Amazon Forecast outputs only.
Jentic publishes the only available OpenAPI specification for Amazon Forecast Query Service, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Amazon Forecast Query Service, keeping it validated and agent-ready. The Forecast Query Service is the runtime side of Amazon Forecast and exposes only the operations needed to query trained predictors. The API returns point and quantile forecasts for a specific item, and serves what-if forecasts that compare baseline predictions against scenario adjustments. It is built for application teams that want to embed pre-computed Forecast predictions into customer-facing demand, capacity, or pricing flows.
Receive forecasts as time-stamped data points ready for charting or downstream logic
Patterns agents use Amazon Forecast Query Service API for, with concrete tasks.
★ Demand Forecast Retrieval
E-commerce and retail teams use the Forecast Query Service to retrieve item-level demand forecasts produced by Amazon Forecast and surface them inside fulfilment, replenishment, and pricing applications. The API returns point forecasts and configurable quantiles for a single item per call, so downstream systems can read confidence bands and not just a midpoint estimate. Forecast values arrive as date-keyed series ready to be plotted or fed into stock decisions.
Query forecast arn:aws:forecast:...:forecast/demand-prod with filter item_id=SKU-12345 and return p10, p50, and p90 values.
What-If Scenario Comparison
Planning teams use the QueryWhatIfForecast operation to compare baseline forecasts against scenarios that alter price, promotion, or holiday inputs. The API returns both baseline and scenario series for a single item, so analysts can view the lift or drag attributable to each scenario without computing the difference manually. This shortens scenario analysis for category managers and supply planners.
Call QueryWhatIfForecast for what-if forecast id wif-xyz with filter item_id=SKU-12345 and return baseline plus scenario series.
Operational Embedding in Customer-Facing Apps
Product and operations teams embed Forecast predictions into staffing, capacity, and pricing surfaces by calling QueryForecast at runtime. Because the API exposes only two operations, integration is small and stable, and the rest of the Forecast lifecycle (training, evaluation) stays inside the separate Forecast control plane. This separation keeps customer-facing services lightweight.
Call QueryForecast for forecast staffing-monthly with filter location_id=eu-west-store-42 and return the next 14 daily values.
Agent-Driven Forecast Lookup via Jentic
AI agents use the Forecast Query Service through Jentic to fetch demand or capacity predictions in response to user questions and workflow events. Jentic exposes the QueryForecast and QueryWhatIfForecast operations as discoverable tools so an agent can search by intent and return forecast values to a chat interface or downstream automation in seconds.
Search Jentic for query forecast, load the QueryForecast schema, and execute it with forecast ARN demand-q3 and filter item_id=SKU-9001.
2 endpoints — jentic publishes the only available openapi specification for amazon forecast query service, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/#X-Amz-Target=AmazonForecastRuntime.QueryForecast
Query a deployed forecast for a single item
/#X-Amz-Target=AmazonForecastRuntime.QueryWhatIfForecast
Query a what-if forecast for baseline and scenario series
/#X-Amz-Target=AmazonForecastRuntime.QueryForecast
Query a deployed forecast for a single item
/#X-Amz-Target=AmazonForecastRuntime.QueryWhatIfForecast
Query a what-if forecast for baseline and scenario series
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for Forecast Query are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing access — raw secret access keys never enter the agent context.
Intent-based discovery
Agents search by intent (for example get demand forecast for a sku) and Jentic returns matching Forecast Query operations with their input schemas, so the agent can call the right endpoint without browsing AWS docs.
Time to first call
Direct integration: half a day for SigV4 signing and runtime testing. Through Jentic: under 15 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Amazon SageMaker
General ML platform for training and serving forecasting models
Choose SageMaker when you need full control over a custom forecasting model rather than the managed Forecast workflow.
AWS Lambda
Wraps Forecast queries inside event-driven workflows
Choose Lambda when forecast queries should run in response to events such as cron triggers or upstream data updates.
Amazon EventBridge
Schedules Forecast queries on a recurring basis
Choose EventBridge when forecasts should be retrieved on a schedule and routed into downstream targets.
Specific to using Amazon Forecast Query Service API through Jentic.
Why is there no official OpenAPI spec for Amazon Forecast Query Service?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Forecast Query Service 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 Forecast Query Service use?
Forecast Query uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the agent never sees the raw secret access key.
Can I retrieve quantile forecasts with this API?
Yes. QueryForecast returns predictions including the quantiles configured on the underlying predictor (commonly p10, p50, and p90). Each quantile arrives as a separate timestamped series in the response.
What are the rate limits for the Amazon Forecast Query Service?
AWS applies per-account, per-region throttling on the Forecast runtime. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.
How do I run a what-if scenario through Jentic?
Search Jentic for what if forecast, load the QueryWhatIfForecast schema, and execute it with the what-if forecast ARN and an item filter. Jentic returns baseline and scenario series side by side.
Does this API train Forecast predictors?
No. Training, evaluation, and deployment live in the separate Amazon Forecast control plane. This service only serves queries against forecasts that have already been generated.