Internet Engineering Task Force API Rules

aid: internet-engineering-task-force
name: Internet Engineering Task Force Rules
description: >-
  Validation, governance, and operational rules applied to the IETF APIs.json
  index and any associated machine-readable artifacts.
type: standard
profile:
  - apis.json
governance:
  source: api-evangelist
  steward: Kin Lane
  visibility: public
rules:
  - id: apisjson-required-fields
    description: APIs.json must include aid, name, description, url, created, modified, and maintainers.
    severity: error
  - id: apisjson-tags-upper-case
    description: All tags must use upper-case first letters.
    severity: warn
  - id: api-baseurl-required
    description: Each documented API should declare a baseURL when known.
    severity: warn
  - id: openapi-non-empty
    description: OpenAPI specs must reference real, validated endpoints. Stub or empty specs are not permitted.
    severity: error
  - id: artifact-location
    description: All OpenAPI specs live under openapi/{repo}-openapi.yml.
    severity: error
  - id: datatracker-readonly
    description: Datatracker public endpoints are read-only. Consumers should expect JSON or XML responses and respect rate limits.
    severity: info