AWS Application Cost Profiler
Browse all Amazonaws APIs61
AI ReadinessAI-Aware (B-)61/100
Official vendor OpenAPI document · agent-readyFinanceExpense ManagementapiKey6 EndpointsREST
For Agents
Use the AWS Application Cost Profiler API to report shared-resource AWS costs by tenant or application on AWS, with 6 operations covering the full control-plane lifecycle.
Use for: Create a daily tenant cost report, I want to import the latest usage data file, List all configured cost reports, Update the S3 destination for an existing cost report
Not supported: Does not handle billing payment, budget alerts, or tag-based cost allocation - use for tenant-level shared-resource cost reporting only.
AWS Application Cost Profiler reports the cost of shared AWS resources broken down by tenant or application using customer-supplied usage data. It accepts uploaded usage records, joins them with billing data, and emits cost reports to S3 on a configurable schedule.
Install Jentic One Beta
Connect the AWS Application Cost Profiler to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Application Cost Profiler, 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-applicationcostprofiler" | 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-applicationcostprofiler" | 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 Application Cost Profiler API.
Define cost reports that emit per-tenant or per-application cost breakdowns to an S3 bucket
Import usage data files from S3 that map shared resource consumption to tenant identifiers
Update report definitions to change schedule, format, or destination
List existing report definitions in the account
Delete a report definition when the workload no longer needs it
Use Cases
Patterns agents use AWS Application Cost Profiler API for, with concrete tasks.
★ Per-tenant cost reporting for a multi-tenant SaaS
Operate shared compute, storage, or database infrastructure across multiple tenants and produce per-tenant cost reports by uploading usage records that attribute resource consumption to tenant identifiers. Application Cost Profiler joins those records with AWS billing data and emits CSV reports to a chosen S3 bucket on a daily or monthly schedule. Initial setup is typically under a day.
Create a daily report definition named 'tenant-cost-daily' that writes to s3://billing-reports/tenant-daily/ and import the latest usage data file from s3://usage-uploads/2026-06/.
Internal chargeback for shared platform teams
Charge internal product teams for their share of a centrally-run platform by uploading usage records keyed by team identifier. The resulting cost reports become the source of truth for monthly chargeback. This replaces ad-hoc cost spreadsheets with a managed, auditable pipeline. Reports refresh on the schedule defined in the report definition.
Create a monthly report definition called 'team-chargeback' configured for CSV format and import the previous month's team-keyed usage records.
Automated usage-data ingestion pipeline
Land usage data files in an S3 bucket from upstream collectors, then call ImportApplicationUsage on each new file to register it for the next report run. Combined with EventBridge or Lambda triggers, this becomes a hands-off ingestion pipeline that produces fresh cost reports without manual operator intervention.
Call ImportApplicationUsage with the S3 location s3://usage-uploads/2026-06-01/usage.csv to register the latest day's records.
AI agent producing tenant cost reports through Jentic
A finance operations agent can run the entire Application Cost Profiler workflow without direct AWS console access by calling its operations through Jentic. It registers report definitions, imports usage files, and lists report status using scoped credentials, so the agent never sees the underlying AWS access keys. This compresses month-end cost-reporting work to a single agent intent.
Search Jentic for 'report aws costs broken down by tenant', load the schemas for PutReportDefinition and ImportApplicationUsage, and execute them in sequence for the current month's data.
Key Endpoints
6 endpoints — aws application cost profiler reports the cost of shared aws resources broken down by tenant or application using customer-supplied usage data.
METHOD
PATH
DESCRIPTION
POST
/reportDefinition
Create a new cost report definition
GET
/reportDefinition
List configured report definitions
GET
/reportDefinition/{reportId}
Get a single report definition
PUT
/reportDefinition/{reportId}
Update a report definition
DELETE
/reportDefinition/{reportId}
Delete a report definition
POST
/importApplicationUsage
Import a usage data file from S3
POST
/reportDefinition
Create a new cost report definition
GET
/reportDefinition
List configured report definitions
GET
/reportDefinition/{reportId}
Get a single report definition
PUT
/reportDefinition/{reportId}
Update a report definition
DELETE
/reportDefinition/{reportId}
Delete a report definition
POST
/importApplicationUsage
Import a usage data file from S3
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 Application Cost Profiler
- AI-Aware (B-)61/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility38
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
0%
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.
38
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
52%
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 AWS Application Cost Profiler by hand means creating IAM credentials, choosing the right regional host from applicationcostprofiler.{region}.amazonaws.com, signing every request with AWS SigV4, and adding your own retry handling. Through Jentic you install once, import AWS Application Cost Profiler from the API Directory, store the AWS access key once, and your agent calls it.
Permission scoping
AWS Application Cost Profiler puts the report id in the URL path (/reportDefinition/{reportId}), so a rule can pin your agent to one report definition: it can read and update that report and nothing else. You choose the operations it may call, so destructive ones like deleting a report definition are not included unless you add them.
Credential isolation
Your AWS access key for AWS Application Cost Profiler is stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'report AWS costs broken down by tenant' or 'import a usage data file from S3', and Jentic returns the matching AWS Application Cost Profiler 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 Application Cost Profiler API through Jentic.
What authentication does the AWS Application Cost Profiler API use?
The AWS Application Cost Profiler API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's your Jentic One instance stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.
Can I create a daily tenant cost report with the AWS Application Cost Profiler API?
Yes - the AWS Application Cost Profiler API exposes 6 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.
What are the rate limits for the AWS Application Cost Profiler API?
AWS applies per-account, per-region request rate limits to the AWS Application Cost Profiler control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the AWS Application Cost Profiler entry, and design retries with exponential backoff to absorb throttling responses.
How do I report aws costs broken down by tenant through Jentic?
Run pip install jentic, then call client.search('report aws costs broken down by tenant') to discover the AWS Application Cost Profiler operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic One instance.
Is the AWS Application Cost Profiler API free to call?
AWS does not charge for control-plane API calls themselves on most AWS Application Cost Profiler operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the AWS Application Cost Profiler pricing page. Refer to the AWS pricing page for the service to estimate cost.
Which operations should an agent call first when working with the AWS Application Cost Profiler API?
For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.
Can I limit what my agent is allowed to do with the AWS Application Cost Profiler API?
Yes. Because you self-host Jentic One, your own rules decide which AWS Application Cost Profiler operations the agent may call and which AWS credentials it may use. Since the report id sits in the URL path (/reportDefinition/{reportId}), a rule can pin the agent to a single report definition so it can read and update that one report and nothing else. You choose the allowed operations, so destructive calls like deleting a report definition stay out of reach unless you add them.
GET STARTED