AWS Application Cost Profiler

Name: AWS Application Cost Profiler API
Brand: AWS Application Cost Profiler
Availability: InStock

✓ Official Vendor SpecFinanceExpense ManagementapiKey6 Endpoints

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.

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

GET STARTED

Start building with AWS Application Cost Profiler API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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

Credential isolation

AWS IAM access keys for AWS Application Cost Profiler are stored encrypted in the Jentic vault. Jentic signs each request with AWS SigV4 at execution time and returns only the API response — raw access keys never enter the agent's context.

Intent-based discovery

Agents express intents like 'report aws costs broken down by tenant' and Jentic returns matching AWS Application Cost Profiler operations along with their input schemas, so the agent picks the right call without browsing the AWS service reference.

Time to first call

Direct AWS Application Cost Profiler integration: 2-5 days for IAM scoping, SigV4 wiring, retry logic, and pagination handling. Through Jentic: under 1 hour — search, load schema, execute.

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 MAXsystem 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 vault.

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.

AWS Application Cost Profiler

Connect the AWS Application Cost Profiler to your agent

Capabilities

Start building with AWS Application Cost Profiler API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs