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 is listed with 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 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.7/100 thin ▬ flat Agent 1/100 human only Front door AI 1/6 silent Heartbeat 100/100 alive self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemium

3 APIs

Platform Engineering Cloud-Native CNCFWorkload SpecificationKubernetes Docker Developer Experience Open Source

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 26.7/100 · thin

Contract Quality 2.0 / 19

Developer Ergonomics 1.8 / 15

Access Clarity 1.3 / 15

Operational Transparency 3.5 / 10

Contract Governance 1.2 / 9

Discoverability 4.7 / 8

Regulatory Posture 1.6 / 15

Open Source Surface 10.0 / 10

Agent readiness — 1/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 75 points between them, because both conditional facets apply and carry 25 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/score/"><img src="https://apis.io/badge/score/card.svg" alt="Score on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document Ask about this →
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey) Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 10.7 — up to +22.3 composite points Ask about this →
Access Clarity scores 8.5 — up to +18.3 composite points Ask about this →
Developer Ergonomics scores 11.9 — up to +17.6 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/score/apis.yml: open an issue on github.com/api-evangelist/score to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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...

Score API pricing

Not yet checked against Score's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Score's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Score Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Score Rate Limits

5 limits

RATE LIMITS

Data License 1

How its data and outputs may be reused, quoted from its own terms.

Score

1 quoted statement, read from Score's own page on 2026-11-10.

LICENSE

FinOps 1

Cost, billing, and metering signals for API financial operations.

Score Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Score Context

44 classes · 1 properties

JSON-LD

Examples 2

Example request and response payloads for these APIs.

Score Basic Workload Example

6 fields

EXAMPLE

Score Compose Output Example

4 fields

EXAMPLE

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Score Domain Security

TLSv1.3

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

JSONLDContext

JSONLDContext

Vocabulary

Vocabulary

Build 2

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

Slack Channel

Commercial 4

Pricing, plans, and the legal terms of use

Plans

FinOps

License

DataLicense

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: score
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/score.png
name: Score
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/score/refs/heads/main/apis.yml
created: '2026-05-02'
modified: '2026-05-02'
specificationVersion: '0.23'
tags:
- Platform Engineering
- Cloud-Native
- CNCF
- Workload Specification
- Kubernetes
- Docker
- Developer Experience
- Open Source
tags_raw:
- Platform Engineering
- Cloud Native
- CNCF
- Workload Specification
- Kubernetes
- Docker
- Developer Experience
- Open Source
- Open-Source
apis:
- aid: score:score-specification
  name: Score Specification
  description: The Score Specification (score.yaml) is a declarative, platform-agnostic workload definition format that captures
    containers, service ports, and resource dependencies in a single file. Reference CLI implementations (score-compose and
    score-k8s) translate Score files into Docker Compose manifests or Kubernetes manifests respectively. The specification
    supports metadata, container definitions with environment variables and volume mounts, service port exposure, health probes,
    and resource references using placeholder syntax.
  humanURL: https://score.dev/
  tags:
  - Platform Engineering
  - Workload Specification
  - Cloud-Native
  - CNCF
  - Open Source
  tags_raw:
  - Platform Engineering
  - Workload Specification
  - Cloud Native
  - CNCF
  - Open Source
  - Open-Source
  properties:
  - type: Documentation
    url: https://docs.score.dev/
  - type: Specification
    url: https://docs.score.dev/docs/score-specification/score-spec-reference/
  - type: GitHubRepository
    url: https://github.com/score-spec/spec
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/score/refs/heads/main/vocabulary/score-vocabulary.yml
  - type: JSONLDContext
    url: https://raw.githubusercontent.com/api-evangelist/score/refs/heads/main/json-ld/score-context.jsonld
- aid: score:score-compose
  name: score-compose
  description: score-compose is the reference Score implementation that translates Score YAML workload specifications into
    Docker Compose configuration files. It enables local development environments that mirror production workload definitions,
    supports resource provisioners for common dependencies like databases and message queues, and generates runnable Docker
    Compose files from a single score.yaml source.
  humanURL: https://score.dev/
  tags:
  - Docker Compose
  - CLI
  - Local Development
  - Platform Engineering
  properties:
  - type: Documentation
    url: https://docs.score.dev/docs/score-implementation/score-compose/
  - type: GitHubRepository
    url: https://github.com/score-spec/score-compose
- aid: score:score-k8s
  name: score-k8s
  description: score-k8s is the reference Score implementation that translates Score YAML workload specifications into Kubernetes
    manifests including Deployments, Services, ConfigMaps, and Secrets. It supports Kubernetes resource provisioners, patch
    templates for customizing generated manifests, and enables consistent workload configuration from development to production
    on Kubernetes.
  humanURL: https://score.dev/
  tags:
  - Kubernetes
  - CLI
  - Platform Engineering
  - Cloud-Native
  tags_raw:
  - Kubernetes
  - CLI
  - Platform Engineering
  - Cloud Native
  properties:
  - type: Documentation
    url: https://docs.score.dev/docs/score-implementation/score-k8s/
  - type: GitHubRepository
    url: https://github.com/score-spec/score-k8s
common:
- type: Plans
  url: plans/score-plans-pricing.yml
- type: RateLimits
  url: rate-limits/score-rate-limits.yml
- type: FinOps
  url: finops/score-finops.yml
- type: IssueTracker
  url: https://github.com/score-spec/spec/issues
- type: Releases
  url: https://github.com/score-spec/spec/releases
- type: SecurityPolicy
  url: https://github.com/score-spec/spec/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/score-spec/spec/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/score-spec/spec/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/score-spec/spec/blob/main/LICENSE
- type: DomainSecurity
  url: security/score-domain-security.yml
- type: Website
  url: https://score.dev/
- type: GitHubOrganization
  url: https://github.com/score-spec
- type: Documentation
  url: https://docs.score.dev/
- type: Slack Channel
  url: https://cloud-native.slack.com/archives/C07DN0D1UCW
- type: JSONLDContext
  url: https://raw.githubusercontent.com/api-evangelist/score/refs/heads/main/json-ld/score-context.jsonld
- type: Vocabulary
  url: https://raw.githubusercontent.com/api-evangelist/score/refs/heads/main/vocabulary/score-vocabulary.yml
- url: https://score.dev/index.xml
  type: Blog
- type: DataLicense
  url: data-license/score-data-license.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Score API — frequently asked questions

Does Score have an API?

Yes. APIs.io lists 3 APIs from Score, including Score Specification, score-compose and score-k8s.

How much does the Score API cost?

APIs.io lists 3 pricing plans for Score, with each plan's price, limits and inclusions under Pricing on this page.

Is the Score API ready for AI agents?

Score has a Kin Score of 26.7 out of 100 (thin) and an Agent Readiness score of 0.6 (human-only), scored by API Evangelist on 2026-11-13.

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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/score"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/score/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/score/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.