Pulumi Context API Exposes Unified Infrastructure Graph for AI Agents and Platform Teams

Pulumi has launched the public preview of its Context API, a read-only platform feature that consolidates Pulumi-managed stacks, inter-stack dependencies, and unmanaged discovered resources into a single queryable graph. Operating over REST and the Pulumi CLI via commands like `pulumi api GraphQuery`, the engine accepts structured JSON queries defined by anchor points, relationship traversals, and projection filters. Designed from the ground up for agentic workflows, the API provides self-documenting Markdown schema endpoints that enable AI agents—such as Pulumi Neo, Cursor, and Claude Code—to autonomously discover vocabulary and validate queries. The capability is currently available for Enterprise and Business Critical tiers using Pulumi CLI v3.243.0 and above. For platform and cloud infrastructure teams, this release addresses the chronic visibility problem inherent in distributed cloud architectures. Determining downstream blast radius—such as identifying which microservice stacks consume outputs from a shared networking module, or locating every resource bound to an out-of-date AWS provider instance—historically required manual state file inspection or brittle scripting. By modeling cloud estates as connected nodes with typed relationships (such as provider ownership, output references, and parent-child links), the Context API allows engineers and automated tools to assess changes comprehensively before running destructive provisioning tasks. This release reflects a major evolution in DevOps and platform engineering: the transition from imperative infrastructure scripting toward agent-native, context-rich platforms. As organizations increasingly task large language model coding agents with infrastructure generation and triage, agents require structured topology rather than isolated state snapshots. While traditional resource searching handles property-level filtering, graph-based querying provides relational awareness. Pulumi's architectural shift aligns with broader industry momentum across multi-cloud management and AI governance, positioning the infrastructure control plane as an interactive knowledge base for both human operators and autonomous systems. In practice, engineering organizations should begin incorporating the Context API into automated deployment pipelines, incident triage playbooks, and internal developer platforms (IDPs). Because permissions mirror existing Pulumi Cloud Role-Based Access Control (RBAC), security boundaries are preserved without separate authorization setup. Platform teams adopting coding assistants should embed the Context API schema retrieval command directly into their agent workspace guidelines (such as `AGENTS.md` or `CLAUDE.md`), enabling agents to self-correct queries dynamically when investigating deprecations, asset drift, or retirement candidates.