Docker
Docker is a platform for developers and sysadmins to build, share, and run applications in containers, packaging code and dependencies together for consistent deployment across environments.
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 Docker the way a machine reads it — 37 machine-readable artifacts across 15 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 — Docker scores 45.3/100 (developing), with a separate agent-readiness read of 64/100 (agent native). 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 Docker
Each block below is one kind of artifact we hold for Docker. 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 15
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.
Docker Config API
Configs are application configurations that can be used by services. Swarm mode must be enabled for these endpoints to work.
Docker Container API
Create and manage containers.
Docker Distribution API
The Distribution API from Docker — 1 operation(s) for distribution.
Docker Exec API
Run new commands inside running containers. Refer to the [command-line reference](https://docs.docker.com/engine/reference/commandline/exec/) for more information. To exec a com...
Docker Image API
The Image API from Docker — 15 operation(s) for image.
Docker Network API
Networks are user-defined networks that containers can be attached to. See the [networking documentation](https://docs.docker.com/network/) for more information.
Docker Node API
Nodes are instances of the Engine participating in a swarm. Swarm mode must be enabled for these endpoints to work.
Docker Plugin API
The Plugin API from Docker — 11 operation(s) for plugin.
Docker Secret API
Secrets are sensitive data that can be used by services. Swarm mode must be enabled for these endpoints to work.
Docker Service API
Services are the definitions of tasks to run on a swarm. Swarm mode must be enabled for these endpoints to work.
Docker Session API
The Session API from Docker — 1 operation(s) for session.
Docker Swarm API
Engines can be clustered together in a swarm. Refer to the [swarm mode documentation](https://docs.docker.com/engine/swarm/) for more information.
Docker System API
The System API from Docker — 6 operation(s) for system.
Docker Task API
A task is a container running on a swarm. It is the atomic scheduling unit of swarm. Swarm mode must be enabled for these endpoints to work.
Docker Volume API
Create and manage persistent storage that can be attached to containers.
Scroll within the panel for all 15 ·
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).
Docker Engine API
OPEN COLLECTIONArazzo Workflows 13
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Docker Build, Tag, and Push an Image
Check registry credentials, build an image from a build context, tag it for a registry, and push it.
ARAZZODocker Snapshot a Running Container as an Image
Pause a running container, commit its filesystem to a new image, unpause it, and tag the snapshot for a registry.
ARAZZODocker Deploy a Replicated Swarm Service with a Secret
Confirm the node is in a swarm, create a secret, deploy a replicated service that mounts it, and watch the tasks converge.
ARAZZODocker Run a Command Inside a Running Container
Confirm a container is running, create an exec instance, start it, and read back the command exit code.
ARAZZODocker Review Privileges and Install a Plugin
Read the privileges a plugin demands, install it with those privileges acknowledged, enable it, and confirm it is running.
ARAZZODocker Create a Network and Attach a Container
Create a user-defined bridge network, create a container, connect it with an alias, start it, and verify the attachment.
ARAZZODocker Create a Volume and Mount It Into a Container
Create a named volume, create a container that binds it to a mount path, start the container, and confirm the volume is in use.
ARAZZODocker Reclaim Disk Space on a Host
Measure disk usage, prune stopped containers, dangling images, unused volumes and networks, and the build cache, then measure again.
ARAZZODocker Roll a Swarm Service Onto a New Image
Read a service's current version, update it to a new image, watch the tasks reconverge, and tail the service logs.
ARAZZODocker Pull an Image and Run a Container
Pull an image from a registry, create a container from it, start it, and read back its running state.
ARAZZODocker Search, Pull, and Vet an Image
Search the registry for an official image, pull it, then inspect its metadata and layer history before use.
ARAZZODocker Stop and Remove a Container
Find a container by name, stop it gracefully, wait for it to exit, and remove it with its anonymous volumes.
ARAZZODocker Troubleshoot a Failing Container
Gather the full diagnostic picture for a container — state, logs, processes, resource stats, and filesystem drift.
ARAZZOScroll within the panel for all 13 ·
MCP Servers 2
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERDocker MCP (artifact)
MCP SERVERPricing 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.
Docker 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.
Docker 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.
Docker Finops
FINOPSSecurity 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 Docker — 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 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 18
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 18 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/docker · machine-readable index on apis.io