Install Jentic One Beta

Connect the Cloud Deployment Manager V2 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Deployment Manager V2 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fdeploymentmanager" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fdeploymentmanager" | 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 Cloud Deployment Manager V2 API.

Insert, update, and delete deployments composed of Google Cloud resources

Preview deployment changes before applying them via cancelPreview and stop operations

Inspect deployment manifests to verify template expansion and resource configuration

GET STARTED

Start building with Cloud Deployment Manager V2 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cloud Deployment Manager V2 API for, with concrete tasks.

★ Infrastructure-as-Code Rollouts

Define Google Cloud infrastructure as Deployment Manager templates and apply them via the deployments.insert endpoint. Engineers commit YAML or Jinja templates to source control, run a preview to surface diffs, then apply the deployment to provision Compute Engine instances, networks, storage buckets, and IAM bindings in one transaction. Typical multi-service stacks roll out in 2-10 minutes.

Insert a new deployment named web-stack using a YAML template that creates one Compute Engine VM and one Cloud Storage bucket, then poll the operation until done.

Deployment Drift Auditing

Use the manifests and resources endpoints to compare what a deployment claims to manage versus what currently exists in the project. Auditors call deployments.get plus manifests.get to retrieve the expanded template, then list resources to verify each is still in the intended state. Useful for compliance reviews and pre-merge checks on platform repos.

Get the active manifest for deployment prod-network and list all resources it owns, then return any resource whose state is not COMPLETED.

Safe Update Previews

Run deployments.update with the preview flag set to model changes without applying them. Platform teams use this to surface destructive changes (resource recreation, IAM removal) before approving a merge. If the preview shows undesired changes, call cancelPreview to discard; otherwise re-run update without preview to apply.

Update deployment data-pipeline with preview=true using a new template, then list the manifest changes and abort if any resource will be deleted.

Agent-Driven Environment Bootstrap

Through Jentic, an AI agent can search for the deployment insert operation, load its schema, and bootstrap an entire test environment from a natural-language brief. The agent supplies a project ID and template body, and Jentic executes the call against Deployment Manager with scoped OAuth credentials managed by your Jentic One instance.

Use Jentic to search 'create a Google Cloud deployment from a template', load the schema, and execute deployments.insert for project test-env-42 with a Jinja template body.

Key Endpoints

18 endpoints — google cloud deployment manager lets you declaratively configure, deploy, and update google cloud resources using yaml or jinja/python templates.

METHOD

PATH

DESCRIPTION

GET

/deploymentmanager/v2/projects/{project}/global/deployments

List all deployments in a project

POST

/deploymentmanager/v2/projects/{project}/global/deployments

Create a new deployment

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Get a specific deployment

DELETE

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Delete a deployment and its resources

POST

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/cancelPreview

Cancel a deployment preview

POST

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/stop

Stop an in-progress deployment update

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/resources

List resources owned by a deployment

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/manifests/{manifest}

Get an expanded deployment manifest

GET

/deploymentmanager/v2/projects/{project}/global/deployments

List all deployments in a project

POST

/deploymentmanager/v2/projects/{project}/global/deployments

Create a new deployment

GET

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Get a specific deployment

DELETE

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}

Delete a deployment and its resources

POST

/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/cancelPreview

Cancel a deployment preview

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Cloud Deployment Manager V2 API by hand means setting up Google OAuth, minting short-lived deployment-manager scoped tokens rather than shipping service-account JSON, and building project and deployment paths against deploymentmanager.googleapis.com. Through Jentic you install once, import the Cloud Deployment Manager V2 API from the API Directory, store the Google credential once, and your agent calls it.

Permission scoping

The API puts the project and deployment id in the URL path (/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}), so a rule can pin your agent to one project or deployment. You choose the operations it may call, so it can list deployments and read resources while deployment deletion is not included unless you add it.

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'deploy a Google Cloud template', and Jentic returns the matching Deployment Manager deployments operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cloud Deployment Manager V2 API through Jentic.

What authentication does the Cloud Deployment Manager API use?

The API uses Google OAuth 2.0 with the deployment-manager and cloud-platform scopes. Through Jentic, OAuth tokens are stored encrypted in your Jentic One instance and scoped per agent run, so raw service-account keys never enter the agent's context.

Can I preview a deployment before applying it with Cloud Deployment Manager?

Yes. Call deployments.update or deployments.insert with the preview parameter set to true. Deployment Manager expands the template and produces a manifest plus a list of intended resource changes without modifying live resources, and cancelPreview discards the preview.

What are the rate limits for the Cloud Deployment Manager API?

Deployment Manager applies Google Cloud per-project quotas: writes (insert, update, delete) are rate-limited per minute and total deployments per project are capped. Check your project quota under IAM and Admin to view current limits.

How do I list resources in a deployment through Jentic?

Search 'list resources in a Google Cloud deployment', load the schema for the resources.list endpoint at /deploymentmanager/v2/projects/{project}/global/deployments/{deployment}/resources, then execute it with your project ID and deployment name. Jentic returns the parsed resource array.

Does Cloud Deployment Manager support rollback?

There is no first-class rollback endpoint. To revert, call deployments.update with the previous template body, or stop an in-progress deployment via the deployments.stop endpoint to halt further changes.

Is the Cloud Deployment Manager API free?

Deployment Manager itself has no charge. You pay for the underlying Google Cloud resources the deployments create (Compute Engine, Cloud Storage, Cloud SQL, etc.) at standard GCP rates.

Can I limit what my agent is allowed to do with the Cloud Deployment Manager API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use. Since the project and deployment id sit in the request path (/deploymentmanager/v2/projects/{project}/global/deployments/{deployment}), you can pin the agent to a single project or deployment and grant only the calls you trust, such as listing deployments and reading their manifests and resources. Destructive operations like deployments.delete or deployments.stop stay off unless you explicitly allow them.

Google Cloud Deployment Manager V2 API

Name: Cloud Deployment Manager V2 API
Brand: Cloud Deployment Manager V2 API
Availability: InStock

Browse all Google APIs

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeoauth218 EndpointsREST

For Agents

Provision and manage Google Cloud infrastructure as code via templated deployments, with preview, manifest, and resource introspection.

Use for: I need to deploy a new set of Google Cloud resources from a template, Preview the changes a deployment will make before applying them, List all deployments in a Google Cloud project, Retrieve the manifest for a deployment to inspect expanded resources

Not supported: Does not handle container orchestration, CI build pipelines, or runtime application monitoring - use for declarative Google Cloud resource provisioning only.

Google Cloud Deployment Manager lets you declaratively configure, deploy, and update Google Cloud resources using YAML or Jinja/Python templates. Manage deployments, manifests, and resources programmatically across projects, with support for previewing changes before applying them. Templates can compose multiple Cloud services (Compute Engine, Cloud Storage, Cloud SQL) into a single repeatable deployment. Built for teams running infrastructure-as-code workflows on Google Cloud.

Jentic One on Github View OpenAPI Document

Connect the Cloud Deployment Manager V2 API to your agent

Capabilities

Start building with Cloud Deployment Manager V2 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Google Cloud Deployment Manager V2 API