Bare Metal Solution API

Name: Bare Metal Solution API API
Brand: Bare Metal Solution API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureComputeoauth233 EndpointsREST

For Agents

Manage Google Cloud Bare Metal Solution instances, volumes, networks, and LUNs from automation tooling.

Quickstart

Get started with Bare Metal Solution API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list Google Bare Metal Solution instances"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bare Metal Solution API API.

Detach a SAN LUN from a Bare Metal instance via /v2/{+instance}:detachLun

List network usage for a region with /v2/{+location}/networks:listNetworkUsage

Disable hyperthreading on an instance via /v2/{+name}:disableHyperthreading

Disable the interactive serial console on an instance with :disableInteractiveSerialConsole

GET STARTED

Start building with Bare Metal Solution API API

Explore with Jentic

View OpenAPI Document

Use for: I need to detach a SAN LUN from a Bare Metal Solution instance, List the network usage in europe-west3 for our Bare Metal deployment, Disable hyperthreading on a database server for licensing compliance, Disable the interactive serial console on a production instance

Not supported: Does not run a hypervisor, manage VMs, or perform OS-level configuration on the bare-metal servers — use for instance, network, volume, and LUN control-plane operations only.

The Bare Metal Solution API manages physical bare-metal servers, networks, volumes, and SAN LUNs hosted in regional extensions adjacent to Google Cloud data centres. It exposes operations to detach LUNs from instances, list network usage, disable hyperthreading or interactive serial console, and patch instance, network, and volume settings. The API is the control plane for legacy or licence-bound workloads such as Oracle databases that must run on dedicated hardware while integrating with Google Cloud networking. It does not run a hypervisor or manage VMs.

Use Cases

Patterns agents use Bare Metal Solution API API for, with concrete tasks.

★ Oracle Database Licensing Compliance

Run Oracle workloads on dedicated bare-metal hardware adjacent to Google Cloud while keeping core counts auditable for licensing. The API exposes disableHyperthreading so an automation can ensure each licensed instance presents the expected core count, and patch endpoints let labels and metadata be kept in sync with the licence inventory.

POST to /v2/{name}:disableHyperthreading on each licensed instance and verify the resulting state in the response.

Storage Volume and LUN Management

Manage SAN volumes and the LUNs they expose across a Bare Metal Solution deployment by listing volumes, patching their metadata, and detaching LUNs when an instance is decommissioned. Suited to storage admins running mixed-tenant SAN setups that need code-driven hygiene.

POST to /v2/{instance}:detachLun for each LUN being moved off a decommissioned instance and patch the volume labels.

Network Usage Reporting Across Regions

Build network usage dashboards by calling listNetworkUsage on each region where a Bare Metal Solution deployment exists. The endpoint returns aggregated bandwidth and capacity data that feeds into capacity planning and chargeback workflows without requiring agents on the hardware itself.

GET /v2/{location}/networks:listNetworkUsage for each region and aggregate the results into a chargeback report.

AI Agent Hardware Hygiene Checks via Jentic

Use an AI agent to run a periodic hygiene check against Bare Metal Solution instances confirming hyperthreading state, console status, and label correctness. Through Jentic the agent finds the relevant operations by intent and runs them with project credentials supplied at execute time, with no Google Cloud SDK setup needed in the agent.

Use Jentic search for 'list Bare Metal Solution instances', and for each instance call the get endpoint and patch labels missing from the inventory.

Key Endpoints

33 endpoints — the bare metal solution api manages physical bare-metal servers, networks, volumes, and san luns hosted in regional extensions adjacent to google cloud data centres.

METHOD

PATH

DESCRIPTION

POST

/v2/{+instance}:detachLun

Detach a LUN from a Bare Metal instance

GET

/v2/{+location}/networks:listNetworkUsage

List network usage in a location

POST

/v2/{+name}:disableHyperthreading

Disable hyperthreading on an instance

POST

/v2/{+name}:disableInteractiveSerialConsole

Disable the interactive serial console

PATCH

/v2/{+name}

Update an instance, network, or volume

GET

/v2/{+name}

Get an instance, network, volume, or LUN by resource name

GET

/v2/{+name}/locations

List Bare Metal Solution locations

POST

/v2/{+instance}:detachLun

Detach a LUN from a Bare Metal instance

GET

/v2/{+location}/networks:listNetworkUsage

List network usage in a location

POST

/v2/{+name}:disableHyperthreading

Disable hyperthreading on an instance

POST

/v2/{+name}:disableInteractiveSerialConsole

Disable the interactive serial console

PATCH

/v2/{+name}

Update an instance, network, or volume

Why though Jentic?

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

Credential isolation

Service account keys with Bare Metal Solution scopes are encrypted in the Jentic vault. Agents only see scoped, short-lived access tokens — never the raw JSON key.

Intent-based discovery

Agents search Jentic with intents like 'detach a LUN from a Bare Metal instance' and Jentic returns the matching operation with its input schema for direct execution.

Time to first call

Direct integration: 2-4 days for IAM setup, networking config, and operation polling. Through Jentic: under 2 hours once the credential is registered.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Compute Engine API

Virtualised compute instead of dedicated bare-metal hardware

Choose Compute Engine when the workload does not require dedicated hardware or specific licensing controls.

Complementary

Network Connectivity API

Connects Bare Metal Solution networks into broader Google Cloud network topology

Use to wire Bare Metal networks into VPCs and hybrid connectivity hubs.

Complementary

Cloud Monitoring API

Observability for Bare Metal Solution instances and networks

Pair when an agent must report on Bare Metal posture in the same dashboards as the rest of the cloud estate.

FAQs

Specific to using Bare Metal Solution API API through Jentic.

What authentication does the Bare Metal Solution API use?

The API uses Google OAuth 2.0 with cloud-platform scope. Service accounts must hold the roles/baremetalsolution.* IAM role on the relevant project. Through Jentic the service account credential is encrypted in the vault and only short-lived access tokens reach the agent.

Can I detach a LUN from an instance through the API?

Yes. POST to /v2/{instance}:detachLun with the LUN resource name in the body. The call returns a long-running operation that completes once the LUN is unmapped from the instance.

How do I disable hyperthreading on a Bare Metal Solution server?

POST to /v2/{name}:disableHyperthreading where name is the instance resource path. The instance reboots as part of the change, so schedule it during a maintenance window.

What are the rate limits for the Bare Metal Solution API?

Numeric limits are not declared in the spec; quotas are enforced per project on baremetalsolution.googleapis.com. Review the project quota dashboard before running large list or patch jobs.

How do I run a hygiene sweep across instances through Jentic?

Search Jentic for 'list Bare Metal Solution instances'. Jentic returns the matching list operation; iterate the result and call the get and patch operations as needed, with credentials supplied from the Jentic vault at each call.

Can the API provision new Bare Metal hardware?

Initial provisioning of physical hardware in a regional extension is handled through a Google Cloud sales process. Once provisioned, the instances and storage are managed through this API.