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.
6 endpointsAWS Budgets lets you plan and track service usage, service costs, and reservation utilisation across an AWS account or organisation. The API supports four budget types: cost budgets, usage budgets, RI utilisation budgets, and RI coverage budgets, each with thresholds that trigger notifications to subscribers when actual or forecasted spend crosses the limit. Budget actions extend this with automatic responses such as applying a restrictive IAM policy, stopping EC2 or RDS instances, or attaching a deny policy to a Service Control Policy when a budget is exceeded.
23 endpointsJentic 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.
4 endpointsAWS Cost Explorer is the analytics API for AWS spend. It exposes the same data the Cost Explorer console renders, including cost and usage by service, account, tag, and dimension, programmatically with daily and monthly granularity. The API supports forecasting future costs and usage, detecting cost anomalies through anomaly monitors and subscriptions, retrieving Reserved Instance and Savings Plans coverage and utilisation, and getting purchase recommendations. Cost categories let you build custom rollups (by team, environment, or product) on top of raw cost data.
37 endpointsJentic publishes the only available OpenAPI specification for the AWS Price List Service, keeping it validated and agent-ready. The Price List Service exposes the public AWS pricing catalogue programmatically: services, their attributes, every SKU and price dimension, and downloadable historical price lists. The API has five operations covering service discovery, attribute enumeration, product price filtering, and signed URLs to price-list files. It is the canonical source for cost-estimator tools, FinOps automation, and cloud-pricing dashboards that need fresh AWS rates without screen-scraping the AWS pricing pages.
5 endpointsJentic 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.
9 endpointsJentic publishes the only available OpenAPI specification for the FinSpace Public API, keeping it validated and agent-ready. The FinSpace Public API manages financial datasets and data access inside an existing FinSpace environment. The API covers datasets, changesets, dataviews, users, and permission groups so that platform teams can load market data, version it across changesets, and grant scoped access to research desks. It is built for capital markets data engineering teams that need to operate the data plane of FinSpace through automation rather than the FinSpace UI.
31 endpointsJentic publishes the only available OpenAPI specification for FinSpace User Environment Management service, keeping it validated and agent-ready. FinSpace is AWS's data management and analytics service for the financial services industry, and this management API handles environment lifecycle. The API creates, retrieves, updates, and deletes FinSpace environments and manages tags applied to those environments. It is built for capital markets and financial-data platform teams that need to provision FinSpace environments programmatically as part of a wider data infrastructure pipeline.
8 endpointsStep 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 | shStep 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 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.