Score
Score is an open-source, platform-agnostic workload specification developed under the Cloud Native Computing Foundation (CNCF) Sandbox program. It provides a developer-centric YAML specification that enables teams to define application workloads once and deploy them across multiple container platforms including Docker Compose, Kubernetes, and cloud runtimes without environment-specific configuration drift. The score-spec organization provides reference CLI implementations (score-compose and score-k8s) that translate Score YAML into platform-specific manifests, eliminating YAML bloat and reducing cognitive load for platform engineering teams.
Score publishes 3 APIs on the APIs.io network. Tagged areas include Platform Engineering, Cloud-Native, CNCF, Workload Specification, and Kubernetes.
The Score catalog on APIs.io includes 1 JSON-LD context.
Score’s developer surface includes documentation, engineering blog, and 7 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Score Specification
The Score Specification (score.yaml) is a declarative, platform-agnostic workload definition format that captures containers, service ports, and resource dependencies in a singl...
score-compose
score-compose is the reference Score implementation that translates Score YAML workload specifications into Docker Compose configuration files. It enables local development envi...
score-k8s
score-k8s is the reference Score implementation that translates Score YAML workload specifications into Kubernetes manifests including Deployments, Services, ConfigMaps, and Sec...
Pricing Plans 1
Published pricing tiers and plan structures.
Score Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Score Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Score Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Score Context
JSON-LDExamples 2
Example request and response payloads for these APIs.
Score Basic Workload Example
EXAMPLEScore Compose Output Example
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Documentation 1
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/score"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/score/operations?limit=25"
curl "https://apis.io/api/v1/providers/score/evidence"
Discovery needs no key. Ratings and market analysis are Pro.