Minimus
Minimus provides hardened, minimal container images designed for security-conscious teams. Its images are built from source with near-zero CVEs, rebuilt daily, and typically around 95% smaller than standard alternatives, with drop-in compatibility for existing workflows. Images ship audit-ready for compliance regimes including FedRAMP, NIST 800-190, FIPS 140-3, CIS, STIG, and SLSA L3, and the company is SOC 2 and ISO 27001 certified. The programmatic surface is the first-party minicli tool (manage private image recipes as code and trigger asynchronous builds), an open MinimOS apk package repository, and a generate-skills feature that makes the CLI agent-native for assistants such as Claude, Codex, and Cursor. Surfaced as a Mayfield portfolio company and enriched by the API Evangelist pipeline.
Minimus is profiled on the APIs.io network. Tagged areas include Company, Container Images, Container Security, Supply Chain Security, and DevSecOps.
Minimus’ developer surface includes documentation, getting-started guide, support, engineering blog, pricing, signup flow, CLI, and 15 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Cloud Native (Kubernetes, CNCF, FinOps) | standard | 53.9 | - | - |
| NIST CMVP FIPS 140 Validated Cryptographic Modules (FIPS 140-1 / 140-2 / 140-3) | standard | 53.9 | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 2
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Source (apis.yml)
Minimus API — frequently asked questions
How do I authenticate with the Minimus API?
Minimus uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Minimus Authentication.
Does Minimus have an MCP server?
Yes. APIs.io lists 1 MCP server for Minimus: Remote MCP server at docs.minimus.io over HTTP; 3 tools listed.
Is the Minimus API ready for AI agents?
Minimus has a Kin Score of 33.7 out of 100 (thin) and an Agent Readiness score of 4.7 (human-only), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.