AWS Cost and Usage Report Service

Name: AWS Cost and Usage Report Service API
Brand: AWS Cost and Usage Report Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingAWS Signature v4 (HMAC)4 EndpointsREST

For Agents

Manage AWS Cost and Usage Report definitions that deliver hourly billing line items to S3 in CSV or Parquet.

Install Jentic One Beta

Connect the AWS Cost and Usage Report Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Cost and Usage Report 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 AWS Cost and Usage Report Service API.

Create a Cost and Usage Report definition that writes CSV or Parquet to S3

Modify an existing report definition to change format, granularity, or schema columns

List all CUR report definitions in the account

GET STARTED

Start building with AWS Cost and Usage Report Service API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AWS Cost and Usage Report Service API for, with concrete tasks.

★ FinOps Data Lake Foundation

FinOps teams pipe AWS billing detail into a data lake so they can attribute spend to teams, products, and tags. AWS CUR's PutReportDefinition creates an hourly-granularity Parquet report that lands in S3 ready for Athena, Redshift, or QuickSight to query. Setup takes under an hour, after which the report is delivered automatically.

Call PutReportDefinition with Format=Parquet, Compression=Parquet, TimeUnit=HOURLY, an S3Bucket and S3Prefix, and AdditionalSchemaElements=[RESOURCES].

Chargeback and Showback by Tag

Engineering organizations need to charge back AWS spend to internal cost centers using tags. Enabling AdditionalSchemaElements=RESOURCES in a CUR report and filtering by cost-allocation tags downstream is the standard pattern. ModifyReportDefinition can update an existing definition rather than recreating it.

Call ModifyReportDefinition for an existing report to enable RESOURCES in AdditionalSchemaElements and SPLIT_COST_ALLOCATION_DATA in AdditionalArtifacts.

Lifecycle Management of Old Reports

When teams reorganize, old CUR definitions accumulate and continue writing to stale S3 buckets. DescribeReportDefinitions lists all current report definitions, and DeleteReportDefinition removes ones that are no longer needed.

Call DescribeReportDefinitions, identify reports whose S3Bucket starts with 'legacy-', then call DeleteReportDefinition for each.

Agent-Configured Billing Reports

An AI agent helping a FinOps lead can configure CUR reports on demand for new accounts and consolidate definitions across an organization. Through Jentic, each operation is one structured call with no SigV4 boilerplate.

For each new account in the organization, call PutReportDefinition with a standard Parquet hourly definition writing to a per-account prefix in the central billing bucket.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for aws cost and usage report service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.PutReportDefinition

Create a new Cost and Usage Report definition

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.DescribeReportDefinitions

List existing report definitions

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.ModifyReportDefinition

Modify an existing report definition

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.DeleteReportDefinition

Delete a report definition

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.PutReportDefinition

Create a new Cost and Usage Report definition

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.DescribeReportDefinitions

List existing report definitions

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.ModifyReportDefinition

Modify an existing report definition

POST

/#X-Amz-Target=AWSOrigamiServiceGatewayService.DeleteReportDefinition

Delete a report definition

Why Jentic?

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

Credential isolation

AWS SigV4 (HMAC) credentials for the AWS Cost and Usage Report Service are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access via Jentic's MAXsystem rather than holding the raw AWS access key ID and secret access key in their context.

Intent-based discovery

Agents search Jentic with intents like 'create a Cost and Usage Report that writes to S3' and Jentic returns the matching AWS Cost and Usage Report Service operation with its input schema, so the agent can call the correct endpoint without browsing the AWS service reference.

Time to first call

Direct integration: 2-4 days for SigV4 request signing, IAM policy setup, and error handling across AWS Cost and Usage Report Service operations. Through Jentic: under 1 hour - search by intent, load the schema, execute.

FAQs

Specific to using AWS Cost and Usage Report Service API through Jentic.

Why is there no official OpenAPI spec for AWS Cost and Usage Report Service?

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

AWS Signature v4 (HMAC) with IAM permissions on cur:* actions and the underlying S3 bucket. Jentic stores the AWS credentials in its vault and signs the requests on the agent's behalf.

Can I create a Parquet Cost and Usage Report with the API?

Yes. Call PutReportDefinition with Format=Parquet and Compression=Parquet, plus AdditionalArtifacts including ATHENA so the report is queryable via Athena out of the box.

What are the rate limits for the AWS Cost and Usage Report API?

The API itself is configuration-only with low TPS limits - PutReportDefinition, ModifyReportDefinition, and DeleteReportDefinition are infrequent operations and each account is limited to a small number of report definitions in total.

How do I create a CUR report through Jentic?

Search Jentic for 'create a Cost and Usage Report that writes to S3', load the PutReportDefinition schema, and execute it with the report name, S3 bucket, S3 prefix, format, and refresh settings. Reports begin delivering on the next billing run.

Is the AWS Cost and Usage Report API free?

The API and CUR delivery are free. You pay only for S3 storage of the delivered files and for any Athena, Redshift, or QuickSight queries you run against them.

AWS Cost and Usage Report Service

Connect the AWS Cost and Usage Report Service to your agent

Capabilities

Start building with AWS Cost and Usage Report Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs