Design Standards

Design Standards encompasses the frameworks, guidelines, and best practices used in product, interface, and system design to ensure consistency, usability, and accessibility. Includes API design guidelines, naming and format conventions, accessibility conformance, deprecation policy, and governance practices.

Design Standards is listed with 1 API on the APIs.io network. Tagged areas include Accessibility, Design Standards, Design Systems, UX, and API Guidelines.

The Design Standards catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

📡 Profile data on GitHub

11.0/100 emerging ▬ flat Agent 1/100 human only Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 API

AccessibilityDesign StandardsDesign Systems UXAPI GuidelinesGovernance

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 11.0/100 · emerging

Contract Quality 1.4 / 21

Developer Ergonomics 1.2 / 17

Access Clarity 1.3 / 17

Operational Transparency 1.2 / 11

Contract Governance 1.4 / 10

Discoverability 4.1 / 9

Regulatory Posture 0.7 / 15

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.

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 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/design-standards/"><img src="https://apis.io/badge/design-standards/card.svg" alt="Design Standards 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
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

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 6.7 — up to +23.3 composite points
Developer Ergonomics scores 7.1 — up to +18.6 composite points
Access Clarity scores 7.9 — up to +18.4 composite points

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.

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/design-standards/apis.yml: open an issue on github.com/api-evangelist/design-standards 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 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Design Standards Program

Rules, capabilities, vocabulary, and linked-data description for an organizational design standards program covering products, interfaces, and APIs.

Design Standards API pricing

Not yet checked against Design Standards'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 Design Standards's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Design Standards Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Design Standards Rate Limits

5 limits

RATE LIMITS

FinOps 1

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

Design Standards Finops

FINOPS

Semantic Vocabularies 1

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

Design Standards Context

0 classes · 0 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Design Standards API Rules

0 rules ·

SPECTRAL

Resources

Documentation 2

Reference material describing how the API behaves

Reference

Reference

Reference

Reference

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Source (apis.yml)

aid: design-standards
name: Design Standards
description: Design Standards encompasses the frameworks, guidelines, and best practices used in product, interface, and system
  design to ensure consistency, usability, and accessibility. Includes API design guidelines, naming and format conventions,
  accessibility conformance, deprecation policy, and governance practices.
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/design-standards.png
tags:
- Accessibility
- Design Standards
- Design Systems
- UX
- API Guidelines
- Governance
url: https://raw.githubusercontent.com/api-evangelist/design-standards/refs/heads/main/apis.yml
created: '2025-01-01'
modified: '2026-04-28'
specificationVersion: '0.23'
apis:
- aid: design-standards:program
  name: Design Standards Program
  description: Rules, capabilities, vocabulary, and linked-data description for an organizational design standards program
    covering products, interfaces, and APIs.
  tags:
  - Standards
  - Governance
  properties:
  - type: Rules
    url: https://raw.githubusercontent.com/api-evangelist/design-standards/main/rules/design-standards-rules.yml
  - type: Capabilities
    url: https://raw.githubusercontent.com/api-evangelist/design-standards/main/capabilities/design-standards-capabilities.md
  - type: Vocabulary
    url: https://raw.githubusercontent.com/api-evangelist/design-standards/main/vocabulary/design-standards-vocabulary.json
  - type: JSONLD
    url: https://raw.githubusercontent.com/api-evangelist/design-standards/main/json-ld/design-standards.jsonld
common:
- type: Plans
  url: plans/design-standards-plans-pricing.yml
- type: RateLimits
  url: rate-limits/design-standards-rate-limits.yml
- type: FinOps
  url: finops/design-standards-finops.yml
- type: Reference
  url: https://opensource.zalando.com/restful-api-guidelines/
- type: Reference
  url: https://www.w3.org/TR/WCAG21/
- type: GitHubOrganization
  url: https://github.com/api-evangelist
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Design Standards API — frequently asked questions

Does Design Standards have an API?

Yes. APIs.io lists 1 API from Design Standards, including Design Standards Program.

How much does the Design Standards API cost?

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

Is the Design Standards API ready for AI agents?

Design Standards has a Kin Score of 11.0 out of 100 (emerging) and an Agent Readiness score of 0.6 (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.

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/design-standards"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/design-standards/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.