AWS Savings Plans

Name: AWS Savings Plans API
Brand: AWS Savings Plans
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceExpense Managementhmac9 EndpointsREST

For Agents

Browse, purchase, and inspect AWS Savings Plans commitments to lock in discounted rates on EC2, Fargate, and Lambda usage.

Connect the AWS Savings Plans to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Savings Plans, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 AWS Savings Plans API.

List available Savings Plan offerings filtered by term, payment option, and product family with DescribeSavingsPlansOfferings

Inspect per-instance discount rates that a given offering applies to with DescribeSavingsPlansOfferingRates

Purchase a Savings Plan commitment for a specific dollar-per-hour amount with CreateSavingsPlan

Queue a future-dated Savings Plan purchase and cancel it before it activates with DeleteQueuedSavingsPlan

GET STARTED

Start building with AWS Savings Plans API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Savings Plans, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Savings Plans, keeping it validated and agent-ready. Savings Plans are an AWS pricing model that offer discounted rates on EC2, Fargate, and Lambda usage in exchange for committing to a consistent dollar-per-hour spend over 1 or 3 years. This API lets FinOps teams browse offerings, purchase or queue plans, describe existing commitments, and inspect the per-instance discount rates that apply across their AWS account or organisation.

Use Cases

Patterns agents use AWS Savings Plans API for, with concrete tasks.

★ FinOps commitment planning

FinOps teams use DescribeSavingsPlansOfferings and DescribeSavingsPlansOfferingRates to compare 1-year vs 3-year and No Upfront vs All Upfront offerings against their forecasted EC2, Fargate, and Lambda spend. The API returns the exact effective hourly rate per instance family and region, which lets the team model break-even and pick the commitment level that matches their lowest sustained spend.

Call DescribeSavingsPlansOfferings filtered by planTypes=ComputeSP and durations=31536000, then for each offering call DescribeSavingsPlansOfferingRates filtered by usageTypes for EC2 m5.large in us-east-1.

Savings Plan purchase and queueing

Cloud-finance teams use CreateSavingsPlan to lock in a commitment at a specific dollar-per-hour rate, optionally with a future start date so the commitment activates aligned with a budget cycle. DeleteQueuedSavingsPlan allows cancellation before the queued plan activates — useful when forecasts shift between commitment and activation.

Call CreateSavingsPlan with savingsPlanOfferingId for the 1-year No Upfront Compute SP, commitment='5.00', and a clientToken for idempotency.

Existing commitment inventory and audit

Cost-allocation teams use DescribeSavingsPlans to inventory all active and expired commitments on the account, then DescribeSavingsPlanRates to see the per-usage-type rate each commitment applies. Combined with tags applied via TagResource, this drives chargeback reporting that maps Savings Plan benefit to the business unit funding the commitment.

Call DescribeSavingsPlans with no filter to enumerate all plans, then for any plan with end date within 90 days flag it for renewal review.

Agent-driven Savings Plan operations through Jentic

AI agents built into FinOps tooling use Jentic to call DescribeSavingsPlansOfferings, CreateSavingsPlan, and DescribeSavingsPlans without holding raw AWS credentials. Jentic stores keys in the MAXsystem vault, signs each request with SigV4, and returns the structured response — letting the agent gather offerings, model spend, and present a recommendation to a human approver before purchase.

Search Jentic for 'list AWS Savings Plan offerings', load DescribeSavingsPlansOfferings, and execute it filtered to the durations and product types matching the team's commitment policy.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for aws savings plans, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/DescribeSavingsPlansOfferings

List available Savings Plan offerings

POST

/DescribeSavingsPlansOfferingRates

List per-instance discount rates for an offering

POST

/CreateSavingsPlan

Purchase or queue a Savings Plan

POST

/DescribeSavingsPlans

List active and historical Savings Plans

POST

/DescribeSavingsPlanRates

List per-usage-type rates of an active plan

POST

/DeleteQueuedSavingsPlan

Cancel a queued Savings Plan before activation

POST

/TagResource

Apply tags to a Savings Plan ARN

POST

/DescribeSavingsPlansOfferings

List available Savings Plan offerings

POST

/DescribeSavingsPlansOfferingRates

List per-instance discount rates for an offering

POST

/CreateSavingsPlan

Purchase or queue a Savings Plan

POST

/DescribeSavingsPlans

List active and historical Savings Plans

POST

/DescribeSavingsPlanRates

List per-usage-type rates of an active plan

Why though Jentic?

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

Credential isolation

AWS credentials are stored encrypted in the Jentic vault (MAXsystem). Each Savings Plans call is signed with SigV4 server-side; the agent only receives scoped, short-lived authorisation, so raw access keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list AWS Savings Plan offerings') and Jentic returns matching Savings Plans operations with their input schemas, so the agent calls DescribeSavingsPlansOfferings or CreateSavingsPlan without browsing AWS docs.

Time to first call

Direct Savings Plans integration: 1 day for SigV4 signing against the global endpoint. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Cost Explorer

Analyse historical usage to right-size Savings Plan commitments before purchase

Use Cost Explorer to model usage patterns and recommended commitments; use Savings Plans to actually purchase and inspect the commitment.

Alternative

Amazon EC2

EC2's Reserved Instances API offers a different (less flexible) commitment model

Choose Reserved Instances when you need capacity guarantees for specific instance families; choose Savings Plans for flexible Compute discounts spanning EC2, Fargate, and Lambda.

Complementary

AWS Budgets

Set spend and coverage alerts that include Savings Plan utilisation

Use Budgets to monitor Savings Plan utilisation and coverage thresholds; use Savings Plans to inspect and adjust the underlying commitments.

FAQs

Specific to using AWS Savings Plans API through Jentic.

Why is there no official OpenAPI spec for AWS Savings Plans?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Savings Plans 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 AWS Savings Plans API use?

Savings Plans uses AWS Signature Version 4 HMAC signing with an access key ID and secret access key, optionally with a session token. The service is global, so requests are signed against the us-east-1 endpoint. Through Jentic, your AWS credentials live in the MAXsystem vault and Jentic signs each request server-side.

Can I buy a Reserved Instance with the AWS Savings Plans API?

No. This API is for Savings Plans only — Compute SP, EC2 Instance SP, and SageMaker SP. Reserved Instances are purchased through the EC2 API (PurchaseReservedInstancesOffering) and have a different commitment model tied to specific instance families.

What are the rate limits for the AWS Savings Plans API?

AWS does not publish a fixed RPS for Savings Plans in the spec; standard AWS API throttling applies and the service returns ThrottlingException on overage. The deeper limit is product-side: there are quotas on the number of Savings Plans an account can hold, available in the AWS service quotas console.

How do I purchase a Savings Plan with the AWS Savings Plans API through Jentic?

Search Jentic for 'purchase an AWS Savings Plan', load the CreateSavingsPlan operation, and call POST /CreateSavingsPlan with savingsPlanOfferingId, commitment in dollars-per-hour, and a unique clientToken for idempotency. Confirm the result with DescribeSavingsPlans. Install with pip install jentic.

Can I cancel a Savings Plan after it activates with the AWS Savings Plans API?

No — once a Savings Plan activates it cannot be cancelled or refunded; you are committed for the chosen 1-year or 3-year term. Only queued plans (those with a future start date that have not yet activated) can be cancelled, via DeleteQueuedSavingsPlan.