Google KMS Inventory API

Name: KMS Inventory API
Brand: KMS Inventory API
Availability: InStock

✓ Official Vendor SpecSecuritySecrets Managementoauth23 EndpointsREST

Install Jentic One Beta

Connect the KMS Inventory API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KMS Inventory API, 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 KMS Inventory API.

List all Cloud KMS crypto keys inside a Google Cloud project

Summarize the resources protected by a specific crypto key

Search an entire organization for resources covered by customer-managed encryption

GET STARTED

Start building with KMS Inventory API

Explore with Jentic

View OpenAPI Document

For Agents

Inventory Cloud KMS keys across a project and search for resources protected by customer-managed encryption keys at organization scope. Read-only audit data for security teams.

Use for: List all Cloud KMS crypto keys in a project, Find every resource protected by a specific KMS key, Search the organization for resources using customer-managed encryption, I need to audit CMEK coverage before rotating a key

Not supported: Does not create, rotate, or destroy keys, encrypt data, or manage IAM policies — use only to inventory crypto keys and search for resources they protect.

Use Cases

Patterns agents use KMS Inventory API for, with concrete tasks.

★ Pre-rotation impact assessment

Before rotating or destroying a Cloud KMS key, security teams need to know exactly which resources depend on it. Calling /v1/{+name}/protectedResourcesSummary on the key returns counts grouped by resource type and project, so the agent can confirm the rotation will not orphan production data.

Call GET /v1/projects/{p}/locations/{l}/keyRings/{kr}/cryptoKeys/{k}/protectedResourcesSummary and return the resourceCount grouped by cloudProduct.

Organization-wide CMEK compliance audit

Compliance teams must demonstrate that regulated workloads use customer-managed encryption keys. The /v1/{+scope}/protectedResources:search endpoint lists every protected resource across an organization, optionally filtered by crypto key, so the agent can produce evidence that BigQuery datasets, Cloud Storage buckets, and Compute disks all sit behind CMEK.

Call protectedResources:search with scope=organizations/{orgId}&cryptoKey={keyName} and return the list of resource names.

Cleanup of unused crypto keys

Each Cloud KMS key version costs money even when nothing references it. By listing keys with /v1/{+parent}/cryptoKeys then checking protectedResourcesSummary for each, an agent can identify keys with zero protected resources that are safe to schedule for destruction.

List crypto keys in a project then for each key with resourceCount=0, output the key resource name for review.

Agent-driven CMEK reporting via Jentic

A security agent triggered by a quarterly compliance review can use Jentic to call the three KMS Inventory operations without writing GCP-specific resource path code. Jentic returns the search and summary schemas in a uniform shape so the agent can feed results straight into a compliance report.

Run google_kmsinventory_search_protected_resources for the organization and write the returned resource list to the compliance bucket.

Key Endpoints

3 endpoints — the kms inventory api gives google cloud security teams an organization-wide view of cloud kms crypto keys and the resources protected by them.

METHOD

PATH

DESCRIPTION

GET

/v1/{+parent}/cryptoKeys

List crypto keys inside a project

GET

/v1/{+name}/protectedResourcesSummary

Summarize resources protected by a specific crypto key

GET

/v1/{+scope}/protectedResources:search

Search organization-wide for protected resources

GET

/v1/{+parent}/cryptoKeys

List crypto keys inside a project

GET

/v1/{+name}/protectedResourcesSummary

Summarize resources protected by a specific crypto key

GET

/v1/{+scope}/protectedResources:search

Search organization-wide for protected resources

Why Jentic?

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

Credential isolation

GCP service account keys with org-level KMS Inventory permissions are stored encrypted in the Jentic vault. Agents receive a short-lived OAuth 2.0 token scoped to https://www.googleapis.com/auth/cloud-platform — the JSON key never reaches the agent.

Intent-based discovery

Agents search Jentic with intents like 'list resources protected by a kms key' or 'find unused crypto keys' and Jentic returns the matching v1 operation with the right scope and parent path templates already documented.

Time to first call

Direct integration: 4-8 hours to grant the right org-level IAM roles, build the resource path strings, and handle pagination. Through Jentic: under 20 minutes — search, load, execute.

FAQs

Specific to using KMS Inventory API through Jentic.

What authentication does the KMS Inventory API use?

OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope, using a service account that has cloudkms.protectedResourcesSummary.get and cloudkms.protectedResources.search IAM permissions at the organization level. Through Jentic the service account JSON sits in the encrypted vault and only a short-lived access token reaches the agent.

How is KMS Inventory different from the Cloud KMS API?

The Cloud KMS API manages keys (create, rotate, encrypt, decrypt, destroy). The KMS Inventory API is read-only and answers a different question: which resources are currently protected by a given key, across an entire project or organization.

What are the rate limits for the KMS Inventory API?

Google enforces a default of 60 read requests per minute per project for inventory operations. The protectedResources:search endpoint also caps page size at 500 resources, so large organizations need to paginate.

How do I audit CMEK coverage through Jentic?

Run jentic search 'list resources protected by a kms key' to surface protectedResources:search, jentic load to retrieve its parameters, then jentic execute with scope=organizations/{orgId} and an optional cryptoKey filter. Jentic returns the paginated resource list ready for a compliance report.

Can I find unused crypto keys with this API?

Yes. List crypto keys in a project with GET /v1/{+parent}/cryptoKeys, then call protectedResourcesSummary on each — keys whose resourceCount is zero are unreferenced and candidates for scheduled destruction.

Is the KMS Inventory API free?

The inventory API itself has no per-call charge; you only pay for the underlying Cloud KMS keys and key versions. Quota is governed by the Cloud KMS API service in the project.