VMware has made a small announcement that matters more than it reads. In SDK generation for VCF APIs using OpenAPI Specifications, Jatin Purohit opens with the fact that carries the post: “Starting with VMware Cloud Foundation (VCF) 9.0, VMware officially publishes OpenAPI specifications for VCF APIs.” The rest is a working guide to generating a .NET client from them with OpenAPI Generator, targeting .NET 8 and RestSharp, and the argument is the one this network has always made: when the specification is the source of truth, “whether your developer teams build in C#, Go, Rust, TypeScript, or Swift, language choice is no longer a blocker.”
There are no vendor figures to discount, and the practical details are the kind only someone who has run the generator against a real enterprise spec would write down. The vSphere specifications are large enough that the generator’s YAML parser crashes past its default limit of about 3 MB of code points, so the post passes a maxYamlCodePoints system property to the JVM first. It trims generation to the five API groups the sample needs with the --global-property apis flag, rather than producing a client for the whole surface. And it generates two independent projects, one for the vSphere Automation REST API at /api and one for the Virtual Infrastructure JSON API at /sdk/vim25, the JSON-RPC equivalent of the classic SOAP endpoint. The specifications live in a public repository, vmware/vcf-api-specs, with folders for vSphere, NSX, SDDC Manager, the VCF installer, VCF operations, and more.
The catalog holds most of the VCF surface and misses the piece the post is built on. The VMware provider page lists 59 API pages, including the VMware Cloud Foundation API, the SDDC Manager API, the VCF Installer API, and the vSphere Web Services API, which is the classic interface the /sdk/vim25 JSON API mirrors. What it does not have is an API page for the vSphere Automation REST API the post generates its client from, and the record does not register the vcf-api-specs repository at all. It points at the vSphere Automation documentation and the Java SDK. That is our gap, and it is filed. The agentic access profile maps 49 operations, 22 of them acting.
The Kin Score is 52.3, developing band. Developer ergonomics carries it at 75.0 and contract quality at 62.6, with access clarity at 47.4 and operational transparency at 23.7, the lowest facet on the record. The Agent Readiness score is 24.8, agent-aware. Error semantics, the MCP server, idempotency, and every identity dimension are unlit. VMware has done the thing that makes everything else in this post possible, publishing the contracts in a public repository a generator can point at. The catalog’s job is to point at the same repository, and until it does, the number above is scoring VMware on the surface we found before VCF 9.0 rather than the one it now publishes.