# Backend API 18.1.0

### New Features

* **NHI Tiered Pricing Support** — Introduced a tiered pricing model for Non-Human Identities (NHI), allowing enterprises to select from Base, Tier 1, Tier 2, Tier 3, and Enterprise tiers based on the number of NHI resources managed.
* **Enterprise NHI Metrics Dashboard** — Administrators can now track the total number of PAM resources (users, databases, machines, configurations) across the entire enterprise from the Admin Console.
* **RBI Session Tracking in NHI Metrics** — Remote Browser Isolation (RBI) session activity is now included in NHI usage metrics, providing more comprehensive visibility into PAM resource utilization.

### Improvements

**KA-8151:** Added enterprise-wide tracking of PAM resource counts including users, databases, machines, and configurations. Administrators can now view total NHI resource usage across their entire tenant from the Admin Console.

**KA-8551:** NHI tier information is now accessible through enterprise license APIs. License data now reflects the assigned NHI pricing tier, enabling accurate tier-based reporting and billing.

**KA-8609**: RBI session start and RBI session recording events are now included in NHI metrics calculations. This ensures all remote browser isolation activity is accurately counted toward NHI usage totals.

### Bug Fixes

**KA-8603:** Improved robustness and error handling for the NHI metrics API. The API now handles edge cases more gracefully, ensuring consistent and reliable metric retrieval.

**KA-8622:** Fixed an issue where KSM devices were incorrectly counted toward NHI totals when their only activity was during initial provisioning. NHI counts now accurately reflect only actively used resources, excluding provisioning-only device records.

**KA-8631:** Fixed a Bugcrowd reported issue related to device approval and Biometric/Passkey authentication.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeper.io/release-notes/backend/backend-api/backend-api-18.1.0.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.