AWS Amazon Forecast Query Service

Name: Amazon Forecast Query Service API
Brand: Amazon Forecast Query Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLMl InferenceapiKey2 Endpoints

Install Jentic One Beta

Connect the Amazon Forecast Query Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Forecast Query Service, 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.

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 | sh

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 instance

Jentic 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 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

GET STARTED

Start building with Amazon Forecast Query Service API

Explore with Jentic

View OpenAPI Document

For Agents

Query Amazon Forecast predictors for point and quantile forecasts, including baseline and what-if scenarios for a specific item.

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.

Use Cases

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.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for amazon forecast query service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AmazonForecastRuntime.QueryForecast

Query a deployed forecast for a single item

POST

/#X-Amz-Target=AmazonForecastRuntime.QueryWhatIfForecast

Query a what-if forecast for baseline and scenario series

POST

/#X-Amz-Target=AmazonForecastRuntime.QueryForecast

Query a deployed forecast for a single item

POST

/#X-Amz-Target=AmazonForecastRuntime.QueryWhatIfForecast

Query a what-if forecast for baseline and scenario series

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AWS access keys for Forecast Query are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get the demand forecast for a SKU' or 'query a what-if forecast', and Jentic returns the matching Forecast Query operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Amazon Forecast Query Service?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, and the Forecast Query Service dispatches every action through a single signed endpoint keyed by the operation name. You add only the operations the agent needs, such as QueryForecast for point and quantile predictions or QueryWhatIfForecast for baseline-versus-scenario series, and any operation you leave out stays outside the allowed set. Your AWS access keys are held by your own instance and injected at signing time, so the agent never handles the raw credentials.

AWS Amazon Forecast Query Service

Connect the Amazon Forecast Query Service to your agent

Capabilities

Start building with Amazon Forecast Query Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs