# Mechanical Secondary at Bengaluru: deployment

Canonical ID: `d1a4373a-cdbe-411e-ab45-1a215da18344`

Secondary product deployment at Mechanical Chef operational region.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** mechanical-chef-secondary-deployment
- **Status:** operational
- **Model:** [Mechanical Secondary](/models/mechanical-chef-secondary.md) (id: `3155ffa3-6b8b-44a9-a9a6-8fdad1e2c8ee`)
- **Company:** [Mechanical Chef](/companies/mechanical-chef.md) (id: `94db5c77-7d09-4171-b63a-03f47d499000`)
- **Location:** [Bengaluru](/locations/bengaluru.md) (id: `0b242685-7a23-4c40-b751-f44b1705a654`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the Mechanical Secondary deployment at Bengaluru?

Mechanical Secondary, built by Mechanical Chef, is recorded as a deployment at Bengaluru on the DEPLOY registry. Mechanical Chef operates the deployment directly.

### Who operates Mechanical Secondary at Bengaluru?

Mechanical Chef, the manufacturer of Mechanical Secondary, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the Mechanical Secondary deployment at Bengaluru?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/d1a4373a-cdbe-411e-ab45-1a215da18344 · feeds: GET /v1/feeds?deploymentId=d1a4373a-cdbe-411e-ab45-1a215da18344 · canonical URL: /deployments/mechanical-chef-secondary-deployment_