AWS Cost and Usage Report Service
Browse all Amazonaws APIs62
AI ReadinessAI-Aware (B-)62/100
Agent-ready OpenAPI document · curated by JenticFinanceAccountingAWS Signature v4 (HMAC)4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage AWS Cost and Usage Report definitions that deliver hourly billing line items to S3 in CSV or Parquet.
Use for: I need to create a Cost and Usage Report that lands in my S3 bucket, I want to switch my CUR from CSV to Parquet, List all Cost and Usage Report definitions in this account, Delete an unused CUR report definition
Not supported: Does not handle interactive cost analysis, budget alerts, or forecasting - use only to manage Cost and Usage Report definitions that deliver line items to S3.
Jentic publishes the only available OpenAPI specification for AWS Cost and Usage Report Service, keeping it validated and agent-ready. AWS Cost and Usage Report (CUR) Service programmatically manages report definitions that deliver detailed AWS billing line items - one row per resource per hour - to Amazon S3 in CSV or Parquet. The API has four operations: create, modify, list, and delete report definitions. Reports underpin enterprise billing, chargeback, and FinOps analytics in tools like Athena, QuickSight, and third-party platforms.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-cur" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Faws-cur" | 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 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
Delete a report definition that is no longer needed
Configure resource IDs, split cost allocation, and refresh-on-close behavior
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AWS Cost and Usage Report Service
- AI-Aware (B-)62/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility39
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
39
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
55%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AWS Cost and Usage Report Service by hand means implementing AWS Signature v4 request signing, resolving the regional cur host, and setting the X-Amz-Target header to route each JSON action to the right operation. Through Jentic you install once, import AWS Cost and Usage Report Service from the API Directory, store the AWS credentials once, and your agent calls it.
Permission scoping
This API routes every call through a single endpoint with the action named in the request, covering operations like PutReportDefinition, DescribeReportDefinitions, and DeleteReportDefinition. Limit the agent to the operations it needs, such as DescribeReportDefinitions, so DeleteReportDefinition is not included unless you add it.
Credential isolation
Your AWS credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a Cost and Usage Report that writes to S3' or 'list existing report definitions', and Jentic returns the matching AWS Cost and Usage Report Service operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the AWS Cost and Usage Report API?
Yes. Because Jentic One is self-hosted, you decide which of this API's operations your agent may call, even though every request routes through a single endpoint with the action named inside it. For example, you can allow only DescribeReportDefinitions so the agent can list report definitions, while withholding PutReportDefinition, ModifyReportDefinition, and DeleteReportDefinition. The AWS credentials stay under your control and are injected only for the operations you have permitted.
GET STARTED