Google Cloud Service Mesh
Google Cloud Service Mesh is Google's managed service mesh solution for GKE and supported GKE Enterprise environments, enabling secure, observable, and reliable communication between microservices. It provides a managed Istio control plane, Google Cloud-native service routing APIs, mTLS security, and built-in telemetry for distributed applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Google Cloud Service Mesh the way a machine reads it — 22 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Google Cloud Service Mesh scores 48.9/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Google Cloud Service Mesh
Each block below is one kind of artifact we hold for Google Cloud Service Mesh. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Google Cloud Network Security API
The Network Security API manages security policies for Cloud Service Mesh, including authorization policies, client TLS policies, and server TLS policies. It provides REST endpo...
Google Cloud Service Mesh xDS Control Plane API
Cloud Service Mesh uses the open-source xDS v3 control plane API to distribute configuration to Envoy sidecar proxies and proxyless gRPC clients. Configurations defined via the ...
Google Cloud Service Mesh EndpointPolicies API
The EndpointPolicies API from Google Cloud Service Mesh — 1 operation(s) for endpointpolicies.
Google Cloud Service Mesh Gateways API
The Gateways API from Google Cloud Service Mesh — 1 operation(s) for gateways.
Google Cloud Service Mesh Google Cloud Network Services API (Service Mesh) API
The Google Cloud Network Services API (Service Mesh) API from Google Cloud Service Mesh — 2 operation(s) for google cloud network services api (service mesh).
Google Cloud Service Mesh GrpcRoutes API
The GrpcRoutes API from Google Cloud Service Mesh — 1 operation(s) for grpcroutes.
Google Cloud Service Mesh HttpRoutes API
The HttpRoutes API from Google Cloud Service Mesh — 1 operation(s) for httproutes.
Google Cloud Service Mesh Locations API
The Locations API from Google Cloud Service Mesh — 1 operation(s) for locations.
Google Cloud Service Mesh Meshes API
The Meshes API from Google Cloud Service Mesh — 1 operation(s) for meshes.
Google Cloud Service Mesh Operations API
The Operations API from Google Cloud Service Mesh — 1 operation(s) for operations.
Google Cloud Service Mesh ServiceLbPolicies API
The ServiceLbPolicies API from Google Cloud Service Mesh — 1 operation(s) for servicelbpolicies.
Google Cloud Service Mesh TcpRoutes API
The TcpRoutes API from Google Cloud Service Mesh — 1 operation(s) for tcproutes.
Google Cloud Service Mesh TlsRoutes API
The TlsRoutes API from Google Cloud Service Mesh — 1 operation(s) for tlsroutes.
Scroll within the panel for all 13 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Google Cloud Network Services API (Service Mesh)
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Google Cloud Service Mesh Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Google Cloud Service Mesh — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/google-cloud-service-mesh · machine-readable index on apis.io