Cloudsmith
Cloudsmith is a cloud-native, universal package management platform providing fully managed, geo-replicated artifact repositories for over 30 package formats (Docker, npm, Maven, NuGet, PyPI, RubyGems, RPM, Deb, Helm, Cargo, Go, Composer, Conan, Conda, Vagrant, Raw, and more). The Cloudsmith REST API (v1) at api.cloudsmith.io exposes operations for organizations, repositories, packages, files, entitlements, vulnerabilities, webhooks, audit logs, metrics, quotas, deny policies, namespaces, distros, formats, recycle bin, storage regions, and broadcasts. Authentication is via API key passed in the Authorization header as "token YOUR_API_KEY".
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 Cloudsmith the way a machine reads it — 31 machine-readable artifacts across 22 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 — Cloudsmith scores 46.7/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 Cloudsmith
Each block below is one kind of artifact we hold for Cloudsmith. 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 22
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.
Cloudsmith audit-log API
The audit-log API from Cloudsmith — 2 operation(s) for audit-log.
Cloudsmith badges API
The badges API from Cloudsmith — 1 operation(s) for badges.
Cloudsmith broadcasts API
The broadcasts API from Cloudsmith — 1 operation(s) for broadcasts.
Cloudsmith bulk-action API
The bulk-action API from Cloudsmith — 1 operation(s) for bulk-action.
Cloudsmith distros API
The distros API from Cloudsmith — 2 operation(s) for distros.
Cloudsmith entitlements API
The entitlements API from Cloudsmith — 8 operation(s) for entitlements.
Cloudsmith files API
The files API from Cloudsmith — 5 operation(s) for files.
Cloudsmith formats API
The formats API from Cloudsmith — 2 operation(s) for formats.
Cloudsmith metrics API
The metrics API from Cloudsmith — 3 operation(s) for metrics.
Cloudsmith namespaces API
The namespaces API from Cloudsmith — 2 operation(s) for namespaces.
Cloudsmith orgs API
The orgs API from Cloudsmith — 40 operation(s) for orgs.
Cloudsmith packages API
The packages API from Cloudsmith — 70 operation(s) for packages.
Cloudsmith quota API
The quota API from Cloudsmith — 4 operation(s) for quota.
Cloudsmith rates API
The rates API from Cloudsmith — 1 operation(s) for rates.
Cloudsmith recycle-bin API
The recycle-bin API from Cloudsmith — 2 operation(s) for recycle-bin.
Cloudsmith repos API
The repos API from Cloudsmith — 59 operation(s) for repos.
Cloudsmith status API
The status API from Cloudsmith — 1 operation(s) for status.
Cloudsmith storage-regions API
The storage-regions API from Cloudsmith — 2 operation(s) for storage-regions.
Cloudsmith user API
The user API from Cloudsmith — 4 operation(s) for user.
Cloudsmith users API
The users API from Cloudsmith — 1 operation(s) for users.
Cloudsmith vulnerabilities API
The vulnerabilities API from Cloudsmith — 4 operation(s) for vulnerabilities.
Cloudsmith webhooks API
The webhooks API from Cloudsmith — 2 operation(s) for webhooks.
Scroll within the panel for all 22 ·
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).
Cloudsmith API (v1)
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.
Cloudsmith 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.
Cloudsmith 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.
Cloudsmith 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.
Cloudsmith API Rules
SPECTRALSecurity 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 Cloudsmith — 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 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cloudsmith · machine-readable index on apis.io