x402 List API · API Governance Rules

x402 List API API Rules

Spectral linting rules defining API design standards and conventions for x402 List API.

5 Rules error 3 warn 2
View Rules File View on GitHub

Rule Categories

x402

Rules

error
x402-info-contact
The API info object must declare a contact.
$.info
error
x402-info-license
The API info object must declare a license.
$.info
warn
x402-info-terms-of-service
The API info object should declare termsOfService.
$.info
error
x402-servers-defined
The document must declare at least one server.
$
warn
x402-operation-description
Every operation should have a description.
$.paths[*][get,post,put,patch,delete]

Spectral Ruleset

Raw ↑
# Spectral governance ruleset for the x402 List OpenAPI document.
#
# Referenced from /.well-known/apis.json (rules[].type = SpectralRules) as the machine-readable
# governance artifact for apis.io readiness, and used by CI. This served copy is the single source
# of truth; the project-root .spectral.yaml simply extends it so `spectral lint` auto-discovers it.
#
# Lint the live contract with:
#   npx @stoplight/spectral-cli lint https://x402-list.com/api/v1/openapi.json
extends:
  - "spectral:oas"
rules:
  # An agent-facing contract must name a contact, a license, and its terms of service.
  x402-info-contact:
    description: The API info object must declare a contact.
    given: "$.info"
    severity: error
    then:
      field: contact
      function: truthy
  x402-info-license:
    description: The API info object must declare a license.
    given: "$.info"
    severity: error
    then:
      field: license
      function: truthy
  x402-info-terms-of-service:
    description: The API info object should declare termsOfService.
    given: "$.info"
    severity: warn
    then:
      field: termsOfService
      function: truthy
  # The document must declare at least one server so an agent knows where to call.
  x402-servers-defined:
    description: The document must declare at least one server.
    given: "$"
    severity: error
    then:
      field: servers
      function: truthy
  # Every operation should carry a description an agent can read.
  x402-operation-description:
    description: Every operation should have a description.
    given: "$.paths[*][get,post,put,patch,delete]"
    severity: warn
    then:
      field: description
      function: truthy

Work with this as data

Every ruleset 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 spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset in the catalog.
  • 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 ruleset
curl "https://apis.io/api/v1/rules/x402-list-api-spectral"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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