Root (fka Slim.ai)
Root (formerly Slim.ai) is a container and dependency security company backed by Insight Partners. Its "secure supply" platform delivers end-to-end, autonomous vulnerability remediation for container images and application packages: a fleet of AI agents (Agentic Vulnerability Remediation, AVR) researches, patches, tests, and ships Root Patches within minutes of CVE publication, without base-image changes or forced version upgrades. Root operates the Root Image Catalog (cr.root.io), Library Catalog, and OS-package registry (pkg.root.io), and exposes a REST API (api.root.io) for querying patch status, security findings, subscriptions, and pulling SBOM, VEX, and provenance artifacts, plus Standard-Webhooks notifications and a first-party CLI (rootio_patcher).
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 Root (fka Slim.ai) the way a machine reads it — 27 machine-readable artifacts across 20 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 — Root (fka Slim.ai) scores 53.7/100 (developing), with a separate agent-readiness read of 78/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.
How we profile Root (fka Slim.ai)
Each block below is one kind of artifact we hold for Root (fka Slim.ai). 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 20
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.
Root (fka Slim.ai) Accounts API
The Accounts API from Root (fka Slim.ai) — 3 operation(s) for accounts.
Root (fka Slim.ai) API Keys API
The API Keys API from Root (fka Slim.ai) — 2 operation(s) for api keys.
Root (fka Slim.ai) Authentication API
The Authentication API from Root (fka Slim.ai) — 1 operation(s) for authentication.
Root (fka Slim.ai) AVR API
The AVR API from Root (fka Slim.ai) — 6 operation(s) for avr.
Root (fka Slim.ai) Billing API
The Billing API from Root (fka Slim.ai) — 1 operation(s) for billing.
Root (fka Slim.ai) Core - Discovered Packages V3 API
The Core - Discovered Packages V3 API from Root (fka Slim.ai) — 1 operation(s) for core - discovered packages v3.
Root (fka Slim.ai) CveFeed API
The CveFeed API from Root (fka Slim.ai) — 1 operation(s) for cvefeed.
Root (fka Slim.ai) Discovery API
The Discovery API from Root (fka Slim.ai) — 2 operation(s) for discovery.
Root (fka Slim.ai) Invitations API
The Invitations API from Root (fka Slim.ai) — 3 operation(s) for invitations.
Root (fka Slim.ai) Notifications API
The Notifications API from Root (fka Slim.ai) — 4 operation(s) for notifications.
Root (fka Slim.ai) Organizations API
The Organizations API from Root (fka Slim.ai) — 1 operation(s) for organizations.
Root (fka Slim.ai) OSVFeed API
The OSVFeed API from Root (fka Slim.ai) — 3 operation(s) for osvfeed.
Root (fka Slim.ai) Package API
The Package API from Root (fka Slim.ai) — 4 operation(s) for package.
Root (fka Slim.ai) Patches API
The Patches API from Root (fka Slim.ai) — 3 operation(s) for patches.
Root (fka Slim.ai) PatchFeed API
The PatchFeed API from Root (fka Slim.ai) — 1 operation(s) for patchfeed.
Root (fka Slim.ai) Remediation API
The Remediation API from Root (fka Slim.ai) — 10 operation(s) for remediation.
Root (fka Slim.ai) Security Findings API
The Security Findings API from Root (fka Slim.ai) — 4 operation(s) for security findings.
Root (fka Slim.ai) Subscriptions API
The Subscriptions API from Root (fka Slim.ai) — 2 operation(s) for subscriptions.
Root (fka Slim.ai) System Matrix API
The System Matrix API from Root (fka Slim.ai) — 2 operation(s) for system matrix.
Root (fka Slim.ai) Webhooks API
The Webhooks API from Root (fka Slim.ai) — 3 operation(s) for webhooks.
Scroll within the panel for all 20 ·
MCP Servers 1
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.
root-fka-slimai-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Root Fka Slimai Webhooks
ASYNCAPISecurity Posture 4
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 Root (fka Slim.ai) — 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 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/root-fka-slimai · machine-readable index on apis.io