Skip to main content

First steps

Are you new to nOps or to using APIs? This is the place to start!

What is nOps?​

nOps is an AWS AI-Powered FinOps platform. Our mission is to make it easy for engineers to take action on cloud optimization.

nOps Business Contexts helps you allocate every penny of your AWS spend, Compute Copilot simplifies price and waste optimization for ASGs and EKS down to the container level, and Essentials automates time-consuming cloud optimization tasks.

How can I leverage this API? The nOps API allows you to access cloud cost and usage insights directly from your own systems, enabling you to monitor and analyze your AWS environment outside of the nOps dashboard. Here’s how you can leverage it:

  1. Real-Time Cost and Usage Monitoring: Use the API to access detailed, up-to-date information on AWS costs and usage across different business contexts like departments, projects, or environments. This allows you to view spending trends and identify cost drivers directly within your own systems.

  2. Custom Reporting and Analytics: With the API, you can pull data to generate custom reports or integrate it into your existing analytics tools, providing tailored insights into cloud spending without depending on nOps’ pre-built dashboards.

  3. Alerts and Anomaly Detection: Use cost and usage data from the API to create custom alerts and monitor for spending anomalies. By integrating with your internal monitoring systems, you can stay informed on cloud costs within the context of your own workflows.

  4. DevOps Integration: The API provides visibility into resources like clusters and workloads, helping you understand cloud costs as part of your CI/CD pipeline.

By using the nOps API, you gain visibility into your cloud spend and resources, allowing you to leverage these insights within your own tools and processes to make data-driven decisions.

What is an API?​

An API, or Application Programming Interface, is a set of rules and protocols that allows different software applications to communicate with each other. In simple terms, an API serves as a bridge between systems, enabling one application to access data or functionality from another without needing to understand its internal workings. With an API, developers can integrate and use external features—like retrieving data, processing actions, or triggering workflows—within their own applications or workflows.

How do I use it?​

You can get started with nOps API here!