Kuma
Kuma is a platform-agnostic open-source service mesh built on top of Envoy proxy. It provides universal connectivity, security, and observability for services and microservices running on any infrastructure including Kubernetes and VMs.
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 Kuma the way a machine reads it — 48 machine-readable artifacts across 38 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 — Kuma scores 53.8/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 Kuma
Each block below is one kind of artifact we hold for Kuma. 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 38
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.
Kuma Kubernetes Policy API
Kuma extends the Kubernetes API server with Custom Resource Definitions (CRDs) for defining and managing service mesh policies. These resources include MeshTrafficPermission, Me...
Kuma Multizone API
Kuma's Multizone deployment API enables managing service meshes across multiple Kubernetes clusters and Universal zones from a single global control plane. It provides resources...
Kuma Dataplane API
The Dataplane API from Kuma — 2 operation(s) for dataplane.
Kuma GlobalInsight API
The GlobalInsight API from Kuma — 1 operation(s) for globalinsight.
Kuma HostnameGenerator API
The HostnameGenerator API from Kuma — 2 operation(s) for hostnamegenerator.
Kuma Inspect API
The Inspect API from Kuma — 4 operation(s) for inspect.
Kuma KRI API
The KRI API from Kuma — 1 operation(s) for kri.
Kuma Mesh API
The Mesh API from Kuma — 2 operation(s) for mesh.
Kuma MeshAccessLog API
The MeshAccessLog API from Kuma — 2 operation(s) for meshaccesslog.
Kuma MeshCircuitBreaker API
The MeshCircuitBreaker API from Kuma — 2 operation(s) for meshcircuitbreaker.
Kuma Meshes API
The Meshes API from Kuma — 9 operation(s) for meshes.
Kuma MeshExternalService API
The MeshExternalService API from Kuma — 2 operation(s) for meshexternalservice.
Kuma MeshFaultInjection API
The MeshFaultInjection API from Kuma — 2 operation(s) for meshfaultinjection.
Kuma MeshGateway API
The MeshGateway API from Kuma — 2 operation(s) for meshgateway.
Kuma MeshHealthCheck API
The MeshHealthCheck API from Kuma — 2 operation(s) for meshhealthcheck.
Kuma MeshHTTPRoute API
The MeshHTTPRoute API from Kuma — 2 operation(s) for meshhttproute.
Kuma MeshIdentity API
The MeshIdentity API from Kuma — 2 operation(s) for meshidentity.
Kuma MeshLoadBalancingStrategy API
The MeshLoadBalancingStrategy API from Kuma — 2 operation(s) for meshloadbalancingstrategy.
Kuma MeshMetric API
The MeshMetric API from Kuma — 2 operation(s) for meshmetric.
Kuma MeshMultiZoneService API
The MeshMultiZoneService API from Kuma — 2 operation(s) for meshmultizoneservice.
Kuma MeshOpenTelemetryBackend API
The MeshOpenTelemetryBackend API from Kuma — 2 operation(s) for meshopentelemetrybackend.
Kuma MeshPassthrough API
The MeshPassthrough API from Kuma — 2 operation(s) for meshpassthrough.
Kuma MeshProxyPatch API
The MeshProxyPatch API from Kuma — 2 operation(s) for meshproxypatch.
Kuma MeshRateLimit API
The MeshRateLimit API from Kuma — 2 operation(s) for meshratelimit.
Kuma MeshRetry API
The MeshRetry API from Kuma — 2 operation(s) for meshretry.
Kuma MeshService API
The MeshService API from Kuma — 2 operation(s) for meshservice.
Kuma MeshTCPRoute API
The MeshTCPRoute API from Kuma — 2 operation(s) for meshtcproute.
Kuma MeshTimeout API
The MeshTimeout API from Kuma — 2 operation(s) for meshtimeout.
Kuma MeshTLS API
The MeshTLS API from Kuma — 2 operation(s) for meshtls.
Kuma MeshTrace API
The MeshTrace API from Kuma — 2 operation(s) for meshtrace.
Kuma MeshTrafficPermission API
The MeshTrafficPermission API from Kuma — 2 operation(s) for meshtrafficpermission.
Kuma MeshTrust API
The MeshTrust API from Kuma — 2 operation(s) for meshtrust.
Kuma MeshZoneAddress API
The MeshZoneAddress API from Kuma — 2 operation(s) for meshzoneaddress.
Kuma Secret API
The Secret API from Kuma — 2 operation(s) for secret.
Kuma System API
The System API from Kuma — 2 operation(s) for system.
Kuma Workload API
The Workload API from Kuma — 2 operation(s) for workload.
Kuma ZoneEgress API
The ZoneEgress API from Kuma — 2 operation(s) for zoneegress.
Kuma ZoneIngress API
The ZoneIngress API from Kuma — 2 operation(s) for zoneingress.
Scroll within the panel for all 38 ·
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).
Kuma API
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.
Kuma Plans Pricing
PLANSRate 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.
Kuma 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.
Kuma Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Kuma Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Kuma API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Kuma Mesh Resource Schema
JSON SCHEMASecurity Posture 2
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.
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 Kuma — 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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/kuma · machine-readable index on apis.io