Front-End Checklist

Front-End Checklist is an open-source project created by David Dias to provide developers with a comprehensive set of best‑practice rules for modern web development. It covers accessibility, performance, security, privacy, SEO, and more across 350+ curated rules, helping teams ship high‑quality front‑ends efficiently. The community‑driven checklist is MIT‑licensed and integrates with AI tools via MCP.

Front-End Checklist is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Frontend, Web Development, Accessibility, and Performance.

The Front-End Checklist catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Front-End Checklist’s developer surface includes documentation, API reference, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

22.2/100 emerging Agent 20/100 agent aware Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

2 APIs 1 MCP Servers

Company Frontend Web Development Accessibility Performance Open Source

Kin Score

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

Composite quality — 22.2/100 · emerging

Contract Quality 4.6 / 21

Developer Ergonomics 2.8 / 17

Access Clarity 2.9 / 17

Operational Transparency 1.0 / 11

Contract Governance 2.2 / 10

Discoverability 4.8 / 9

Regulatory Posture 2.8 / 15

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 8 / 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 0 / 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/frontendchecklist-io/"><img src="https://apis.io/badge/frontendchecklist-io/card.svg" alt="Front-End Checklist 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):

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 →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

10 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 21.6 — up to +19.6 composite points Ask about this →
Developer Ergonomics scores 16.7 — up to +16.7 composite points Ask about this →
Access Clarity scores 17.0 — up to +16.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/frontendchecklist-io/apis.yml: open an issue on github.com/api-evangelist/frontendchecklist-io 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 →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Agent2Agent

measured — observed by APIs.io (flavored)

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

APIs 2

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

Front-End Checklist MCP

MCP server exposing Front-End Checklist rules to AI agents

Front-End Checklist API

Front-End Checklist API as documented publicly: 5 operations. Contract generated from the documentation by API Evangelist (2026-11-08); not the provider's own document.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Front-End Checklist MCP Server

Remote MCP server at mcp.frontendchecklist.io.

MCP SERVER

Semantic Vocabularies 1

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

Frontendchecklist Io Context

5 classes · 4 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Front-End Checklist API Rules

38 rules · 36 error-severity 1 warn-severity 1 info-severity

SPECTRAL

JSON Schema 5

Standalone JSON Schema definitions for this provider's data models.

GetUserResponse

2 properties

JSON SCHEMA

GetUsersIdResponse

2 properties

JSON SCHEMA

GetUsersResponse

1 properties

JSON SCHEMA

PostApiUsersRequest

2 properties

JSON SCHEMA

PostApiUsersResponse

2 properties

JSON SCHEMA

Security Posture 1

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

Front-End Checklist Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Access & Security 2

Authentication, authorization, and security posture

Security

Security

DomainSecurity

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 3

Properties that don't map to a standard resource type

AgentCard

AgentCard

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: frontendchecklist-io
name: Front-End Checklist
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - security
  generated: '2026-11-13'
  method: derived
image: https://frontendchecklist.io/og-image.png
description: Front-End Checklist is an open-source project created by David Dias to provide developers with a comprehensive
  set of best‑practice rules for modern web development. It covers accessibility, performance, security, privacy, SEO, and
  more across 350+ curated rules, helping teams ship high‑quality front‑ends efficiently. The community‑driven checklist is
  MIT‑licensed and integrates with AI tools via MCP.
url: https://artifacts.apis.io/frontendchecklist-io/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-08 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-08'
modified: '2026-11-08'
tags:
- Company
- Frontend
- Web Development
- Accessibility
- Performance
- Open Source
tags_raw:
- Company
- Front-End
- Web Development
- Accessibility
- Performance
- Open Source
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/frontendchecklist-io-rules.yml
- type: JSONLD
  url: json-ld/frontendchecklist-io-context.jsonld
- type: Vocabulary
  url: vocabulary/frontendchecklist-io-vocabulary.yml
- type: DataModel
  url: data-model/frontendchecklist-io-data-model.yml
- type: Conformance
  url: conformance/frontendchecklist-io-conformance.yml
- type: LLMsTxt
  url: llms/frontendchecklist-io-llms.txt
- type: AgentCard
  url: a2a/frontendchecklist-io-a2a.yml
- type: MCPServer
  url: mcp/frontendchecklist-io-mcp.yml
- type: Hosts
  url: hosts/frontendchecklist-io-hosts.yml
- type: Vendors
  url: vendors/frontendchecklist-io-vendors.yml
- type: TermsOfService
  url: https://frontendchecklist.io/terms
- type: Security
  url: https://frontendchecklist.io/rules/security
- type: PrivacyPolicy
  url: https://frontendchecklist.io/privacy
- type: DomainSecurity
  url: security/frontendchecklist-io-domain-security.yml
- type: Website
  url: https://frontendchecklist.io/
- type: Documentation
  url: https://frontendchecklist.io/guide
- type: APIReference
  url: https://frontendchecklist.io/mcp
apis:
- name: Front-End Checklist MCP
  description: MCP server exposing Front-End Checklist rules to AI agents
  humanURL: https://frontendchecklist.io/mcp
  baseURL: null
  aid: frontendchecklist-io:front-end-checklist-mcp
- aid: frontendchecklist-io:frontendchecklist-io-api
  name: Front-End Checklist API
  description: 'Front-End Checklist API as documented publicly: 5 operations. Contract generated from the documentation by
    API Evangelist (2026-11-08);

    not the provider''s own document.'
  humanURL: https://frontendchecklist.io/rules/testing/contract-testing
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/frontendchecklist-io-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/frontendchecklist-io-post-api-users-response-schema.json
  - type: JSONSchema
    url: json-schema/frontendchecklist-io-get-users-id-response-schema.json
  - type: JSONSchema
    url: json-schema/frontendchecklist-io-get-user-response-schema.json
  - type: JSONSchema
    url: json-schema/frontendchecklist-io-get-users-response-schema.json
  - type: JSONSchema
    url: json-schema/frontendchecklist-io-post-api-users-request-schema.json
x-coverage:
  state: unreadable
  reason: js-rendered-docs
  detail: Documentation pages are static HTML without machine‑readable OpenAPI/AsyncAPI/GraphQL specs.
  evidence:
  - url: https://frontendchecklist.io/
    status: 200
  checked: '2026-11-09'
x-enrichment:
  date: '2026-11-08'
  status: enriched
  artifacts_added: 23
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Front-End Checklist API — frequently asked questions

Does Front-End Checklist have an API?

Yes. APIs.io lists 2 APIs from Front-End Checklist, including Front-End Checklist MCP and Front-End Checklist API.

Is there an OpenAPI specification for the Front-End Checklist API?

Yes. APIs.io indexes 1 OpenAPI specification for Front-End Checklist, each linked for download from this page.

Does Front-End Checklist have an MCP server?

Yes. APIs.io lists 1 MCP server for Front-End Checklist: Remote MCP server at mcp.frontendchecklist.io.

Is the Front-End Checklist API ready for AI agents?

Front-End Checklist has a Kin Score of 22.2 out of 100 (emerging) and an Agent Readiness score of 19.9 (agent-aware), 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/frontendchecklist-io"

All providers

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

Every operation they expose

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

How their score was established

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