Google Cloud IoT Core API (DEPRECATED)

DEPRECATED AS OF AUGUST 16, 2023 — Google Cloud IoT Core has been shut down and is no longer accepting new customers or traffic; do not build new systems on this API. It previously provided device registry management, MQTT/HTTP bridge for device telemetry, and bidirectional device state/config over GCP Pub/Sub.

Evaluated Mar 06, 2026 (0d ago) vdeprecated-2023
Homepage ↗ Other gcp iot deprecated mqtt http-bridge device-registry telemetry pubsub
⚙ Agent Friendliness
2
/ 100
Can an agent use this?
🔒 Security
0
/ 100
Is it safe for agents?
⚡ Reliability
0
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
20
Error Messages
10
Auth Simplicity
0
Rate Limits
0

🔒 Security

TLS Enforcement
0
Auth Strength
0
Scope Granularity
0
Dep. Hygiene
0
Secret Handling
0

Service is shut down. No security posture applies. Previously used mutual TLS and JWT for device auth.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
0
AF Security Reliability

Best When

Only relevant when an AI agent is auditing or migrating a legacy system that was built on Google Cloud IoT Core before its 2023 deprecation.

Avoid When

Avoid entirely for any new development — the service is shut down. Use Azure IoT Hub, AWS IoT Core, or HiveMQ as alternatives.

Use Cases

  • HISTORICAL ONLY: Registering IoT devices with X.509 certificates or RS256/ES256 JWT authentication in a managed device registry
  • HISTORICAL ONLY: Receiving telemetry events from devices via MQTT or HTTP bridge routed to Cloud Pub/Sub topics
  • HISTORICAL ONLY: Sending configuration updates to devices and reading device state reported back to the cloud
  • MIGRATION TARGET: Evaluating existing IoT Core workloads to migrate to HiveMQ, EMQX, or self-managed MQTT on GKE
  • MIGRATION TARGET: Understanding legacy system architecture for agents tasked with modernizing IoT Core integrations to alternative platforms

Not For

  • Any new IoT project — this service is fully shut down and will return errors for all API calls
  • Production workloads of any kind — the API is no longer operational as of August 16, 2023
  • Learning or prototyping IoT concepts — use AWS IoT Core, Azure IoT Hub, or HiveMQ Cloud instead

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: none_service_shutdown
OAuth: No Scopes: No

Service is shut down. Previously used JWT tokens signed with RS256 or ES256 device keys for MQTT, and GCP service account OAuth2 for management API. All auth mechanisms are non-functional.

Pricing

Model: shutdown
Free tier: No
Requires CC: No

Google Cloud IoT Core was shut down on August 16, 2023. No new usage is possible and existing usage ceased at that date.

Agent Metadata

Pagination
none
Idempotent
Not_applicable
Retry Guidance
Not documented

Known Gotchas

  • CRITICAL: This service was permanently shut down on August 16, 2023 — any agent attempting to use this API will receive errors or timeouts on all calls
  • Google's migration guide recommends HiveMQ, EMQX, or building on Cloud Pub/Sub + Cloud Functions directly as replacement architectures
  • Existing IoT Core device registries and their certificates are no longer accessible — migration required exporting device data before the shutdown date
  • The Cloud IoT Core SDK libraries have been deprecated and archived on GitHub — do not install or use google-cloud-iot client libraries in new projects
  • Pub/Sub topics that were backed by IoT Core telemetry routes still exist but receive no data — agents inspecting legacy GCP projects may find orphaned Pub/Sub topics from IoT Core migrations

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Google Cloud IoT Core API (DEPRECATED).

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered