ARD entry validity

Every ARD entry must carry a domain-anchored urn:air identifier, a display name, a media type, and exactly one of url or data.

Standard
Emerging checkEmerging
Off by default, turn on in settings

Who supports it

No agent or browser has announced support yet.

27 others: no evidence yet. See every agent and browser

What it checks

For each entry in the site’s ARD catalog, the extension checks the four terms the specification requires:

  • an identifier that starts with urn:air: and whose publisher segment (the first part after urn:air:) is the domain being scanned,
  • a non-empty displayName,
  • a type that looks like a media type (it contains a /), and
  • exactly one of url or data, never both and never neither.

The domain anchoring matters because it is what lets a registry tie an entry to whoever served it.

Results

Status When
Pass Every entry carries all the required terms
Warn One or more entries are missing required terms (up to four are listed as evidence)
Warn The catalog is published but lists no entries
N/A There is no ARD catalog, or it could not be read

How to fix

Fix each entry named in the evidence. A valid entry for example.com:

{
  "identifier": "urn:air:example.com:api:orders",
  "displayName": "Orders API",
  "type": "application/openapi+json",
  "url": "https://example.com/openapi.json"
}

Use data instead of url only when you embed the resource’s description inline, and never set both.

Support by agent and browser

Announced means the vendor’s own docs or announcement say so. Published is the date on the vendor’s own page, where it has one. Checked is the last time our weekly research found that page still saying so.

No agent or browser has announced anything about this yet.

No evidence yet27
  • ChatGPT
  • Claude
  • Gemini
  • Perplexity
  • Copilot
  • Meta AI
  • ChatGPT Atlas
  • Comet
  • Dia
  • Gemini in Chrome
  • Edge Copilot Mode
  • Claude Code
  • Cursor
  • Codex
  • GitHub Copilot
  • Windsurf
  • CCBot
  • Applebot
  • Amazonbot
  • Bytespider
  • Cohere
  • Mistral
  • DuckAssist
  • Chrome
  • Edge
  • Firefox
  • Safari

Adoption on the top 100 sites

1 of 100 measured sites implement it

Scanned 23 Oct 2026 with the Sitebulb Labs extension, against the Tranco list (tranco-56Z8N).

9 Oct 2026: 1%12 Oct 2026: 1%23 Oct 2026: 1%
9 Oct 2026 1% → 23 Oct 2026 1%
Sites implementing it1
  1. #32 github.com (with warnings)

Overview

1/9

Stalled

No meaningful support, or vendors have said no.

How this rating is worked out1 of 9 points
FactorPointsWhy
Vendor support0 / 30 vendors supporting, 0 partly or planned
Top-100 adoption1 / 31% of measured sites
Spec maturity0 / 3Community proposal

8 or more points is Established, 5 to 7 is Gaining traction, 2 to 4 is Speculative and under 2 is Stalled. A feature is also Stalled when more vendors have said no than yes. Read the spec.

Community insights

No community insights for this feature yet.

Quotes are from public posts, checked against the original before they appear here. Suggest an insight, or ask for yours to be removed.