Apache Mesos
Apache Mesos is a retired cluster manager (now in the Apache Attic) that provided efficient resource isolation and sharing across distributed applications or frameworks. It abstracted CPU, memory, storage, and other compute resources from machines, enabling fault-tolerant and elastic distributed systems. Mesos exposed comprehensive HTTP APIs for schedulers, operators, executors, and agents.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Apache Mesos the way a machine reads it — 27 machine-readable artifacts across 2 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 — Apache Mesos scores 37.8/100 (thin), with a separate agent-readiness read of 39/100 (agent aware). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Apache Mesos
Each block below is one kind of artifact we hold for Apache Mesos. 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 2
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.
Apache Mesos Scheduler HTTP API
The Mesos Scheduler HTTP API at /api/v1/scheduler enables framework schedulers to subscribe to resource offers, launch tasks, kill tasks, reconcile status, and manage framework ...
Apache Mesos Apache Mesos Operator HTTP API API
The Apache Mesos Operator HTTP API API from Apache Mesos — 1 operation(s) for apache mesos operator http api.
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).
Apache Mesos Operator HTTP 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.
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.
Apache Mesos 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.
Apache Mesos Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Resource Abstraction
Abstracts CPU, memory, storage, and other compute resources from physical machines across the entire cluster.
Two-Level Scheduling
Framework schedulers receive resource offers from Mesos and decide how to use them, enabling coexistence of diverse workloads.
Linear Scalability
Proven to scale to tens of thousands of nodes with fault-tolerant replicated master using ZooKeeper.
Container Support
Native Docker and AppC container image support for running containerized workloads.
HTTP API
Comprehensive HTTP API supporting JSON and Protobuf encoding for schedulers, operators, executors, and agents.
High Availability
Fault-tolerant master failover via ZooKeeper with automatic leader election and state recovery.
Resource Reservations
Static and dynamic resource reservations for frameworks and roles with quota management.
Maintenance Scheduling
Built-in maintenance window scheduling for graceful draining and reactivation of agent nodes.
Scroll within the panel for all 8 ·
Security 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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Distributed Systems Orchestration
Run multiple distributed frameworks including Hadoop, Spark, and Kafka on shared cluster resources.
Container Orchestration
Schedule and manage containerized workloads across a datacenter with resource isolation.
Big Data Processing
Run Apache Spark, Hadoop MapReduce, and other big data frameworks on Mesos-managed resources.
Microservices Platform
Host microservices workloads with Marathon framework providing long-running service scheduling on Mesos.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apache Hadoop
Run Hadoop MapReduce jobs on Mesos-managed cluster resources.
Apache Spark
Apache Spark supports Mesos as a cluster manager for distributed job execution.
Apache Kafka
Kafka brokers can be scheduled and managed on Mesos clusters.
Apache ZooKeeper
ZooKeeper provides leader election and state storage for Mesos master high availability.
Docker
Native Docker container image and runtime support for containerized workload execution.
Elasticsearch
Elasticsearch can be deployed and managed as a framework on Mesos clusters.
Resources
Every other property we hold for Apache Mesos — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-mesos · machine-readable index on apis.io