[
 {
  "id": "2s",
  "org_id": "2s",
  "name": "2s",
  "url": "https://2s.io/.well-known/agents.json",
  "type": "origin",
  "implements": [
   "agents-json"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agents-json",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "2s",
    "role": "API publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://2s.io/.well-known/agents.json returns status 200 application/json. agentsJson is 0.1.0; info.title is \"2s API - Agent Flows\", version 1.0.0. It references five OpenAPI 3.1 group specs (search, patents, law, business, agent) and defines six flows: discover_endpoints_flow, web_grounded_answer_flow, screen_entity_sanctions_flow, lookup_company_flow, patent_prior_art_flow, and search_us_caselaw_flow.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://2s.io/.well-known/agents.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://2s.io/.well-known/agents.json",
  "note": "https://2s.io/.well-known/agents.json returns status 200 application/json. agentsJson is 0.1.0; info.title is \"2s API - Agent Flows\", version 1.0.0. It references five OpenAPI 3.1 group specs (search, patents, law, business, agent) and defines six flows: discover_endpoints_flow, web_grounded_answer_flow, screen_entity_sanctions_flow, lookup_company_flow, patent_prior_art_flow, and search_us_casela"
 },
 {
  "id": "8004scan",
  "org_id": "altlayer",
  "name": "8004scan",
  "url": "https://8004scan.io/",
  "type": "authority",
  "implements": [
   "erc-8004"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "8004scan (AltLayer)",
    "role": "Explorer / Scanner",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Homepage covers identity, reputation, and validation across 29 chains.",
    "full_detail_md": "8004scan, whose page names Alt Research at altlayer.io, describes identity, reputation, and validation for trustless agents across 29 chains. The homepage probe returned HTTP 200 on 2026-10-30, which is the explorer site rather than a registry JSON record.",
    "facets": {
     "registry_or_contract": "Explorer index of ERC-8004 identity, reputation, and validation records, not an IdentityRegistry deployment",
     "chains_or_networks": "Homepage states coverage across 29 chains",
     "standards_profile": "ERC-8004 trustless-agent identity, reputation, and validation browser",
     "sdk_or_deployment": "Public website https://8004scan.io/ operated by Alt Research (altlayer.io)"
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "explorer"
    },
    "source_url": "https://8004scan.io/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://8004scan.io/",
  "note": "Homepage covers identity, reputation, and validation across 29 chains."
 },
 {
  "id": "a14y",
  "org_id": "a14y",
  "name": "a14y",
  "url": "https://a14y.dev/scorecards/",
  "type": "sdk",
  "implements": [
   "vercel-agent-readability"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "vercel-agent-readability",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "a14y",
    "role": "Validator / CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-06",
    "col4_md": "npx a14y and the Chrome extension score a site against the pinned checklist. v0.2.0 (2026-04-06) uses algorithm `flat-pool-v1` with 38 checks. The v0.3.0 draft switches to `per-check-mean-v1`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://a14y.dev/scorecards/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a14y.dev/scorecards/",
  "note": "npx a14y and the Chrome extension score a site against the pinned checklist. v0.2.0 (2026-04-06) uses algorithm `flat-pool-v1` with 38 checks. The v0.3.0 draft switches to `per-check-mean-v1`."
 },
 {
  "id": "a2a-cli",
  "org_id": "a2aproject",
  "name": "A2A CLI",
  "url": "https://a2a-protocol.org/oauth/a2a-cli.json",
  "type": "sdk",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "A2A CLI",
    "role": "Official CLI client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-11",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-11",
    "as_of": null,
    "col4_md": "Live OAuth Client ID Metadata Document (HTTP 200) names client A2A CLI (`client_id` `https://a2a-protocol.org/oauth/a2a-cli.json`, `client_uri` `https://github.com/a2aproject/a2a-cli`) with grants `authorization_code`, `refresh_token`, and `urn:ietf:params:oauth:grant-type:device_code`, and `token_endpoint_auth_method` `none`.",
    "full_detail_md": "The official A2A CLI publishes an OAuth Client ID Metadata Document at https://a2a-protocol.org/oauth/a2a-cli.json. The document sets client_name to A2A CLI, client_uri to https://github.com/a2aproject/a2a-cli, response_types to code, and token_endpoint_auth_method to none. grant_types lists authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:device_code. redirect_uris are loopback callbacks.",
    "facets": {
     "transport_bindings": "OAuth client metadata document; no Agent Card transport binding in this document",
     "discovery_artifact": "https://a2a-protocol.org/oauth/a2a-cli.json",
     "protocol_version": "Not stated in the client metadata document",
     "auth_schemes": "authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code; token_endpoint_auth_method none",
     "verification_posture": "Live client metadata document (HTTP 200)"
    },
    "telemetry": {
     "http_status": 200
    },
    "source_url": "https://a2a-protocol.org/oauth/a2a-cli.json"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "recorded",
  "source": "https://a2a-protocol.org/oauth/a2a-cli.json",
  "note": "Live OAuth Client ID Metadata Document (HTTP 200) names client A2A CLI (`client_id` `https://a2a-protocol.org/oauth/a2a-cli.json`, `client_uri` `https://github.com/a2aproject/a2a-cli`) with grants `authorization_code`, `refresh_token`, and `urn:ietf:params:oauth:grant-type:device_code`, and `token_endpoint_auth_method` `none`."
 },
 {
  "id": "a2a-official-sdks",
  "org_id": "a2aproject",
  "name": "Official A2A SDKs",
  "url": "https://a2a-protocol.org/latest/specification/",
  "type": "sdk",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Official A2A SDKs",
    "role": "Official client & server SDKs",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-28",
    "col4_md": "Proto-generated official client and server SDKs across six languages: `Python`, `Go`, `Java`, `JS`, `.NET`, and `Rust`.",
    "full_detail_md": "The canonical A2A specification mandates that SDK language bindings and derived schemas MUST be regenerated from the normative Protocol Buffers (`proto`) definition rather than edited manually, listing six official SDK languages (`Python`, `Go`, `Java`, `JS`, `.NET`, and `Rust`, following the five production-ready SDK languages—`Python`, `JavaScript`, `Java`, `Go`, and `.NET`—reported by the Linux Foundation on April 9, 2026); Microsoft Foundry documentation (updated 2026-10-28) likewise directs developers to build A2A servers serving `/.well-known/agent-card.json` using the official `Python`, `.NET`, or `JavaScript` A2A SDK.",
    "facets": {
     "transport_bindings": "JSONRPC, GRPC, and HTTP+JSON (regenerated from canonical proto)",
     "discovery_artifact": "Serves and consumes /.well-known/agent-card.json",
     "protocol_version": "1.0 (with v0.3 backward-compatibility noted in AAIF proposal)",
     "auth_schemes": "HTTP Bearer, API key, OAuth 2.0 (PKCE, Device Code RFC 8628), OpenID Connect, mTLS",
     "verification_posture": "Canonical specification requirement and official a2aproject GitHub repositories"
    },
    "telemetry": null,
    "source_url": "https://a2a-protocol.org/latest/specification/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2a-protocol.org/latest/specification/",
  "note": "Proto-generated official client and server SDKs across six languages: `Python`, `Go`, `Java`, `JS`, `.NET`, and `Rust`."
 },
 {
  "id": "a2a-slimrpc",
  "org_id": "a2a-slimrpc",
  "name": "a2a-slimrpc (A2A server bindings)",
  "url": "https://github.com/a2aproject/a2a-rs/tree/main/a2a-slimrpc",
  "type": "sdk",
  "implements": [
   "slim"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "slim",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "a2a-slimrpc (A2A server bindings)",
    "role": "Messaging node / Server",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-05-14",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05-14",
    "col4_md": "Crate a2aproject/a2a-rs/a2a-slimrpc: SLIMRPC bindings for A2A v1 server implementations. MLS is the SLIMRPC default and is what verifies the token (peer keys are set only for MLS sessions). SLIM docs call SLIMRPC a fourth, experimental A2A binding that uses the encrypted session layer instead of HTTP. a2aproject/experimental-cpb-slimrpc (created 2026-05-14) says it is not part of the core A2A specification.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/a2aproject/a2a-rs/tree/main/a2a-slimrpc"
   },
   {
    "protocol_id": "slim",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "a2a-slimrpc (A2A client bindings)",
    "role": "Client SDK / Runtime",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Same crate, a2a-rs/a2a-slimrpc: SLIMRPC bindings for A2A v1 clients. MLS is the default and verifies the token. experimental-cpb-slimrpc is marked Experimental and is not part of the core A2A specification. A2A's three standard bindings stay JSON-RPC, gRPC, and HTTP+JSON/REST.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/a2aproject/a2a-rs/tree/main/a2a-slimrpc"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/a2aproject/a2a-rs/tree/main/a2a-slimrpc",
  "note": "Crate a2aproject/a2a-rs/a2a-slimrpc: SLIMRPC bindings for A2A v1 server implementations. MLS is the SLIMRPC default and is what verifies the token (peer keys are set only for MLS sessions). SLIM docs call SLIMRPC a fourth, experimental A2A binding that uses the encrypted session layer instead of HTTP. a2aproject/experimental-cpb-slimrpc (created 2026-05-14) says it is not part of the core A2A spec"
 },
 {
  "id": "a2ui-android",
  "org_id": "a2ui-community",
  "name": "A2UI-Android",
  "url": "https://a2ui.org/reference/renderers",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "A2UI-Android",
    "role": "Community Jetpack Compose renderer",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Community Jetpack Compose renderer with 20+ components (`v0.8`).",
    "full_detail_md": "The A2UI renderers page lists A2UI-Android under ecosystem renderers as a community Jetpack Compose renderer with 20+ components on v0.8.",
    "facets": {
     "transport_or_binding": "A2UI messages rendered as Compose components",
     "component_or_catalog": "20+ community components",
     "spec_version": "v0.8",
     "sdk_or_renderer": "A2UI-Android"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/reference/renderers"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://a2ui.org/reference/renderers",
  "note": "Community Jetpack Compose renderer with 20+ components (`v0.8`)."
 },
 {
  "id": "a2ui-mcp-samples",
  "org_id": "google",
  "name": "A2UI over MCP samples",
  "url": "https://developers.googleblog.com/a2ui-and-mcp-apps/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "A2UI over MCP samples",
    "role": "Reference server",
    "status": "Partial",
    "status_display": "Partial · as of 2026-06-17",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-17",
    "col4_md": "Recipe Studio returns `application/a2ui+json` at `a2ui://dynamic-ui/recipe-card` via `resources/read` or `tools/call`.",
    "full_detail_md": "The June 17, 2026 post shows Recipe Studio returning an embedded resource with MIME type application/a2ui+json and URI a2ui://dynamic-ui/recipe-card, delivered by resources/read or tools/call, and says the authors are considering making a MCP extension to support A2UI. The same post describes a web-based Pong sample whose native A2UI score cards are rehydrated with the updated score, and a Document Editor that packages the A2UI rendering engine inside the MCP App bundle.",
    "facets": {
     "transport_or_binding": "MCP resources/read or tools/call; an MCP extension is still under consideration",
     "component_or_catalog": "application/a2ui+json at a2ui://dynamic-ui/recipe-card; Pong score cards; Document Editor bundles a renderer",
     "spec_version": "Example payload version v0.9 in the 2026-06-17 post",
     "sdk_or_renderer": "Recipe Studio, web-based Pong, and Document Editor samples"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/a2ui-and-mcp-apps/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.googleblog.com/a2ui-and-mcp-apps/",
  "note": "Recipe Studio returns `application/a2ui+json` at `a2ui://dynamic-ui/recipe-card` via `resources/read` or `tools/call`."
 },
 {
  "id": "a2ui-python-sdks",
  "org_id": "google",
  "name": "A2UI Python agent packages",
  "url": "https://github.com/a2ui-project/a2ui",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "A2UI Python agent packages",
    "role": "Agent SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-17",
    "col4_md": "Release snapshot publishes `python/a2ui-agent-sdk/v0.9.0`, `python/a2ui-core/v0.4.0`, `python/a2ui-adk/v0.1.0`, and `python/a2ui-a2a/v0.1.0`.",
    "full_detail_md": "GitHub Releases on 2026-10-17 published python/a2ui-agent-sdk/v0.9.0 (a2ui-agent-sdk 0.9.0), python/a2ui-core/v0.4.0, python/a2ui-adk/v0.1.0, and python/a2ui-a2a/v0.1.0, and the same list published cli-v0.1.0 (A2UI CLI v0.1.0) on 2026-10-30. The main README describes a2ui-agent-sdk as teaching the LLM a catalog and a2ui-core as protocol messages, data model, data binding, and catalog validation, but still says a2ui-a2a and a2ui-adk are Not published yet, unlike that release snapshot; tags v0.8 and v0.9 both point at commit 19919ef committed 2026-04-06, and there is no v0.9.1 tag, while the README calls v0.9.1 the current production release.",
    "facets": {
     "transport_or_binding": "a2ui-a2a connects the agent SDK to A2A; a2ui-adk connects it to ADK",
     "component_or_catalog": "a2ui-agent-sdk teaches an LLM catalog; a2ui-core validates catalogs and data binding",
     "spec_version": "Release snapshot 2026-10-17 (agent-sdk 0.9.0, core 0.4.0, adk 0.1.0, a2a 0.1.0); main README still says adk and a2a are Not published yet",
     "sdk_or_renderer": "python/a2ui-agent-sdk, python/a2ui-core, python/a2ui-adk, python/a2ui-a2a; cli-v0.1.0 published 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://api.github.com/repos/a2ui-project/a2ui/releases"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/repos/a2ui-project/a2ui/releases",
  "note": "Release snapshot publishes `python/a2ui-agent-sdk/v0.9.0`, `python/a2ui-core/v0.4.0`, `python/a2ui-adk/v0.1.0`, and `python/a2ui-a2a/v0.1.0`."
 },
 {
  "id": "a2ui-react-native",
  "org_id": "a2ui-community",
  "name": "a2ui-react-native",
  "url": "https://a2ui.org/reference/renderers",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "a2ui-react-native",
    "role": "Community React Native renderer",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Community React Native renderer for iOS/Android (`v0.8`).",
    "full_detail_md": "The A2UI renderers page lists a2ui-react-native as a React Native renderer for iOS and Android on v0.8.",
    "facets": {
     "transport_or_binding": "A2UI messages rendered in React Native",
     "component_or_catalog": "Community renderer",
     "spec_version": "v0.8",
     "sdk_or_renderer": "a2ui-react-native"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/reference/renderers"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://a2ui.org/reference/renderers",
  "note": "Community React Native renderer for iOS/Android (`v0.8`)."
 },
 {
  "id": "a2ui-web-client-packages",
  "org_id": "a2ui",
  "name": "A2UI web client packages",
  "url": "https://a2ui.org/guides/client-setup",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "A2UI web client packages",
    "role": "Official web renderer packages",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Client-setup guide: `npm install @a2ui/lit @a2ui/web_core` and `npm install @a2ui/angular @a2ui/web_core`, with Lit element `<a2ui-surface>` on shared `@a2ui/web_core`.",
    "full_detail_md": "The published client-setup guide marks React, Lit, and Angular Stable on v0.8 and v0.9, and marks Jetpack Compose Planned Q2 2026. Web renderers share @a2ui/web_core for the message processor, state management, and data binding. Lit installs with @a2ui/lit and renders through the a2ui-surface element. Angular installs with @a2ui/angular. That status table is not the renderers-page matrix, which uses a v0.9.1 column and marks Jetpack Compose Alpha there.",
    "facets": {
     "transport_or_binding": "Web renderers on the shared @a2ui/web_core message processor",
     "component_or_catalog": "Lit <a2ui-surface> and replaceable Basic Catalog",
     "spec_version": "Published guide columns v0.8 and v0.9",
     "sdk_or_renderer": "@a2ui/lit, @a2ui/angular, @a2ui/web_core"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/guides/client-setup"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://a2ui.org/guides/client-setup",
  "note": "Client-setup guide: `npm install @a2ui/lit @a2ui/web_core` and `npm install @a2ui/angular @a2ui/web_core`, with Lit element `<a2ui-surface>` on shared `@a2ui/web_core`."
 },
 {
  "id": "a2ui-web-renderers",
  "org_id": "google",
  "name": "A2UI web renderers",
  "url": "https://a2ui.org/roadmap/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Official web renderers",
    "role": "Web renderer",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-17",
    "col4_md": "Roadmap marks Web Core, Lit, Angular, and React Stable; the v0.9 post landed the React renderer.",
    "full_detail_md": "The roadmap marks Web Core (shared core library for web renderers), Web Components (Lit, framework-agnostic), Angular (full integration), and React (official React renderer) Stable. The April 17, 2026 v0.9 post says the official React renderer landed and that Flutter, Lit, Angular, and React were version-bumped.",
    "facets": {
     "transport_or_binding": "Client renderers for the A2UI JSON message stream",
     "component_or_catalog": "Web Core shared library; Lit, Angular, and React catalog renderers",
     "spec_version": "Roadmap Stable; v0.9 post 2026-04-17 version-bumped Flutter, Lit, Angular, and React",
     "sdk_or_renderer": "Web Core, Web Components (Lit), Angular, and the official React renderer"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/roadmap/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2ui.org/roadmap/",
  "note": "Roadmap marks Web Core, Lit, Angular, and React Stable; the v0.9 post landed the React renderer."
 },
 {
  "id": "aao-registry",
  "org_id": "agenticadvertising",
  "name": "AgenticAdvertising.org registry",
  "url": "https://agenticadvertising.org/api/registry/stats",
  "type": "authority",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AgenticAdvertising.org registry",
    "role": "Directory/registry (discovery)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200 from `https://agenticadvertising.org/api/registry/stats`. The body reports `registered_agents` 33, `registered_publishers` 14, `discovered_agents` 87, `discovered_publishers` 450, `discovered_properties` 22705, and `authorizations` 7742. `authorizations_by_source` splits `adagents_json` 7314 and `agent_claim` 428. `properties_by_type` includes `website` 19544, `podcast` 2081, `radio` 966, and `ctv_app` 64. The AAO Directory API page states that this endpoint is discovery, not authorization. The HTTP 200 stats response is declared registry presence, not conformance or live trading.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "registered_agents": 33,
     "registered_publishers": 14,
     "discovered_agents": 87,
     "discovered_publishers": 450,
     "discovered_properties": 22705,
     "authorizations": 7742,
     "adagents_json": 7314,
     "agent_claim": 428
    },
    "source_url": "https://agenticadvertising.org/api/registry/stats"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://agenticadvertising.org/api/registry/stats",
  "note": "HTTP 200 from `https://agenticadvertising.org/api/registry/stats`. The body reports `registered_agents` 33, `registered_publishers` 14, `discovered_agents` 87, `discovered_publishers` 450, `discovered_properties` 22705, and `authorizations` 7742. `authorizations_by_source` splits `adagents_json` 7314 and `agent_claim` 428. `properties_by_type` includes `website` 19544, `podcast` 2081, `radio` 966,"
 },
 {
  "id": "acceptmarkdown-scanner",
  "org_id": "acceptmarkdown",
  "name": "AcceptMarkdown scanner",
  "url": "https://acceptmarkdown.com/",
  "type": "authority",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "AcceptMarkdown scanner",
    "role": "Negotiation checker",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Checks `Accept: text/markdown`, `Vary: Accept`, status `406`, and `q` values.",
    "full_detail_md": "The AcceptMarkdown checker scores whether a URL serves Markdown for Accept: text/markdown, sets Vary: Accept, rejects an unsupported type with 406, and honors q-values. The page does not publish a site-wide pass rate.",
    "facets": {
     "negotiation_or_artifact": "Four-check scanner for Accept, Vary, 406, and q-values",
     "response_headers": "Reports the origin response; does not publish a web-wide pass rate",
     "content_type_or_tokens": "Edge request with Accept: text/markdown",
     "verification_posture": "Checker description fetched 2026-11-06"
    },
    "telemetry": null,
    "source_url": "https://acceptmarkdown.com/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://acceptmarkdown.com/",
  "note": "Checks `Accept: text/markdown`, `Vary: Accept`, status `406`, and `q` values."
 },
 {
  "id": "acp-discovery-retailers",
  "org_id": "acp-discovery-retailers",
  "name": "Target, Sephora, Nordstrom, Lowe's, Best Buy, The Home Depot, and Wayfair",
  "url": "https://web.archive.org/web/20261012013103/https://openai.com/index/powering-product-discovery-in-chatgpt/",
  "type": "origin",
  "implements": [
   "agentic-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Target, Sephora, Nordstrom, Lowe's, Best Buy, The Home Depot, and Wayfair",
    "role": "Merchant cohort",
    "status": "Partial",
    "status_display": "Partial · as of 2026-03-24",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-24",
    "col4_md": "Discovery only, not checkout, for Target, Sephora, Nordstrom, Lowe's, Best Buy, The Home Depot, and Wayfair.",
    "full_detail_md": "On March 24, 2026 OpenAI said leading retailers including Target, Sephora, Nordstrom, Lowe's, Best Buy, The Home Depot, and Wayfair have integrated into ACP for discovery. That sentence is a discovery integration. It does not describe a Shared Payment Token checkout for this cohort.",
    "facets": {
     "commerce_role_or_surface": "Retailer product discovery inside ChatGPT",
     "payment_or_token_rail": "No Shared Payment Token checkout described for this cohort",
     "api_or_spec_version": "ACP discovery integration, not checkout settlement",
     "availability_or_eligibility_posture": "OpenAI statement of March 24, 2026; discovery only"
    },
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20261012013103/https://openai.com/index/powering-product-discovery-in-chatgpt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://web.archive.org/web/20261012013103/https://openai.com/index/powering-product-discovery-in-chatgpt/",
  "note": "Discovery only, not checkout, for Target, Sephora, Nordstrom, Lowe's, Best Buy, The Home Depot, and Wayfair."
 },
 {
  "id": "adcp-client",
  "org_id": "adcontextprotocol",
  "name": "@adcp/client",
  "url": "https://www.npmjs.com/package/@adcp/client",
  "type": "sdk",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "@adcp/client",
    "role": "Client SDK",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The npm record marks `@adcp/client` `deprecated`: Renamed to `@adcp/sdk` in `v6.0`. Install `@adcp/sdk@^6.1.0` instead.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@adcp/client"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@adcp/client",
  "note": "The npm record marks `@adcp/client` `deprecated`: Renamed to `@adcp/sdk` in `v6.0`. Install `@adcp/sdk@^6.1.0` instead."
 },
 {
  "id": "adcp-go",
  "org_id": "adcontextprotocol",
  "name": "adcp-go",
  "url": "https://github.com/adcontextprotocol/adcp-go",
  "type": "sdk",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "adcp-go",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "GitHub describes adcontextprotocol/adcp-go as the Golang SDK for the AdCP protocol, licensed under `Apache-2.0` and last pushed on 2026-10-30. The 3.2.8 introduction install line ends with `go get github.com/adcontextprotocol/adcp-go/adcp`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/repos/adcontextprotocol/adcp-go"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/repos/adcontextprotocol/adcp-go",
  "note": "GitHub describes adcontextprotocol/adcp-go as the Golang SDK for the AdCP protocol, licensed under `Apache-2.0` and last pushed on 2026-10-30. The 3.2.8 introduction install line ends with `go get github.com/adcontextprotocol/adcp-go/adcp`."
 },
 {
  "id": "adcp-python",
  "org_id": "adcontextprotocol",
  "name": "adcp Python SDK",
  "url": "https://pypi.org/project/adcp/",
  "type": "sdk",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "adcp Python SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "PyPI `adcp` version `9.3.1` was uploaded on 2026-10-29. The summary is Official Python client for the Ad Context Protocol (AdCP). The packaged README names `ADCPClient` and `ADCPHandler`. The 3.2.8 introduction install line includes `pip install adcp`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/adcp/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/adcp/json",
  "note": "PyPI `adcp` version `9.3.1` was uploaded on 2026-10-29. The summary is Official Python client for the Ad Context Protocol (AdCP). The packaged README names `ADCPClient` and `ADCPHandler`. The 3.2.8 introduction install line includes `pip install adcp`."
 },
 {
  "id": "adcp-sdk",
  "org_id": "adcontextprotocol",
  "name": "@adcp/sdk",
  "url": "https://www.npmjs.com/package/@adcp/sdk",
  "type": "sdk",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "@adcp/sdk",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "npm dist-tag `latest` is `16.6.1`, published 2026-10-29. The package description is AdCP SDK - client, server, and compliance harnesses for the AdContext Protocol (`MCP` + `A2A`). The 3.2.8 introduction install line begins `npm install @adcp/sdk`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@adcp/sdk"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@adcp/sdk",
  "note": "npm dist-tag `latest` is `16.6.1`, published 2026-10-29. The package description is AdCP SDK - client, server, and compliance harnesses for the AdContext Protocol (`MCP` + `A2A`). The 3.2.8 introduction install line begins `npm install @adcp/sdk`."
 },
 {
  "id": "addie",
  "org_id": "agenticadvertising",
  "name": "Addie",
  "url": "https://docs.adcontextprotocol.org/dist/docs/3.2.8/intro",
  "type": "harness",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Addie",
    "role": "Testing assistant",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The 3.2.8 introduction tells builders to ask Addie to ask questions about AdCP, explore the protocol, and test tasks, with no code required.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.adcontextprotocol.org/dist/docs/3.2.8/intro"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.adcontextprotocol.org/dist/docs/3.2.8/intro",
  "note": "The 3.2.8 introduction tells builders to ask Addie to ask questions about AdCP, explore the protocol, and test tasks, with no code required."
 },
 {
  "id": "adk-web",
  "org_id": "google",
  "name": "ADK Web",
  "url": "https://a2ui.org/ecosystem/a2ui-in-the-world/",
  "type": "harness",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "ADK Web",
    "role": "Developer UI",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "ADK Web renders the `v0.8` basic catalog and converts A2UI between A2A DataPart metadata and ADK events.",
    "full_detail_md": "The ecosystem page says the built-in developer UI, ADK Web, includes native A2UI rendering, and that ADK integrated the A2UI v0.8 basic catalog to render spec-compliant agent parts as native UI components in the chat. A2UI messages are converted between A2A DataPart metadata and ADK events.",
    "facets": {
     "transport_or_binding": "A2A DataPart metadata converted to ADK events",
     "component_or_catalog": "A2UI v0.8 basic catalog rendered as native chat components",
     "spec_version": "v0.8 basic catalog",
     "sdk_or_renderer": "ADK Web developer UI"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/ecosystem/a2ui-in-the-world/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://a2ui.org/ecosystem/a2ui-in-the-world/",
  "note": "ADK Web renders the `v0.8` basic catalog and converts A2UI between A2A DataPart metadata and ADK events."
 },
 {
  "id": "adobe",
  "org_id": "adobe",
  "name": "Adobe",
  "url": "https://blog.adobe.com/en/publish/2025/12/10/edit-photoshop-chatgpt",
  "type": "origin",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Adobe",
    "role": "ChatGPT app",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Photoshop editing in ChatGPT, plus Acrobat and Express for photos, designs, and PDFs.",
    "full_detail_md": "Adobe's post says people can edit with Photoshop directly in ChatGPT. Adobe Acrobat and Adobe Express are also available in ChatGPT, for photos, designs, and PDFs.",
    "facets": {
     "transport_or_manifest": "Vendor blog announcement; no plugin.json cited on this row",
     "ui_or_widget_surface": "Photoshop, Acrobat, and Express surfaces inside ChatGPT",
     "auth_or_permissions": "No permission model named in the cited Adobe post",
     "sdk_or_version": "Photoshop, Acrobat, and Express described as available in ChatGPT"
    },
    "telemetry": null,
    "source_url": "https://blog.adobe.com/en/publish/2025/12/10/edit-photoshop-chatgpt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://blog.adobe.com/en/publish/2025/12/10/edit-photoshop-chatgpt",
  "note": "Photoshop editing in ChatGPT, plus Acrobat and Express for photos, designs, and PDFs."
 },
 {
  "id": "adyen",
  "org_id": "adyen",
  "name": "Adyen",
  "url": "https://www.adyen.com",
  "type": "venue",
  "implements": [
   "agentic-commerce-protocol",
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Adyen",
    "role": "Payment rail",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-16",
    "col4_md": "ACP checkout delegates the payment token to Adyen (`adyen` provider enum, 2026-01-16).",
    "full_detail_md": "Adyen's docs say to delegate payments to Adyen from an agent platform in the ACP checkout flow, and that the merchant uses the token to process the payment with Adyen. The 2026-01-16 changelog added adyen to the provider enum for both PaymentProvider and AuthenticationProvider.",
    "facets": {
     "commerce_role_or_surface": "ACP checkout payment provider",
     "payment_or_token_rail": "Delegated payment token processed by the merchant with Adyen",
     "api_or_spec_version": "Provider enum value adyen on PaymentProvider and AuthenticationProvider (changelog 2026-01-16)",
     "availability_or_eligibility_posture": "Documented delegation from an agent platform in the ACP checkout flow"
    },
    "telemetry": null,
    "source_url": "https://docs.adyen.com/online-payments/agentic-commerce/agent-platform/agentic-payments-acp"
   },
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Adyen",
    "role": "Payment processor",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-02",
    "col4_md": "Agentic API transacts with Adyen merchants; sessions require RFC 9421.",
    "full_detail_md": "The Adyen Agentic API lets an AI agent platform transact with Adyen merchants using the Universal Commerce Protocol, and session operations also require UCP HTTP Message Signatures (RFC 9421). September 2, 2026: Adyen NV is an inaugural member of the Payments Technical Council, and MAINTAINERS.md lists Jose Mendez (Adyen NV).",
    "facets": {
     "commerce_surface": "Adyen Agentic API for AI agent platforms",
     "payment_handlers_or_rail": "UCP transactions with Adyen merchants; session operations require RFC 9421 HTTP Message Signatures",
     "transport_bindings": "Documented agent-platform integration, not a probed merchant profile",
     "spec_version": "Payments Technical Council inaugural member as of September 2, 2026"
    },
    "telemetry": null,
    "source_url": "https://docs.adyen.com/online-payments/agentic-commerce/agent-platform/ai-agent-integration-ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.adyen.com/online-payments/agentic-commerce/agent-platform/agentic-payments-acp",
  "note": "ACP checkout delegates the payment token to Adyen (`adyen` provider enum, 2026-01-16)."
 },
 {
  "id": "adyen-ucp",
  "org_id": "adyen",
  "name": "Adyen UCP",
  "url": "https://docs.adyen.com/online-payments/agentic-commerce/agent-platform/ai-agent-integration-ucp",
  "type": "authority",
  "implements": [
   "http-message-signatures"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Adyen",
    "role": "Commerce verifier (UCP profile)",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Requires UCP profile of RFC 9421 (`Signature`, `Signature-Input`, `UCP-Agent`, and `Content-Digest`) on checkout session operations.",
    "full_detail_md": "Adyen's Agentic API requires UCP HTTP Message Signatures (RFC 9421) alongside Bearer API key authentication on checkout session operations for request integrity and origin verification, checking `Signature`, `Signature-Input` (covered components, algorithm, key ID), `UCP-Agent`, and SHA-256 `Content-Digest` on `POST` and `PUT` requests.",
    "facets": {
     "profile_or_spec_target": "Universal Commerce Protocol (UCP) profile of RFC 9421",
     "signature_fields": "`Signature`, `Signature-Input`, `UCP-Agent`, and `Content-Digest` (required on `POST` and `PUT`)",
     "algorithms_or_keys": "Key ID and algorithm declared in `Signature-Input` paired with `UCP-Agent` profile URL",
     "verification_posture": "Commerce API verifier (Adyen Agentic API checkout session operations)"
    },
    "telemetry": null,
    "source_url": "https://docs.adyen.com/online-payments/agentic-commerce/agent-platform/ai-agent-integration-ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.adyen.com/online-payments/agentic-commerce/agent-platform/ai-agent-integration-ucp",
  "note": "Requires UCP profile of RFC 9421 (`Signature`, `Signature-Input`, `UCP-Agent`, and `Content-Digest`) on checkout session operations."
 },
 {
  "id": "ag-ui-channels",
  "org_id": "copilotkit",
  "name": "AG-UI Channels SDK",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "AG-UI Channels SDK (OpenTag)",
    "role": "Chat client",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`OpenTag` serves a Python LangGraph agent over AG-UI into Slack and Microsoft Teams.",
    "full_detail_md": "The overview lists chat platforms (Slack, Microsoft Teams) as Supported, and describes the Channels SDK as one implementation of that client shape. `OpenTag` is a complete application built on it: a Python LangGraph agent served over AG-UI into Slack and Microsoft Teams, with the agent and its runtime self-hosted while platform credentials and message delivery are handled by CopilotKit Intelligence, a hosted service that is not part of the protocol.",
    "facets": {
     "transport": "AG-UI event stream into Slack and Microsoft Teams",
     "event_or_state_model": "Python LangGraph agent served as an AG-UI event stream",
     "integration_role": "Chat-platform client application",
     "sdk_or_package": "AG-UI Channels SDK; OpenTag application"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "`OpenTag` serves a Python LangGraph agent over AG-UI into Slack and Microsoft Teams."
 },
 {
  "id": "ag-ui-core",
  "org_id": "ag-ui",
  "name": "@ag-ui/core",
  "url": "https://registry.npmjs.org/@ag-ui/core",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "@ag-ui/core",
    "role": "TypeScript SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-16",
    "col4_md": "npm `@ag-ui/core` latest `1.0.3` sets `protocolVersion` to `1.0`.",
    "full_detail_md": "The npm registry record for `@ag-ui/core` latest `1.0.3` is timestamped 2026-10-16T08:40:38.297Z, describes TypeScript definitions and runtime schemas for AG-UI, and sets `protocolVersion` to `1.0`. The AG-UI 1.0 post on 2026-09-30 says the TypeScript, Python, and .NET SDKs are now generated from the JSON Schema. This row is package-registry metadata, not a live agent endpoint.",
    "facets": {
     "transport": "Not a run transport; npm package metadata",
     "event_or_state_model": "protocolVersion 1.0 runtime schemas",
     "integration_role": "TypeScript protocol SDK",
     "sdk_or_package": "@ag-ui/core 1.0.3"
    },
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@ag-ui/core"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@ag-ui/core",
  "note": "npm `@ag-ui/core` latest `1.0.3` sets `protocolVersion` to `1.0`."
 },
 {
  "id": "ag-ui-dotnet",
  "org_id": "microsoft",
  "name": "AG-UI .NET SDK",
  "url": "https://devblogs.microsoft.com/dotnet/ag-ui-dotnet-sdk/",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "AG-UI .NET SDK",
    "role": "Client and server SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-25",
    "col4_md": "`AGUI.Server` exposes an endpoint and `AGUI.Client` consumes one; published on NuGet.",
    "full_detail_md": "The September 25th, 2026 post says the .NET team contributed a .NET SDK for AG-UI with CopilotKit, published on NuGet under the MIT license. `AGUI.Server` turns an agent into an AG-UI endpoint, `AGUI.Client` lets a .NET application consume one, and the overview lists .NET as Supported under SDKs.",
    "facets": {
     "transport": "AG-UI endpoint (binding not further named on the post)",
     "event_or_state_model": "AG-UI endpoint produced by AGUI.Server and consumed by AGUI.Client",
     "integration_role": "Client and server SDK",
     "sdk_or_package": "AGUI.Server and AGUI.Client on NuGet (MIT)"
    },
    "telemetry": null,
    "source_url": "https://devblogs.microsoft.com/dotnet/ag-ui-dotnet-sdk/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://devblogs.microsoft.com/dotnet/ag-ui-dotnet-sdk/",
  "note": "`AGUI.Server` exposes an endpoint and `AGUI.Client` consumes one; published on NuGet."
 },
 {
  "id": "ag-ui-protocol",
  "org_id": "ag-ui",
  "name": "ag-ui-protocol",
  "url": "https://pypi.org/pypi/ag-ui-protocol/json",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "ag-ui-protocol",
    "role": "Python SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-17",
    "col4_md": "PyPI `ag-ui-protocol` `1.0.0` requires Python `>=3.9` and `pydantic>=2.11.2`.",
    "full_detail_md": "PyPI `ag-ui-protocol` `1.0.0` is described as a Python SDK for the Agent-User Interaction (AG-UI) Protocol, with `requires_python` `>=3.9` and `pydantic>=2.11.2`, and the 1.0.0 upload time is 2026-09-17T18:31:18. The 1.0 post says the TypeScript, Python, and .NET SDKs are generated from the schema. This row is package-registry metadata, not a live agent endpoint.",
    "facets": {
     "transport": "Not a run transport; PyPI package metadata",
     "event_or_state_model": "Python SDK generated from the AG-UI 1.0 schema",
     "integration_role": "Python protocol SDK",
     "sdk_or_package": "ag-ui-protocol 1.0.0 (Python >=3.9, pydantic>=2.11.2)"
    },
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/ag-ui-protocol/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/ag-ui-protocol/json",
  "note": "PyPI `ag-ui-protocol` `1.0.0` requires Python `>=3.9` and `pydantic>=2.11.2`."
 },
 {
  "id": "ag2",
  "org_id": "ag2",
  "name": "AG2",
  "url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "type": "sdk",
  "implements": [
   "a2a",
   "ag-ui",
   "nlip",
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry",
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AG2",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-27",
    "col4_md": "A2A blog and AAIF proposal list `AG2` (formerly `AutoGen`) agent swarm connections tagged with `a2a`.",
    "full_detail_md": "The A2A project blog (2026-08-27) names `AG2` among supporting frameworks, and the AAIF Growth Stage proposal (#37) states that `AG2` (formerly `AutoGen`) exposes and connects agent swarms over A2A with `a2a` tagged as a core capability on its repository.",
    "facets": {
     "transport_bindings": "Inter-agent swarm connection over A2A (reported in AAIF proposal)",
     "discovery_artifact": "Not specified in AAIF proposal",
     "protocol_version": "Not specified in AAIF proposal (2026-08-27 blog / proposal #37)",
     "auth_schemes": "Not specified in AAIF proposal",
     "verification_posture": "Listed in A2A blog (2026-08-27) and AAIF proposal #37"
    },
    "telemetry": null,
    "source_url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AG2",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists AG2 as Supported under Agent Framework - 1st Party, with Docs and Demos.",
    "full_detail_md": "The AG-UI overview lists AG2 as Supported under Agent Framework - 1st Party, with Docs and Demos. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "1st-party agent framework (directory listing)",
     "sdk_or_package": "Not named; Docs and Demos only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   },
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "AG2",
    "role": "Agent framework",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-06-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-30",
    "col4_md": "Pull request 2468, `feat: add NLIP integration`, merged on 2026-04-08. It defines `NlipRemoteAgent`, which turns a remote NLIP server into a `ConversableAgent`, and `NlipAgentServer`, which exposes existing AG2 agents as NLIP servers. Pull request 3024, `feat: add NLIP integration for beta`, merged on 2026-06-30. It defines `NlipConfig`, a `ModelConfig` for a remote NLIP server, and `NlipServer`, a standards-compliant NLIP endpoint, under `autogen.beta.extensions.nlip` as an opt-in extension.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/repos/ag2ai/ag2/pulls/2468"
   },
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "AG2",
    "role": "GenAI span middleware",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "AG2 middleware follows the OpenTelemetry GenAI semantic conventions. `gen_ai.operation.name` includes `invoke_agent`, `chat`, `execute_tool`, and `await_human_input`. Tool spans carry `gen_ai.tool.name`, `gen_ai.tool.call.id`, and `gen_ai.tool.type`. Named backends include Jaeger, Grafana Tempo, Datadog, Honeycomb, Langfuse, Arize AX, and Arize Phoenix.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.ag2.ai/docs/user-guide/telemetry/agent/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "note": "A2A blog and AAIF proposal list `AG2` (formerly `AutoGen`) agent swarm connections tagged with `a2a`."
 },
 {
  "id": "ag2-a2ui-agent",
  "org_id": "ag2",
  "name": "AG2 A2UIAgent",
  "url": "https://docs.ag2.ai/latest/docs/blog/2026/03/20/AG2-A2UI/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AG2 A2UIAgent",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-20",
    "col4_md": "`A2UIAgent` extends `ConversableAgent` over AG-UI and A2A; roadmap marks AG2 Complete.",
    "full_detail_md": "AG2's March 20, 2026 post says A2UIAgent extends ConversableAgent with prompt engineering, response parsing, schema validation with retry, and action handling, and that it works with both AG-UI (streaming) and A2A out of the box. The ecosystem page says the same agent serves the UI over A2A (JSON-RPC) and AG-UI (SSE), and the roadmap marks AG2 Complete for A2UIAgent.",
    "facets": {
     "transport_or_binding": "A2A (JSON-RPC) and AG-UI (SSE / streaming)",
     "component_or_catalog": "System prompt includes the A2UI component catalog; custom catalogs supported",
     "spec_version": "A2UIAgent; roadmap status Complete; post dated 2026-03-20",
     "sdk_or_renderer": "AG2 A2UIAgent extending ConversableAgent"
    },
    "telemetry": null,
    "source_url": "https://docs.ag2.ai/latest/docs/blog/2026/03/20/AG2-A2UI/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.ag2.ai/latest/docs/blog/2026/03/20/AG2-A2UI/",
  "note": "`A2UIAgent` extends `ConversableAgent` over AG-UI and A2A; roadmap marks AG2 Complete."
 },
 {
  "id": "agent-community",
  "org_id": "agent-community",
  "name": "Agent Community",
  "url": "https://agentcommunity.org/ask?query=What%20is%20AID%3F",
  "type": "origin",
  "implements": [
   "nlweb"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlweb",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Agent Community",
    "role": "NLWeb site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GET `https://agentcommunity.org/ask?query=What%20is%20AID%3F` returned status 200 JSON with `query_id` and a `results` list of Schema.org `Article` items (`url`, `name`, `site`, `score`). Docs say `/ask` is extractive retrieval over published documentation and does not call an LLM.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agentcommunity.org/ask?query=What%20is%20AID%3F"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://agentcommunity.org/ask?query=What%20is%20AID%3F",
  "note": "GET `https://agentcommunity.org/ask?query=What%20is%20AID%3F` returned status 200 JSON with `query_id` and a `results` list of Schema.org `Article` items (`url`, `name`, `site`, `score`). Docs say `/ask` is extractive retrieval over published documentation and does not call an LLM."
 },
 {
  "id": "agent-console-aat-verify-mjs",
  "org_id": "agent-console-aat-verify-mjs",
  "name": "Agent Console aat-verify.mjs",
  "url": "https://raw.githubusercontent.com/cyl-castillo/agent-console/main/README.md",
  "type": "authority",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Agent Console aat-verify.mjs",
    "role": "Verifier / Audit parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Dependency-free Node verifier shipped beside Testigo. It checks the exported JSONL ledger offline. The ledger is SHA-256 over RFC 8785, conformant to draft-sharif-agent-audit-trail-08. The same README also describes a browser check of signed proof packets and a reproducible auditor zip.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/cyl-castillo/agent-console/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/cyl-castillo/agent-console/main/README.md",
  "note": "Dependency-free Node verifier shipped beside Testigo. It checks the exported JSONL ledger offline. The ledger is SHA-256 over RFC 8785, conformant to draft-sharif-agent-audit-trail-08. The same README also describes a browser check of signed proof packets and a reproducible auditor zip."
 },
 {
  "id": "agent-console-testigo",
  "org_id": "agent-console-testigo",
  "name": "Agent Console / Testigo",
  "url": "https://raw.githubusercontent.com/cyl-castillo/agent-console/main/README.md",
  "type": "sdk",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Agent Console / Testigo",
    "role": "Audit emitter",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Testigo (src-tauri/src/services/aat_export.rs) exports every agent session as a draft-sharif-agent-audit-trail-08 JSONL file. The chain is SHA-256 over RFC 8785 canonical JSON. Appendix E of draft -09 lists this exporter. The same tree ships aat-verify.mjs for offline checks.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/cyl-castillo/agent-console/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/cyl-castillo/agent-console/main/README.md",
  "note": "Testigo (src-tauri/src/services/aat_export.rs) exports every agent session as a draft-sharif-agent-audit-trail-08 JSONL file. The chain is SHA-256 over RFC 8785 canonical JSON. Appendix E of draft -09 lists this exporter. The same tree ships aat-verify.mjs for offline checks."
 },
 {
  "id": "agent0-sdk",
  "org_id": "agent0lab",
  "name": "Agent0 SDK",
  "url": "https://raw.githubusercontent.com/agent0lab/agent0-ts/main/README.md",
  "type": "sdk",
  "implements": [
   "erc-8004"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Agent0 SDK",
    "role": "Verifier SDK / Runtime",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Main-branch TypeScript SDK `1.7.0` publishes MCP and A2A endpoints on ERC-8004.",
    "full_detail_md": "The Agent0 README on the main branch describes a TypeScript SDK, marked release 1.7.0 in that file, for agentic economies on ERC-8004 that publishes MCP and A2A endpoints, extracts tools and skills from those endpoints, advertises OASF taxonomies, and indexes on-chain and IPFS data with a subgraph. Support is Partial because the evidence is that unreleased main-branch README, not a tagged release artifact.",
    "facets": {
     "registry_or_contract": "Registers agents on ERC-8004 and indexes on-chain and IPFS data",
     "chains_or_networks": "Described as ERC-8004 blockchain infrastructure; the README lead does not name a chain id",
     "standards_profile": "ERC-8004 registration, MCP and A2A endpoint advertisement, and OASF taxonomies",
     "sdk_or_deployment": "TypeScript SDK release 1.7.0 noted on the main-branch README, with subgraph indexing"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agent0lab/agent0-ts/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/agent0lab/agent0-ts/main/README.md",
  "note": "Main-branch TypeScript SDK `1.7.0` publishes MCP and A2A endpoints on ERC-8004."
 },
 {
  "id": "agentavow",
  "org_id": "agentavow",
  "name": "AgentAvow",
  "url": "https://agentavow.com/.well-known/ai-catalog.json",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "AgentAvow",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Catalog at /.well-known/ai-catalog.json (Content-Type: application/ai-catalog+json, host did:web:agentavow.com); in the 2026-10-30 snapshot, extensions `com.agentavow.catalogBuild` self-declares status: \"signed\" with a catalog ES256 JWS (did:web:agentavow.com#catalog-es256-v1) and an independent-assessor trustManifest on github-mcp-server (assessor manifests alone do not make a third-party entry Level 3 Trusted).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agentavow.com/.well-known/ai-catalog.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://agentavow.com/.well-known/ai-catalog.json",
  "note": "Catalog at /.well-known/ai-catalog.json (Content-Type: application/ai-catalog+json, host did:web:agentavow.com); in the 2026-10-30 snapshot, extensions `com.agentavow.catalogBuild` self-declares status: \"signed\" with a catalog ES256 JWS (did:web:agentavow.com#catalog-es256-v1) and an independent-assessor trustManifest on github-mcp-server (assessor manifests alone do not make a third-party entry L"
 },
 {
  "id": "agentcommunity-aid",
  "org_id": "agentcommunity-aid",
  "name": "@agentcommunity/aid",
  "url": "https://registry.npmjs.org/@agentcommunity/aid",
  "type": "sdk",
  "implements": [
   "aid"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "aid",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "@agentcommunity/aid",
    "role": "Resolver / Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-25",
    "col4_md": "Node.js and browser discovery SDK on npm; latest 2.1.1 published 2026-07-25 (1.0.0 on 2025-07-12). Package page calls it the main discovery SDK for resolving an AID record",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@agentcommunity/aid"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@agentcommunity/aid",
  "note": "Node.js and browser discovery SDK on npm; latest 2.1.1 published 2026-07-25 (1.0.0 on 2025-07-12). Package page calls it the main discovery SDK for resolving an AID record"
 },
 {
  "id": "agentcommunity-aid-doctor",
  "org_id": "agentcommunity-aid-doctor",
  "name": "@agentcommunity/aid-doctor",
  "url": "https://registry.npmjs.org/@agentcommunity/aid-doctor",
  "type": "sdk",
  "implements": [
   "aid"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "aid",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "@agentcommunity/aid-doctor",
    "role": "CLI / Validator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-25",
    "col4_md": "npm CLI, latest 2.1.1 published 2026-07-25 (1.0.0 on 2025-07-12), for AID record generation, validation, diagnostics, and PKA helpers",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@agentcommunity/aid-doctor"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@agentcommunity/aid-doctor",
  "note": "npm CLI, latest 2.1.1 published 2026-07-25 (1.0.0 on 2025-07-12), for AID record generation, validation, diagnostics, and PKA helpers"
 },
 {
  "id": "agentic-direct",
  "org_id": "iab-tech-lab",
  "name": "Agentic Direct",
  "url": "https://github.com/IABTechLab/agentic-direct",
  "type": "sdk",
  "implements": [
   "aamp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "aamp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Agentic Direct",
    "role": "Reference orchestration server",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "The hub README calls Agentic Direct the core communication framework and orchestration layer for agent interaction. The repository README describes a schema-driven A2A and MCP implementation for OpenDirect v2.1. The MCP server layer returns mock responses. The A2A layer includes an Agent Card Generator (`v0.3.0`) and a JSON-RPC 2.0 router. The JavaScript client uses `@a2a-js/sdk`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/IABTechLab/agentic-direct/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/IABTechLab/agentic-direct/main/README.md",
  "note": "The hub README calls Agentic Direct the core communication framework and orchestration layer for agent interaction. The repository README describes a schema-driven A2A and MCP implementation for OpenDirect v2.1. The MCP server layer returns mock responses. The A2A layer includes an Agent Card Generator (`v0.3.0`) and a JSON-RPC 2.0 router. The JavaScript client uses `@a2a-js/sdk`."
 },
 {
  "id": "agenticskills-curated",
  "org_id": "agenticskills",
  "name": "AgenticSkills",
  "url": "https://agenticskills.io",
  "type": "authority",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AgenticSkills",
    "role": "Curated SKILL.md directory",
    "status": "Listed",
    "status_display": "Listed · as of 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-11-06",
    "col4_md": "Vendor-declared curated `v1.7.0` index: `195+` skills and `139` MCP servers.",
    "full_detail_md": "Index v1.7.0 dated NOV 6 2026 tracks 195+ curated skills, 139 MCP servers, and 9 platforms, with install paths such as ~/.claude/skills/ and .cursor/skills/.",
    "facets": {
     "transport_or_packaging": "Curated directory with per-platform install paths",
     "manifest_or_entry": "v1.7.0; 195+ skills; 139 MCP servers; 9 platforms",
     "execution_or_sandbox": "Install into the client skills folder",
     "verification_posture": "Index stamp NOV 6 2026"
    },
    "telemetry": null,
    "source_url": "https://agenticskills.io"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://agenticskills.io",
  "note": "Vendor-declared curated `v1.7.0` index: `195+` skills and `139` MCP servers."
 },
 {
  "id": "agentnameservice-verifier",
  "org_id": "agentnameservice-verifier",
  "name": "agentnameservice verifier",
  "url": "https://www.ietf.org/archive/id/draft-narajala-courtney-ansv2-02.txt",
  "type": "authority",
  "implements": [
   "ans"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "ans",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "agentnameservice verifier",
    "role": "Verifier SDK / Runtime",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "The ANS v2 draft says the open-source project includes a verifier beside the registry, transparency log, schemas, SDKs, and CLI. A verifier pins an agent to one log entry and one version. The badge it can fetch is a TXT record at `_ans-badge.{agentHost}` with `v=ans-badge1; version=v{version}; url={badgeURL}`. Identity certificates from the private CA are used for mTLS between agents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-narajala-courtney-ansv2-02.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.ietf.org/archive/id/draft-narajala-courtney-ansv2-02.txt",
  "note": "The ANS v2 draft says the open-source project includes a verifier beside the registry, transparency log, schemas, SDKs, and CLI. A verifier pins an agent to one log entry and one version. The badge it can fetch is a TXT record at `_ans-badge.{agentHost}` with `v=ans-badge1; version=v{version}; url={badgeURL}`. Identity certificates from the private CA are used for mTLS between agents."
 },
 {
  "id": "agentpeering-registry",
  "org_id": "agentpeering",
  "name": "AgentPeering",
  "url": "https://agentpeering.com/docs/faq",
  "type": "authority",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AgentPeering",
    "role": "Independent public A2A registry",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Independent vendor-neutral A2A registry verifying domain ownership, monitoring uptime, and speaking `v0.3` `message/send` (plus `v0.2` `tasks/send`).",
    "full_detail_md": "Owners prove domain control and receive a public page with uptime monitoring, latency tracking, and a trust score. The registry speaks A2A v0.3 message/send and still accepts v0.2 tasks/send. It states it is not affiliated with Google or the Linux Foundation.",
    "facets": {
     "transport_bindings": "JSON-RPC; v0.3 message/send and v0.2 tasks/send",
     "discovery_artifact": "Agent Card at /.well-known/agent-card.json",
     "protocol_version": "v0.3, still accepts v0.2",
     "auth_schemes": "Domain-ownership proof for listings",
     "verification_posture": "Independent registry FAQ checked 2026-11-06"
    },
    "telemetry": null,
    "source_url": "https://agentpeering.com/docs/faq"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://agentpeering.com/docs/faq",
  "note": "Independent vendor-neutral A2A registry verifying domain ownership, monitoring uptime, and speaking `v0.3` `message/send` (plus `v0.2` `tasks/send`)."
 },
 {
  "id": "agents-txt-audit-tool",
  "org_id": "agents-txt-audit-tool",
  "name": "agents.txt audit tool (mcp.agents-txt.com)",
  "url": "https://agents-txt.com/about/",
  "type": "authority",
  "implements": [
   "agents-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "agents.txt audit tool (mcp.agents-txt.com)",
    "role": "CLI / Validator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Live audit tool and the `audit_site` MCP tool at mcp.agents-txt.com validate an agents.txt file against the draft",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agents-txt.com/about/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://agents-txt.com/about/",
  "note": "Live audit tool and the `audit_site` MCP tool at mcp.agents-txt.com validate an agents.txt file against the draft"
 },
 {
  "id": "agents-txt-com",
  "org_id": "agents-txt-com",
  "name": "agents-txt.com",
  "url": "https://agents-txt.com/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "agents-txt.com",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://agents-txt.com/auth.md is the agents.txt reference site's registration walkthrough, advertised from /agents.txt under Authorization: auth-md. Authorization-server metadata agent_auth lists skill https://agents-txt.com/auth.md, register_uri https://agents-txt.com/agent/auth, claim_uri https://agents-txt.com/agent/auth/claim, revocation_uri https://agents-txt.com/agent/auth/revoke, and identity types anonymous and identity_assertion.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agents-txt.com/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://agents-txt.com/auth.md",
  "note": "https://agents-txt.com/auth.md is the agents.txt reference site's registration walkthrough, advertised from /agents.txt under Authorization: auth-md. Authorization-server metadata agent_auth lists skill https://agents-txt.com/auth.md, register_uri https://agents-txt.com/agent/auth, claim_uri https://agents-txt.com/agent/auth/claim, revocation_uri https://agents-txt.com/agent/auth/revoke, and ident"
 },
 {
  "id": "agentskill-sh-marketplace",
  "org_id": "agentskill-sh",
  "name": "agentskill.sh",
  "url": "https://agentskill.sh/",
  "type": "authority",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "agentskill.sh",
    "role": "Agent skills marketplace",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Vendor-declared marketplace counter listing `275,000+` skills for `20+` AI tools (self-reported, not deduplicated or security-vetted).",
    "full_detail_md": "The homepage offers skills for Claude Code, Cursor, Copilot, Windsurf, Zed, and 20+ AI tools. This count is a different population from GuildSkills.",
    "facets": {
     "transport_or_packaging": "Public skills marketplace",
     "manifest_or_entry": "275,000+ skills",
     "execution_or_sandbox": "Directory browse surface",
     "verification_posture": "Homepage claim checked 2026-11-06"
    },
    "telemetry": null,
    "source_url": "https://agentskill.sh/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://agentskill.sh/",
  "note": "Vendor-declared marketplace counter listing `275,000+` skills for `20+` AI tools (self-reported, not deduplicated or security-vetted)."
 },
 {
  "id": "agenui",
  "org_id": "agenui",
  "name": "AGenUI",
  "url": "https://github.com/AGenUI/AGenUI",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "AGenUI",
    "role": "Native renderer",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "AGenUI describes a native A2UI renderer for iOS, Android, and HarmonyOS (`v1.7.0`).",
    "full_detail_md": "The AGenUI repository describes a Native A2UI Renderer for iOS, Android, and HarmonyOS, and its README includes a section titled What's New in v1.7.0. The row stays Listed from that repository README rather than Supported, because the evidence is the default-branch README and not a pinned release snapshot.",
    "facets": {
     "transport_or_binding": "Native streaming renderer described by the repository README",
     "component_or_catalog": "Custom components and styles",
     "spec_version": "README section What's New in v1.7.0; not graded from a release snapshot",
     "sdk_or_renderer": "AGenUI for iOS, Android, and HarmonyOS"
    },
    "telemetry": null,
    "source_url": "https://github.com/AGenUI/AGenUI"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/AGenUI/AGenUI",
  "note": "AGenUI describes a native A2UI renderer for iOS, Android, and HarmonyOS (`v1.7.0`)."
 },
 {
  "id": "agiodigital-com",
  "org_id": "agio-digital",
  "name": "Agio Digital",
  "url": "https://www.agiodigital.com/",
  "type": "origin",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "Agio Digital",
    "role": "In-page caller",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Page script checks `r.modelContext.registerTool`, then calls it.",
    "full_detail_md": "The HTTP 200 page fetched 2026-10-30 binds the document argument to `r`, checks that `r.modelContext.registerTool` is a function, and calls `r.modelContext.registerTool` with name, description, and inputSchema.",
    "facets": {
     "engine_or_runtime": "In-page script on www.agiodigital.com",
     "api_surface_or_flag": "r.modelContext.registerTool after a function check (document argument bound to r)",
     "position_or_status": "Live HTTP 200 page (fetched 2026-10-30)",
     "package_or_version": "Spec member document.modelContext.registerTool; no package version in the script"
    },
    "telemetry": {
     "http_status": 200,
     "observed_member": "modelContext.registerTool",
     "document_binding": "{document:t=Yee,enabled:n=!0}=e,r=t",
     "spec_member": "document.modelContext.registerTool"
    },
    "source_url": "https://www.agiodigital.com/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.agiodigital.com/",
  "note": "Page script checks `r.modelContext.registerTool`, then calls it."
 },
 {
  "id": "agno",
  "org_id": "agno",
  "name": "Agno",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "sdk",
  "implements": [
   "ag-ui",
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Agno",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists Agno as Supported under Agent Framework - 1st Party, with Docs and Demos.",
    "full_detail_md": "The AG-UI overview lists Agno as Supported under Agent Framework - 1st Party, with Docs and Demos. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "1st-party agent framework (directory listing)",
     "sdk_or_package": "Not named; Docs and Demos only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   },
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Agno",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`OpenResponses` base class; stateless, no `previous_response_id`; configurable `base_url`.",
    "full_detail_md": "Agno documents OpenResponses, the base class for providers implementing the Open Responses API specification, with a configurable base_url and a role_map. The class is stateless by default (no previous_response_id chaining), and the same page says providers that implement this spec include Ollama (v0.13.3+) and OpenRouter.",
    "facets": {
     "endpoint_or_route": "configurable base_url",
     "streaming_or_items": "Base class for Open Responses providers; this reference page does not name a streaming flag",
     "tool_or_state_model": "stateless by default (no previous_response_id chaining); role_map includes tool",
     "sdk_or_version": "OpenResponses class; the page cites Ollama v0.13.3+ and OpenRouter"
    },
    "telemetry": null,
    "source_url": "https://docs.agno.com/reference/models/open-responses"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "Overview lists Agno as Supported under Agent Framework - 1st Party, with Docs and Demos."
 },
 {
  "id": "agntcy-acp-acpnode",
  "org_id": "agntcy",
  "name": "ACPNode",
  "url": "https://raw.githubusercontent.com/agntcy/docs/a23e3c757391e13b9834a59b26a0a33d8d70a328/docs/syntactic/agntcy_acp_sdk.md",
  "type": "sdk",
  "implements": [
   "agent-connect-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-connect-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "agntcy_acp.langgraph.ACPNode",
    "role": "Orchestrator node",
    "status": "Partial",
    "status_display": "Partial · as of 2026-04-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-11",
    "col4_md": "The agntcy-acp docs show `agntcy_acp.langgraph.ACPNode` used as a LangGraph graph node so a remote ACP agent can sit inside a `StateGraph`. The package version on PyPI is `1.5.2`. The `agntcy/acp-sdk` repository was archived by the owner on Apr 11, 2026. AGNTCY deprecated Agent Connect Protocol on `2025-08-21` in favor of A2A and archived the repositories on Apr 11, 2026.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agntcy/docs/a23e3c757391e13b9834a59b26a0a33d8d70a328/docs/syntactic/agntcy_acp_sdk.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/agntcy/docs/a23e3c757391e13b9834a59b26a0a33d8d70a328/docs/syntactic/agntcy_acp_sdk.md",
  "note": "The agntcy-acp docs show `agntcy_acp.langgraph.ACPNode` used as a LangGraph graph node so a remote ACP agent can sit inside a `StateGraph`. The package version on PyPI is `1.5.2`. The `agntcy/acp-sdk` repository was archived by the owner on Apr 11, 2026. AGNTCY deprecated Agent Connect Protocol on `2025-08-21` in favor of A2A and archived the repositories on Apr 11, 2026."
 },
 {
  "id": "agntcy-acp-cli",
  "org_id": "agntcy",
  "name": "agntcy-acp CLI",
  "url": "https://raw.githubusercontent.com/agntcy/docs/a23e3c757391e13b9834a59b26a0a33d8d70a328/docs/syntactic/agntcy_acp_sdk.md",
  "type": "sdk",
  "implements": [
   "agent-connect-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-connect-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "agntcy-acp CLI",
    "role": "CLI",
    "status": "Partial",
    "status_display": "Partial · as of 2026-04-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-11",
    "col4_md": "The agntcy-acp client SDK includes a CLI. Commands are `generate-agent-models`, `generate-agent-oapi`, `validate-acp-descriptor`, and `validate-acp-manifest`. PyPI version is `1.5.2`. The `agntcy/acp-sdk` repository was archived by the owner on Apr 11, 2026. AGNTCY deprecated Agent Connect Protocol on `2025-08-21` in favor of A2A and archived the repositories on Apr 11, 2026.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agntcy/docs/a23e3c757391e13b9834a59b26a0a33d8d70a328/docs/syntactic/agntcy_acp_sdk.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/agntcy/docs/a23e3c757391e13b9834a59b26a0a33d8d70a328/docs/syntactic/agntcy_acp_sdk.md",
  "note": "The agntcy-acp client SDK includes a CLI. Commands are `generate-agent-models`, `generate-agent-oapi`, `validate-acp-descriptor`, and `validate-acp-manifest`. PyPI version is `1.5.2`. The `agntcy/acp-sdk` repository was archived by the owner on Apr 11, 2026. AGNTCY deprecated Agent Connect Protocol on `2025-08-21` in favor of A2A and archived the repositories on Apr 11, 2026."
 },
 {
  "id": "agntcy-acp-client",
  "org_id": "agntcy",
  "name": "agntcy-acp Python client",
  "url": "https://pypi.org/project/agntcy-acp/",
  "type": "sdk",
  "implements": [
   "agent-connect-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-connect-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "agntcy-acp Python client",
    "role": "Client SDK",
    "status": "Partial",
    "status_display": "Partial · as of 2026-04-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-11",
    "col4_md": "PyPI package `agntcy-acp` version `1.5.2` summarizes itself as Agent Connect Protocol SDK. The `1.5.2` wheel was uploaded on 2025-06-16, matching GitHub release `v1.5.2` published the same day, and the client docs import `AsyncACPClient`. The repository was last pushed on 2025-06-16 and archived read-only by the owner on Apr 11, 2026, following AGNTCY's `2025-08-21` deprecation of Agent Connect Protocol in favor of A2A.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/agntcy-acp/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/agntcy-acp/json",
  "note": "PyPI package `agntcy-acp` version `1.5.2` summarizes itself as Agent Connect Protocol SDK. The `1.5.2` wheel was uploaded on 2025-06-16, matching GitHub release `v1.5.2` published the same day, and the client docs import `AsyncACPClient`. The repository was last pushed on 2025-06-16 and archived read-only by the owner on Apr 11, 2026, following AGNTCY's `2025-08-21` deprecation of Agent Connect Pr"
 },
 {
  "id": "agntcy-acp-package-index",
  "org_id": "agntcy",
  "name": "agntcy-acp package index",
  "url": "https://agntcy.github.io/acp-sdk/html/index.html",
  "type": "sdk",
  "implements": [
   "agent-connect-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-connect-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "agntcy-acp package index",
    "role": "Client and server SDK modules",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "The package API reference describes the Agent Connect Protocol SDK as an open-source library with tools for both client and server implementations. The module index lists `agntcy_acp.langgraph.acp_node`, `agntcy_acp.langgraph.api_bridge`, `agntcy_acp.langgraph.io_mapper`, and `agntcy_acp.manifest`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agntcy.github.io/acp-sdk/html/index.html"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://agntcy.github.io/acp-sdk/html/index.html",
  "note": "The package API reference describes the Agent Connect Protocol SDK as an open-source library with tools for both client and server implementations. The module index lists `agntcy_acp.langgraph.acp_node`, `agntcy_acp.langgraph.api_bridge`, `agntcy_acp.langgraph.io_mapper`, and `agntcy_acp.manifest`."
 },
 {
  "id": "agntcy-dir",
  "org_id": "agntcy",
  "name": "AGNTCY Directory (agntcy/dir)",
  "url": "https://github.com/agntcy/dir",
  "type": "sdk",
  "implements": [
   "ads"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ads",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AGNTCY Directory (`agntcy/dir`)",
    "role": "Directory server & CLI",
    "status": "Development",
    "status_display": "Development · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-10-30",
    "col4_md": "Source repository named in `draft-mp-agntcy-ads-03` (Go, `Apache-2.0`, pushed 2026-10-30). Implements the gRPC `apiserver`, `reconciler`, and `dirctl` daemon backed by OCI artifact storage and DHT content routing for OASF agent records, with `v1.8.0` container images and Helm chart plus Go, Python, and JavaScript SDKs documented in the repository README (documented from repository metadata rather than a probed public ADS endpoint).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agntcy/dir/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/agntcy/dir/main/README.md",
  "note": "Source repository named in `draft-mp-agntcy-ads-03` (Go, `Apache-2.0`, pushed 2026-10-30). Implements the gRPC `apiserver`, `reconciler`, and `dirctl` daemon backed by OCI artifact storage and DHT content routing for OASF agent records, with `v1.8.0` container images and Helm chart plus Go, Python, and JavaScript SDKs documented in the repository README (documented from repository metadata rather "
 },
 {
  "id": "agntcy-slim",
  "org_id": "agntcy-slim",
  "name": "agntcy/slim",
  "url": "https://slim.agntcy.org/latest/slim/slim-overview/",
  "type": "sdk",
  "implements": [
   "slim"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "slim",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "agntcy/slim",
    "role": "Messaging node / Server",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-20",
    "col4_md": "Messaging node software slim-v3.4.6 with slimctl-v3.4.6 (published 2026-10-20). gRPC data plane routed by hierarchical names; Rust control plane. Group sessions optionally use MLS, with key rotation when membership changes. Carries A2A or MCP, or direct point-to-point and group messages.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://slim.agntcy.org/latest/slim/slim-overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://slim.agntcy.org/latest/slim/slim-overview/",
  "note": "Messaging node software slim-v3.4.6 with slimctl-v3.4.6 (published 2026-10-20). gRPC data plane routed by hierarchical names; Rust control plane. Group sessions optionally use MLS, with key rotation when membership changes. Carries A2A or MCP, or direct point-to-point and group messages."
 },
 {
  "id": "agntcy-workflow-srv",
  "org_id": "agntcy",
  "name": "AGNTCY Agent Workflow Server",
  "url": "https://github.com/agntcy/workflow-srv",
  "type": "sdk",
  "implements": [
   "agent-connect-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-connect-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AGNTCY Agent Workflow Server",
    "role": "Server runtime",
    "status": "Partial",
    "status_display": "Partial · as of 2026-04-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-11",
    "col4_md": "Agent Workflow Server exposes agents from diverse frameworks through Agent Connect Protocol (ACP). The support table lists `LangGraph` `>=0.2.60,<0.4.0` and `LlamaIndex` `>=0.12.0,<0.13.0`, with client auth via `x-api-key`. That `x-api-key` header is the Workflow Server's optional API key, not an authentication scheme defined by the ACP OpenAPI document. The docs state this component is not currently under active development; the repository was last pushed on 2025-09-15 and archived read-only by the owner on Apr 11, 2026. `agntcy/acp-spec` is the Agent Connect Protocol specification proposed by the Agntcy Collective (OpenAPI `3.1.1`, title Agent Connect Protocol, version `0.2.3`), last pushed on 2025-05-23 and archived read-only. On `2025-08-21` Luca Muscariello wrote that the Core WG is deprecating ACP in favor of A2A, and AGNTCY archived the repositories on Apr 11, 2026.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agntcy/workflow-srv/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/agntcy/workflow-srv/main/README.md",
  "note": "Agent Workflow Server exposes agents from diverse frameworks through Agent Connect Protocol (ACP). The support table lists `LangGraph` `>=0.2.60,<0.4.0` and `LlamaIndex` `>=0.12.0,<0.13.0`, with client auth via `x-api-key`. That `x-api-key` header is the Workflow Server's optional API key, not an authentication scheme defined by the ACP OpenAPI document. The docs state this component is not curren"
 },
 {
  "id": "agora-protocol",
  "org_id": "agora-protocol",
  "name": "agora-protocol (PyPI)",
  "url": "https://raw.githubusercontent.com/agora-protocol/python/main/README.md",
  "type": "sdk",
  "implements": [
   "agora-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agora-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "agora-protocol (PyPI)",
    "role": "Client SDK / Runtime",
    "status": "Experimental",
    "status_display": "Experimental · as of 2025-01-03",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-01-03",
    "col4_md": "PyPI agora-protocol 0.2.0 (uploaded 2025-01-03), README status Open Beta. Exchanges use HTTPS POST. Agents refer to a protocol document by its SHA1 hash. The getting-started example pairs a LangChain agent with a Camel agent, first in natural language and then with structured routines. The 2024 site also describes an optional /.wellknown endpoint that returns supported protocol hashes.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agora-protocol/python/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/agora-protocol/python/main/README.md",
  "note": "PyPI agora-protocol 0.2.0 (uploaded 2025-01-03), README status Open Beta. Exchanges use HTTPS POST. Agents refer to a protocol document by its SHA1 hash. The getting-started example pairs a LangChain agent with a Camel agent, first in natural language and then with structured routines. The 2024 site also describes an optional /.wellknown endpoint that returns supported protocol hashes."
 },
 {
  "id": "agoraescrowv2-sol-agoraescrowv1-sol",
  "org_id": "agoraescrowv2-sol-agoraescrowv1-sol",
  "name": "AgoraEscrowV2.sol & AgoraEscrowV1.sol (Base Sepolia)",
  "url": "https://base-sepolia.blockscout.com/api/v2/addresses/0x0e8E6A760c76cA92c5C5dA06d293E33f1B5fbAEc/transactions",
  "type": "venue",
  "implements": [
   "agora-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agora-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "`AgoraEscrowV2.sol` & `AgoraEscrowV1.sol` (Base Sepolia)",
    "role": "Escrow settlement contracts (Originator)",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-05-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-05-29",
    "col4_md": "Base Sepolia USDC escrow contracts (AgoraEscrowV2.sol at 0x0e8E…bAEc deployed 2026-05-29 with 1 on-chain job on V2; legacy AgoraEscrowV1 at 0xCE78…2B76 has 1,499 prior testnet txns; V2.1 undeployed)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://base-sepolia.blockscout.com/api/v2/addresses/0x0e8E6A760c76cA92c5C5dA06d293E33f1B5fbAEc/transactions"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://base-sepolia.blockscout.com/api/v2/addresses/0x0e8E6A760c76cA92c5C5dA06d293E33f1B5fbAEc/transactions",
  "note": "Base Sepolia USDC escrow contracts (AgoraEscrowV2.sol at 0x0e8E…bAEc deployed 2026-05-29 with 1 on-chain job on V2; legacy AgoraEscrowV1 at 0xCE78…2B76 has 1,499 prior testnet txns; V2.1 undeployed)"
 },
 {
  "id": "agoraproto-org",
  "org_id": "agoraproto-org",
  "name": "agoraproto.org (api.agoraproto.org)",
  "url": "https://agoraproto.org",
  "type": "venue",
  "implements": [
   "agora-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agora-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "`agoraproto.org` (`api.agoraproto.org`)",
    "role": "Marketplace platform (Originator)",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-05-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-05-29",
    "col4_md": "HTTP 402 job marketplace API (`/v1/x402/jobs`, `/v1/payments/execute`) settling in Base Sepolia testnet USDC (537 cumulative API-tracked jobs reported in `/v1/stats` across legacy and on-chain routes; newest completed job dated 2026-05-29 UTC)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agoraproto.org"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://agoraproto.org",
  "note": "HTTP 402 job marketplace API (`/v1/x402/jobs`, `/v1/payments/execute`) settling in Base Sepolia testnet USDC (537 cumulative API-tracked jobs reported in `/v1/stats` across legacy and on-chain routes; newest completed job dated 2026-05-29 UTC)"
 },
 {
  "id": "ai-catalog-cli",
  "org_id": "ai-catalog-cli",
  "name": "ai-catalog CLI",
  "url": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-cli/main/README.md",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "ai-catalog CLI",
    "role": "Validator / Parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Installed binary `ai-catalog` (crate `ai-catalog-cli`) inspects, validates, and packages catalogs. Its `SKILL.md` tells an agent to call that binary to discover and install catalog entries.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-cli/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-cli/main/README.md",
  "note": "Installed binary `ai-catalog` (crate `ai-catalog-cli`) inspects, validates, and packages catalogs. Its `SKILL.md` tells an agent to call that binary to discover and install catalog entries."
 },
 {
  "id": "ai-catalog-go-sdk",
  "org_id": "ai-catalog-go-sdk",
  "name": "AI Catalog Go SDK",
  "url": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-go/main/README.md",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "AI Catalog Go SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`discovery.Discover` accepts a URL or a bare domain and tries, in order, a catalog at the URL, a `Link` header with rel=ai-catalog, an HTML `<link rel=\"ai-catalog\">`, then `/.well-known/ai-catalog.json`. The README states that `discovery.Discover` does not guard against requests to private addresses by default; a service that runs it for callers it does not trust should pass `discovery.WithFetcher`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-go/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-go/main/README.md",
  "note": "`discovery.Discover` accepts a URL or a bare domain and tries, in order, a catalog at the URL, a `Link` header with rel=ai-catalog, an HTML `<link rel=\"ai-catalog\">`, then `/.well-known/ai-catalog.json`. The README states that `discovery.Discover` does not guard against requests to private addresses by default; a service that runs it for callers it does not trust should pass `discovery.WithFetcher"
 },
 {
  "id": "ai-catalog-rust-sdk",
  "org_id": "ai-catalog-rust-sdk",
  "name": "AI Catalog Rust SDK",
  "url": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-rust/main/README.md",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "AI Catalog Rust SDK",
    "role": "Validator / Parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Crates `ai-catalog`, `ai-catalog-validate`, `ai-catalog-trust`, and `ai-catalog-discover` implement the spec. `ai-catalog-discover` resolves a `Link` header, an HTML <link rel=\"ai-catalog\">, and /.well-known/ai-catalog.json.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-rust/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/Agent-Card/ai-catalog-rust/main/README.md",
  "note": "Crates `ai-catalog`, `ai-catalog-validate`, `ai-catalog-trust`, and `ai-catalog-discover` implement the spec. `ai-catalog-discover` resolves a `Link` header, an HTML <link rel=\"ai-catalog\">, and /.well-known/ai-catalog.json."
 },
 {
  "id": "ai-google-dev-gemini-api-docs-llms-txt",
  "org_id": "google",
  "name": "Gemini API",
  "url": "https://ai.google.dev/gemini-api/docs/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Google AI (Gemini API docs)",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `https://ai.google.dev/gemini-api/docs/llms.txt` as `text/markdown` (`# Gemini API`), indexing Gemini API docs, API reference, and managed-agent environment pages.",
    "full_detail_md": "Serves `https://ai.google.dev/gemini-api/docs/llms.txt` as `text/markdown; charset=utf-8` (84,423 bytes, fetched 2026-10-30). Deployed at the `/gemini-api/docs/` subpath, the file opens `# Gemini API` and indexes Gemini API guides, the API reference, Google AI Studio quickstarts, and persistent execution environments for managed agents.",
    "facets": {
     "artifact_path": "https://ai.google.dev/gemini-api/docs/llms.txt",
     "companion_files": "Linked Gemini API .md documentation and API reference pages",
     "content_type_or_bytes": "text/markdown; charset=utf-8 (84,423 bytes)",
     "generator_or_consumer_mode": "Subpath documentation index (/gemini-api/docs/llms.txt)"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "marker": "# Gemini API",
     "content_type": "text/markdown; charset=utf-8"
    },
    "source_url": "https://ai.google.dev/gemini-api/docs/llms.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://ai.google.dev/gemini-api/docs/llms.txt",
  "note": "Serves `https://ai.google.dev/gemini-api/docs/llms.txt` as `text/markdown` (`# Gemini API`), indexing Gemini API docs, API reference, and managed-agent environment pages."
 },
 {
  "id": "ai-txt-core",
  "org_id": "ai-txt-core",
  "name": "@ai-txt/core",
  "url": "https://github.com/kaylacar/ai-txt",
  "type": "sdk",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "@ai-txt/core",
    "role": "Validator / Parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "CLI check npx @ai-txt/core check `<url>` --agent ClaudeBot fetches a site's ai.txt and evaluates it for a named agent.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/kaylacar/ai-txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/kaylacar/ai-txt",
  "note": "CLI check npx @ai-txt/core check `<url>` --agent ClaudeBot fetches a site's ai.txt and evaluates it for a named agent."
 },
 {
  "id": "ai2bot",
  "org_id": "allen-institute",
  "name": "AI2Bot",
  "url": "https://allenai.org/crawler",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Allen Institute for AI",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`AI2Bot` (`Mozilla/5.0 (compatible) AI2Bot (+https://www.allenai.org/crawler)`) crawls web content to train open language models.",
    "full_detail_md": "The AI2 Bot collects web content used to train open language models. Requests send the User-Agent `Mozilla/5.0 (compatible) AI2Bot (+https://www.allenai.org/crawler)`, which the page says can be used to filter or reject that traffic.",
    "facets": {
     "user_agent_token": [
      "AI2Bot",
      "Mozilla/5.0 (compatible) AI2Bot (+https://www.allenai.org/crawler)"
     ],
     "operator_purpose": "Collecting web content to train open language models",
     "ip_verification_url": "https://allenai.org/crawler",
     "robots_directives_honored": "User-Agent string can be used by site operators to filter or reject crawler traffic"
    },
    "telemetry": null,
    "source_url": "https://allenai.org/crawler"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://allenai.org/crawler",
  "note": "`AI2Bot` (`Mozilla/5.0 (compatible) AI2Bot (+https://www.allenai.org/crawler)`) crawls web content to train open language models."
 },
 {
  "id": "aid-discovery",
  "org_id": "aid-discovery",
  "name": "aid-discovery",
  "url": "https://pypi.org/pypi/aid-discovery/json",
  "type": "sdk",
  "implements": [
   "aid"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "aid",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "aid-discovery",
    "role": "Resolver / Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-25",
    "col4_md": "Python discovery library on PyPI; 2.1.1 uploaded 2026-07-25 (1.0.0 on 2025-07-17). PyPI summary: library for AID, a DNS-based discovery protocol for AI agents",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/aid-discovery/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/aid-discovery/json",
  "note": "Python discovery library on PyPI; 2.1.1 uploaded 2026-07-25 (1.0.0 on 2025-07-17). PyPI summary: library for AID, a DNS-based discovery protocol for AI agents"
 },
 {
  "id": "aider",
  "org_id": "aider",
  "name": "Aider",
  "url": "https://agents.md/",
  "type": "harness",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Aider",
    "role": "Coding agent / CLI",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Documented in the `agents.md` FAQ as requiring explicit `read: AGENTS.md` configuration in `.aider.conf.yml`.",
    "full_detail_md": "Listed on `agents.md` with an explicit FAQ configuration snippet (`Configure Aider to use AGENTS.md` in `.aider.conf.yml` via `read: AGENTS.md`); requires opt-in configuration in `.aider.conf.yml` rather than automatic directory-hierarchy discovery.",
    "facets": {
     "discovery_behavior": "Opt-in file read configured via `read: AGENTS.md` in `.aider.conf.yml`",
     "hierarchy_precedence": "Explicit file path configured in `.aider.conf.yml`",
     "fallback_files": ".aider.conf.yml",
     "verification_posture": "Configuration snippet documented in the `agents.md` FAQ"
    },
    "telemetry": null,
    "source_url": "https://agents.md/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://agents.md/",
  "note": "Documented in the `agents.md` FAQ as requiring explicit `read: AGENTS.md` configuration in `.aider.conf.yml`."
 },
 {
  "id": "aioseo",
  "org_id": "aioseo",
  "name": "AIOSEO",
  "url": "https://aioseo.com/features/llms-txt/",
  "type": "sdk",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "AIOSEO",
    "role": "WordPress SEO plugin",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-10",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-10",
    "col4_md": "WordPress plugin documented on `llmstxt.org` that ships a built-in `llms.txt` generator.",
    "full_detail_md": "Listed in the `llmstxt.org` Integrations section as a WordPress plugin (All in One SEO) providing a built-in `llms.txt` generator for WordPress sites.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "None stated",
     "content_type_or_bytes": "Generated Markdown index (CMS plugin)",
     "generator_or_consumer_mode": "WordPress plugin with built-in /llms.txt generator"
    },
    "telemetry": null,
    "source_url": "https://llmstxt.org"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://llmstxt.org",
  "note": "WordPress plugin documented on `llmstxt.org` that ships a built-in `llms.txt` generator."
 },
 {
  "id": "akamai",
  "org_id": "akamai",
  "name": "Akamai",
  "url": "https://investor.visa.com/news/news-details/2025/Akamai-and-Visa-Collaborate-to-Build-Trust-in-Agentic-Commerce/default.aspx",
  "type": "authority",
  "implements": [
   "kyapay-token",
   "tap"
  ],
  "archetypes": [
   "identity_auth_crypto",
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "tap",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Akamai",
    "role": "CDN / WAF verifier",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-17",
    "col4_md": "Joint announcement of 2025-12-17: Trusted Agent Protocol is supported across Akamai Cloud, with Akamai's edge user recognition and bot and abuse protection, to establish the agent and the person the agent represents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://investor.visa.com/news/news-details/2025/Akamai-and-Visa-Collaborate-to-Build-Trust-in-Agentic-Commerce/default.aspx"
   },
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Akamai",
    "role": "Edge verifier / platform (Companion draft co-author)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Edge verification of Skyfire KYA/PAY JWTs (`hid`, `apd`, `aid` claims) for bot management and paid crawl access alongside TollBit",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20260610154228id_/https://www.akamai.com/newsroom/press-release/no-free-crawls-akamai-tollbit-and-skyfire-turn-traffic-into-revenue"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://investor.visa.com/news/news-details/2025/Akamai-and-Visa-Collaborate-to-Build-Trust-in-Agentic-Commerce/default.aspx",
  "note": "Joint announcement of 2025-12-17: Trusted Agent Protocol is supported across Akamai Cloud, with Akamai's edge user recognition and bot and abuse protection, to establish the agent and the person the agent represents."
 },
 {
  "id": "akamai-app-api-protector",
  "org_id": "akamai",
  "name": "Akamai App & API Protector",
  "url": "https://web.archive.org/web/20260609113733/https://www.akamai.com/blog/security/redefine-trust-web-bot-authentication",
  "type": "authority",
  "implements": [
   "http-message-signatures"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Akamai (App & API Protector)",
    "role": "CDN / WAF verifier (Web Bot Auth & TAP profiles)",
    "status": "Partial",
    "status_display": "Partial · as of 2025-11-10",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-10",
    "col4_md": "Validates Web Bot Auth and Visa Trusted Agent Protocol signatures at the edge using RFC 9421 rules.",
    "full_detail_md": "Akamai App & API Protector retrieves a bot's `application/http-message-signatures-directory+json` public key directory and validates `Signature-Input` and `Signature` headers at the Akamai edge using RFC 9421 rules for Web Bot Auth and Visa's Trusted Agent Protocol (published November 10, 2025).",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth and Visa Trusted Agent Protocol profiles of RFC 9421",
     "signature_fields": "`Signature-Input` and `Signature` validated against `application/http-message-signatures-directory+json` directories",
     "algorithms_or_keys": "RFC 9421 public-key verification (e.g., `alg=\"rsa-pss-sha512\"`)",
     "verification_posture": "CDN / WAF edge verifier (Akamai App & API Protector)"
    },
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20260609113733/https://www.akamai.com/blog/security/redefine-trust-web-bot-authentication"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://web.archive.org/web/20260609113733/https://www.akamai.com/blog/security/redefine-trust-web-bot-authentication",
  "note": "Validates Web Bot Auth and Visa Trusted Agent Protocol signatures at the edge using RFC 9421 rules."
 },
 {
  "id": "alation-a2ui",
  "org_id": "alation",
  "name": "Alation",
  "url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "type": "harness",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Alation",
    "role": "Product host",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-11-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-11-11",
    "col4_md": "The Alation Intelligence Operating System (AIOS) builds its feeds using A2UI, and Alation is named among companies already building with A2UI.",
    "full_detail_md": "The NOV. 11, 2026 Google Developers Blog says AIOS builds feeds using A2UI, including metric cards and charts, and that the same feed can be viewed inside Alation.",
    "facets": {
     "transport_or_binding": "A2UI feeds in Alation and in an assistant conversation",
     "component_or_catalog": "Metric cards, charts, and custom components",
     "spec_version": "Named in the A2UI 1.0 public-release announcement",
     "sdk_or_renderer": "Alation Intelligence Operating System (AIOS)"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "note": "The Alation Intelligence Operating System (AIOS) builds its feeds using A2UI, and Alation is named among companies already building with A2UI."
 },
 {
  "id": "alchemy",
  "org_id": "alchemy",
  "name": "Alchemy",
  "url": "https://agents.alchemy.com/",
  "type": "origin",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Alchemy",
    "role": "Seller",
    "status": "Listed",
    "status_display": "Listed · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Catalog active: `tempo` and `stripe` `charge`; POST `/:network/v2` at `https://mpp.alchemy.com`.",
    "full_detail_md": "The catalog lists Alchemy as active, with serviceUrl https://mpp.alchemy.com, methods tempo and stripe, intent charge, and assets 0x20c000000000000000000000b9537d11c60e8b50 and usd. POST /:network/v2 is a JSON-RPC call (eth_*, alchemy_*).",
    "facets": {
     "settlement_rail": "tempo and stripe charge; assets 0x20c000000000000000000000b9537d11c60e8b50 and usd",
     "challenge_or_scheme": "Catalog status active; serviceUrl https://mpp.alchemy.com",
     "headers_or_methods": "Payment method tempo and stripe, intent charge",
     "sdk_or_endpoint": "POST /:network/v2 JSON-RPC (eth_*, alchemy_*)"
    },
    "telemetry": null,
    "source_url": "https://mpp.dev/api/services"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.dev/api/services",
  "note": "Catalog active: `tempo` and `stripe` `charge`; POST `/:network/v2` at `https://mpp.alchemy.com`."
 },
 {
  "id": "algovoi",
  "org_id": "algovoi",
  "name": "AlgoVoi",
  "url": "https://algovoi.co.uk",
  "type": "authority",
  "implements": [
   "ap2"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ap2",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "AlgoVoi",
    "role": "Payment gateway",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The extensions document sets `ap2_version` to `0.1`. AlgoVoi Crypto Payment Method adds multi-chain methods for Algorand, VOI, Hedera, Stellar, Base, Solana, Tempo, and ARC, used as `PaymentMethodData.supported_methods`. AlgoVoi Intent Bounds adds optional max_price and max_quantity fields to `IntentMandate`. The AlgoVoi Payment Agent card says it gates access using x402, MPP (IETF), or AP2. The host OpenAPI document titles the service AlgoVoi Gateway, a public-facing x402 payment gateway.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json"
    },
    "source_url": "https://api.algovoi.co.uk/ap2/extensions"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.algovoi.co.uk/ap2/extensions",
  "note": "The extensions document sets `ap2_version` to `0.1`. AlgoVoi Crypto Payment Method adds multi-chain methods for Algorand, VOI, Hedera, Stellar, Base, Solana, Tempo, and ARC, used as `PaymentMethodData.supported_methods`. AlgoVoi Intent Bounds adds optional max_price and max_quantity fields to `IntentMandate`. The AlgoVoi Payment Agent card says it gates access using x402, MPP (IETF), or AP2. The h"
 },
 {
  "id": "allbirds",
  "org_id": "allbirds",
  "name": "Allbirds",
  "url": "https://www.allbirds.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Allbirds",
    "role": "Seller (Shopify merchant)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`.",
    "full_detail_md": "The live profile declares protocol version 2026-08-25 (the ucp.version field, not a publication date) on weareallbirds.myshopify.com, where dev.ucp.shopping binds transports mcp and embedded and service dev.ucp.common is published. Payment handlers are com.google.pay at handler spec 2026-01-11, dev.shopify.card at handler spec 2026-01-15, and dev.shopify.shop_pay at handler spec 2026-04-08, and capabilities include dev.ucp.shopping.checkout plus dev.ucp.common.identity_linking.",
    "facets": {
     "commerce_surface": "Shopify storefront weareallbirds.myshopify.com",
     "payment_handlers_or_rail": "com.google.pay (handler spec 2026-01-11), dev.shopify.card (handler spec 2026-01-15), dev.shopify.shop_pay (handler spec 2026-04-08)",
     "transport_bindings": "dev.ucp.shopping over mcp and embedded; dev.ucp.common over mcp",
     "spec_version": "ucp.version 2026-08-25 (protocol version, not a publication date); supported_versions also lists 2026-04-08 and 2026-01-23"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8",
     "ucp_version": "2026-08-25",
     "transports": [
      "mcp",
      "embedded"
     ],
     "payment_handlers": [
      "com.google.pay",
      "dev.shopify.card",
      "dev.shopify.shop_pay"
     ],
     "merchant_host": "weareallbirds.myshopify.com",
     "publishes_dev_ucp_common_service": true
    },
    "source_url": "https://www.allbirds.com/.well-known/ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.allbirds.com/.well-known/ucp",
  "note": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`."
 },
 {
  "id": "alpic",
  "org_id": "alpic",
  "name": "Alpic",
  "url": "https://alpic.ai/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Alpic",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://alpic.ai/auth.md tells an agent how to obtain an Alpic API key and deploy MCP servers. https://api.alpic.ai/.well-known/oauth-authorization-server advertises agent_auth.skill https://alpic.ai/auth.md, register_uri https://api.alpic.ai/agent/auth, assertion types urn:ietf:params:oauth:token-type:id-jag and urn:ietf:params:oauth:token-type:jwt, and credential type api_key.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://alpic.ai/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://alpic.ai/auth.md",
  "note": "https://alpic.ai/auth.md tells an agent how to obtain an Alpic API key and deploy MCP servers. https://api.alpic.ai/.well-known/oauth-authorization-server advertises agent_auth.skill https://alpic.ai/auth.md, register_uri https://api.alpic.ai/agent/auth, assertion types urn:ietf:params:oauth:token-type:id-jag and urn:ietf:params:oauth:token-type:jwt, and credential type api_key."
 },
 {
  "id": "amazon-bedrock",
  "org_id": "amazon",
  "name": "Amazon Bedrock",
  "url": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Amazon Bedrock",
    "role": "Inference API",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-22",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-22",
    "col4_md": "Supports the Responses API format on `bedrock-runtime` and `bedrock-mantle` (streaming and non-streaming; launched December 2025); AWS joined AAIF in support of Open Responses on October 22, 2026. Anthony Liguori (Amazon) is an initial TSC voting member.",
    "full_detail_md": "AWS says Amazon Bedrock has supported the Responses API since December 2025 and already supports it across dozens of models, with streaming and non-streaming modes on bedrock-runtime and bedrock-mantle, in a post dated 22 OCT 2026. The New Stack lists AWS (in Bedrock) among projects supporting the spec. Anthony Liguori (Amazon) is an initial TSC voting member.",
    "facets": {
     "endpoint_or_route": "bedrock-runtime and bedrock-mantle",
     "streaming_or_items": "streaming and non-streaming modes",
     "tool_or_state_model": "Responses API format across dozens of models; the post does not name previous_response_id",
     "sdk_or_version": "Responses API supported since December 2025; Open Responses AAIF post dated 22 OCT 2026"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/",
  "note": "Supports the Responses API format on `bedrock-runtime` and `bedrock-mantle` (streaming and non-streaming; launched December 2025); AWS joined AAIF in support of Open Responses on October 22, 2026. Anthony Liguori (Amazon) is an initial TSC voting member."
 },
 {
  "id": "amazon-bedrock-agentcore",
  "org_id": "amazon",
  "name": "Amazon Bedrock AgentCore Runtime",
  "url": "https://aws.amazon.com/bedrock/agentcore/",
  "type": "origin",
  "implements": [
   "a2a",
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AWS (Bedrock AgentCore Runtime)",
    "role": "Managed agent runtime",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2025-11-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-11",
    "col4_md": "November 2025 blog announces container runtime (`port 9000`) proxying `JSON-RPC 2.0` and authenticated `/.well-known/agent-card.json`.",
    "full_detail_md": "AWS's 11 November 2025 Machine Learning Blog announcement and walkthrough describes Amazon Bedrock AgentCore Runtime hosting stateless A2A server containers on `port 9000` as a transparent proxy for `JSON-RPC 2.0` over HTTP/S or Server-Sent Events, serving authenticated Agent Cards at `/.well-known/agent-card.json` and enforcing inbound AWS SigV4 or OAuth 2.0 authentication via AgentCore Identity.",
    "facets": {
     "transport_bindings": "JSON-RPC 2.0 over HTTP/S or Server-Sent Events (stateless container proxy on port 9000)",
     "discovery_artifact": "Authenticated Agent Card at /.well-known/agent-card.json",
     "protocol_version": "Pre-v1.0 era announcement (published 2025-11-11)",
     "auth_schemes": "Inbound AWS SigV4 and OAuth 2.0 (Amazon Cognito / AgentCore Identity); outbound IAM execution roles",
     "verification_posture": "Vendor release announcement and architecture walkthrough (2025-11-11)"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/machine-learning/introducing-agent-to-agent-protocol-support-in-amazon-bedrock-agentcore-runtime/"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Amazon Bedrock AgentCore Runtime",
    "role": "Agent server",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-13",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-13",
    "col4_md": "Port `8080`: `/invocations` HTTP/SSE and `/ws` WebSocket; runtime auth is `SigV4` or `OAuth 2.0`.",
    "full_detail_md": "Amazon Bedrock AgentCore expects AG-UI containers on port 8080, with `/invocations` for HTTP/SSE and `/ws` for WebSocket, and the runtime handles authentication (`SigV4` / `OAuth 2.0`), session isolation, and scaling. What's New records the 2026-03-13 announcement that Amazon Bedrock AgentCore Runtime now supports the AG-UI protocol, and the AG-UI overview lists AWS Bedrock AgentCore as Supported.",
    "facets": {
     "transport": "HTTP/SSE at /invocations and WebSocket at /ws, container port 8080",
     "event_or_state_model": "AG-UI event stream over HTTP/SSE or WebSocket",
     "integration_role": "Managed agent server runtime",
     "sdk_or_package": "AgentCore container; SigV4 or OAuth 2.0 (no separate SDK named)"
    },
    "telemetry": null,
    "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-agui.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://aws.amazon.com/blogs/machine-learning/introducing-agent-to-agent-protocol-support-in-amazon-bedrock-agentcore-runtime/",
  "note": "November 2025 blog announces container runtime (`port 9000`) proxying `JSON-RPC 2.0` and authenticated `/.well-known/agent-card.json`."
 },
 {
  "id": "amazon-bedrock-agentcore-browser",
  "org_id": "amazon-bedrock-agentcore-browser",
  "name": "Amazon Bedrock AgentCore Browser",
  "url": "https://aws.amazon.com/blogs/machine-learning/reduce-captchas-for-ai-agents-browsing-the-web-with-web-bot-auth-preview-in-amazon-bedrock-agentcore-browser/",
  "type": "agent",
  "implements": [
   "web-bot-auth-signature-agent-card"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "web-bot-auth-signature-agent-card",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Amazon Bedrock AgentCore Browser",
    "role": "Bot / Agent signer",
    "status": "Experimental",
    "status_display": "Experimental · as of 2025-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-30",
    "col4_md": "Web Bot Auth preview in AgentCore Browser, announced 2025-10-30, signs browsing traffic so the agent is presented as a verified bot on domains that allow verified bots. AWS says that after the protocol is finalized, AgentCore will move from the shared service key to customer-specific keys. Regional AgentCore signer endpoints are among the 500 URLs in the Cloudflare Radar registry.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/machine-learning/reduce-captchas-for-ai-agents-browsing-the-web-with-web-bot-auth-preview-in-amazon-bedrock-agentcore-browser/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://aws.amazon.com/blogs/machine-learning/reduce-captchas-for-ai-agents-browsing-the-web-with-web-bot-auth-preview-in-amazon-bedrock-agentcore-browser/",
  "note": "Web Bot Auth preview in AgentCore Browser, announced 2025-10-30, signs browsing traffic so the agent is presented as a verified bot on domains that allow verified bots. AWS says that after the protocol is finalized, AgentCore will move from the shared service key to customer-specific keys. Regional AgentCore signer endpoints are among the 500 URLs in the Cloudflare Radar registry."
 },
 {
  "id": "amazon-bedrock-agentcore-runtime",
  "org_id": "amazon",
  "name": "Amazon Bedrock AgentCore Runtime",
  "url": "https://builder.aws.com/content/3KumnpioszB60y33kJPJogaYsK1/what-are-mcp-apps-building-apps-that-run-on-claude-and-chatgpt",
  "type": "origin",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Amazon Bedrock AgentCore Runtime",
    "role": "MCP server runtime",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-10-19",
    "col4_md": "Oct 19, 2026 AWS employee article describes deploying an MCP Apps server to Amazon Bedrock AgentCore Runtime, with the UI rendered in Claude Desktop or ChatGPT.",
    "full_detail_md": "Ashita, an AWS employee, published an AWS Builder Center article on Oct 19, 2026. It says MCP Apps let an MCP server deliver rich, bidirectional HTML UIs such as interactive dashboards, data-collection forms, and real-time visualizations, rendered inside an AI host such as Claude Desktop or ChatGPT. The article deploys the TypeScript MCP server to Amazon Bedrock AgentCore Runtime.",
    "facets": {
     "transport_or_channel": "MCP server deployed to Amazon Bedrock AgentCore Runtime",
     "ui_resource_or_primitive": "Interactive HTML UI rendered in Claude Desktop or ChatGPT",
     "sandbox_or_security": "Article describes the UI rendered securely and natively inside the AI host",
     "sdk_or_version": "AWS Builder Center article by Ashita, an AWS employee, published Oct 19, 2026"
    },
    "telemetry": null,
    "source_url": "https://builder.aws.com/content/3KumnpioszB60y33kJPJogaYsK1/what-are-mcp-apps-building-apps-that-run-on-claude-and-chatgpt"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://builder.aws.com/content/3KumnpioszB60y33kJPJogaYsK1/what-are-mcp-apps-building-apps-that-run-on-claude-and-chatgpt",
  "note": "Oct 19, 2026 AWS employee article describes deploying an MCP Apps server to Amazon Bedrock AgentCore Runtime, with the UI rendered in Claude Desktop or ChatGPT."
 },
 {
  "id": "amazon-nova-act",
  "org_id": "amazon",
  "name": "Amazon Nova Act",
  "url": "https://aws.amazon.com/blogs/architecture/build-adaptive-ai-interfaces-with-the-ag-ui-protocol-agent-swarms-and-nova-act-on-aws/",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Amazon Nova Act",
    "role": "Reference architecture",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-09-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-09-29",
    "col4_md": "29 SEP 2026 Architecture Blog post shows adaptive interfaces built with the AG-UI protocol, the Strands Agents SDK Swarm pattern, and Amazon Nova Act.",
    "full_detail_md": "Anand Bilgaiyan and Renjith Pillai, AWS Architecture Blog, 29 SEP 2026, show how to build interfaces that adapt to variable agent outputs by using the AG-UI protocol, the Strands Agents SDK, and Amazon Nova Act. The post uses the Strands Agents SDK Swarm pattern for multi-agent collaboration and Amazon Nova Act for legacy system integration.",
    "facets": {
     "transport": "AG-UI protocol for dynamic UI generation",
     "event_or_state_model": "Adaptive interfaces for variable agent outputs",
     "integration_role": "Reference architecture with Strands Agents SDK Swarm and Amazon Nova Act",
     "sdk_or_package": "Strands Agents SDK"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/architecture/build-adaptive-ai-interfaces-with-the-ag-ui-protocol-agent-swarms-and-nova-act-on-aws/"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://aws.amazon.com/blogs/architecture/build-adaptive-ai-interfaces-with-the-ag-ui-protocol-agent-swarms-and-nova-act-on-aws/",
  "note": "29 SEP 2026 Architecture Blog post shows adaptive interfaces built with the AG-UI protocol, the Strands Agents SDK Swarm pattern, and Amazon Nova Act."
 },
 {
  "id": "amazonbot",
  "org_id": "amazon",
  "name": "Amazonbot",
  "url": "https://developer.amazon.com/docs/amazonbot/amazonbot.html",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Amazon",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-26",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-26",
    "col4_md": "`Amazonbot` crawls for service improvement and AI training; `Amzn-SearchBot` indexes Alexa search; `Amzn-User` serves live user requests.",
    "full_detail_md": "`Amazonbot` may be used to train Amazon AI models. `Amzn-SearchBot` improves search experiences such as Alexa and does not crawl content for generative AI model training. `Amzn-User` fetches live pages for user actions, may not follow all robots.txt directives, and does not crawl content for generative AI model training.",
    "facets": {
     "user_agent_token": [
      "Amazonbot",
      "Amzn-SearchBot",
      "Amzn-User"
     ],
     "operator_purpose": "Amazonbot: service improvement and AI model training; Amzn-SearchBot: search (no generative training); Amzn-User: user-initiated fetches",
     "ip_verification_url": "https://developer.amazon.com/docs/amazonbot/amazonbot.html",
     "robots_directives_honored": "Amazonbot and Amzn-SearchBot honor robots.txt; Amzn-User may not follow all robots.txt directives"
    },
    "telemetry": null,
    "source_url": "https://developer.amazon.com/docs/amazonbot/amazonbot.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developer.amazon.com/docs/amazonbot/amazonbot.html",
  "note": "`Amazonbot` crawls for service improvement and AI training; `Amzn-SearchBot` indexes Alexa search; `Amzn-User` serves live user requests."
 },
 {
  "id": "american-association-for-the-advancement-of-science",
  "org_id": "american-association-for-the-advancement-of-science",
  "name": "American Association for the Advancement of Science",
  "url": "https://www.science.org",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "American Association for the Advancement of Science",
    "role": "Publisher",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Adopters list: American Association for the Advancement of Science (https://www.science.org): as tdmrep.json, with a policy.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md",
  "note": "Adopters list: American Association for the Advancement of Science (https://www.science.org): as tdmrep.json, with a policy."
 },
 {
  "id": "american-chemical-society",
  "org_id": "american-chemical-society",
  "name": "American Chemical Society",
  "url": "https://pubs.acs.org/",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "American Chemical Society",
    "role": "Publisher",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Adopters list: American Chemical Society (https://pubs.acs.org/): as tdmrep.json, with a policy.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md",
  "note": "Adopters list: American Chemical Society (https://pubs.acs.org/): as tdmrep.json, with a policy."
 },
 {
  "id": "amp",
  "org_id": "amp",
  "name": "Amp",
  "url": "https://ampcode.com/news/agent-skills",
  "type": "harness",
  "implements": [
   "agents-md",
   "anthropic-agent-skills-format",
   "oauth-cimd"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Amp",
    "role": "Coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-10",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-10",
    "col4_md": "Lazily loads skill instructions from workspace `.agents/skills/`, `~/.config/agents/skills/`, `.claude/skills/`, and `~/.claude/skills/` since `2025-12-10`.",
    "full_detail_md": "In its `2025-12-10` release note, Amp announced support for lazily loading Agent Skills from workspace `.agents/skills/`, user-level `~/.config/agents/skills/`, and Claude compatibility paths (`.claude/skills/` and `~/.claude/skills/`) to teach local tools such as `Agent Sandbox`, `BigQuery`, and `Tmux`.",
    "facets": {
     "transport_or_packaging": "Workspace (.agents/skills/), user (~/.config/agents/skills/), and Claude compatibility (.claude/skills/, ~/.claude/skills/) directories",
     "manifest_or_entry": "Skill directories lazily loaded for local tool workflows",
     "execution_or_sandbox": "Lazy-loaded tool instructions; optional isolated agent sandbox skill for untrusted code",
     "verification_posture": "First-party Amp release note (2025-12-10, checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://ampcode.com/news/agent-skills"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Amp",
    "role": "Coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2025-08-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-08-20",
    "col4_md": "Adopted `AGENTS.md` as standard filename on 2025-08-20 with glob mentions and `AGENT.md` backward compatibility.",
    "full_detail_md": "Switched its standard instruction filename from singular `AGENT.md` (introduced May 2025) to plural `AGENTS.md` on 2025-08-20 after OpenAI secured the `agents.md` domain, retaining backward compatibility with existing `AGENT.md` files and supporting dynamic context inclusion via glob mentions and filters.",
    "facets": {
     "discovery_behavior": "Automatic repository scan for AGENTS.md with dynamic glob mentions and filters",
     "hierarchy_precedence": "Standard AGENTS.md lookup with backward compatibility for legacy singular AGENT.md",
     "fallback_files": "AGENT.md",
     "verification_posture": "Documented in Amp 2025-08-20 release announcement"
    },
    "telemetry": null,
    "source_url": "https://ampcode.com/news/AGENTS.md"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Amp",
    "role": "OAuth client",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Supports CIMD, and falls back to dynamic client registration when CIMD is absent.",
    "full_detail_md": "Amp's MCP documentation says Amp supports Client ID Metadata Documents and falls back to dynamic client registration for servers that do not support CIMD. The `amp mcp oauth` commands manage that local OAuth state.",
    "facets": {
     "metadata_flag_or_profile": "Product documentation states CIMD support with dynamic-client-registration fallback; the page does not quote a hosted client metadata URL",
     "auth_method_or_pkce": "Not specified on the Amp MCP page beyond CIMD, with dynamic registration when the server does not support CIMD",
     "uri_or_ssrf_rules": "Not specified on the Amp MCP page",
     "draft_or_spec_version": "Undated Amp MCP documentation; the page does not name a CIMD draft revision, and the grade is not taken from a floating main-branch source file"
    },
    "telemetry": null,
    "source_url": "https://ampcode.com/docs/customize/mcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://ampcode.com/news/agent-skills",
  "note": "Lazily loads skill instructions from workspace `.agents/skills/`, `~/.config/agents/skills/`, `.claude/skills/`, and `~/.claude/skills/` since `2025-12-10`."
 },
 {
  "id": "ample-computer",
  "org_id": "ample-computer",
  "name": "Ample Computer",
  "url": "https://api.ample.computer/.well-known/poppy.json",
  "type": "origin",
  "implements": [
   "personal-agent-protocol"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "personal-agent-protocol",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Ample Computer",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "https://api.ample.computer/.well-known/poppy.json, seen 2026-10-29, is protocol_version 0.1 with organization.name Ample Computer. Implementation report filed 2026-10-17 says the company has been live on Draft 0.1 since 2026-10-17. Ample Computer is a cloud for apps that AI agents deploy.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json"
    },
    "source_url": "https://api.ample.computer/.well-known/poppy.json"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://api.ample.computer/.well-known/poppy.json",
  "note": "https://api.ample.computer/.well-known/poppy.json, seen 2026-10-29, is protocol_version 0.1 with organization.name Ample Computer. Implementation report filed 2026-10-17 says the company has been live on Draft 0.1 since 2026-10-17. Ample Computer is a cloud for apps that AI agents deploy."
 },
 {
  "id": "anp-proxy",
  "org_id": "anp-proxy",
  "name": "ANP Proxy",
  "url": "https://raw.githubusercontent.com/agent-network-protocol/anp-proxy/main/README.md",
  "type": "sdk",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "ANP Proxy",
    "role": "Messaging node / Server",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "asyncio HTTP-over-WebSocket tunnel that exposes private ASGI agent services.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agent-network-protocol/anp-proxy/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/agent-network-protocol/anp-proxy/main/README.md",
  "note": "asyncio HTTP-over-WebSocket tunnel that exposes private ASGI agent services."
 },
 {
  "id": "anp-sdks",
  "org_id": "anp-sdks",
  "name": "ANP SDKs (anp, Rust anp, @awiki/anp-typescript-sdk)",
  "url": "https://pypi.org/pypi/anp/json",
  "type": "sdk",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "ANP SDKs (anp, Rust anp, @awiki/anp-typescript-sdk)",
    "role": "Client SDK / Runtime",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "PyPI anp 1.0.7 (identity authentication, end-to-end encrypted communication, LLM protocol negotiation, and data exchange), the Rust anp crate on crates.io, and npm @awiki/anp-typescript-sdk 0.9.5. Legacy PyPI package agent-connect remains published.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/anp/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://pypi.org/pypi/anp/json",
  "note": "PyPI anp 1.0.7 (identity authentication, end-to-end encrypted communication, LLM protocol negotiation, and data exchange), the Rust anp crate on crates.io, and npm @awiki/anp-typescript-sdk 0.9.5. Legacy PyPI package agent-connect remains published."
 },
 {
  "id": "ant-international",
  "org_id": "ant-international",
  "name": "Ant International (Alipay+ network)",
  "url": "https://www.ant-intl.com/en/news/detail/ant-international-launches-open-sourced-agentic-mobile-protocol-to-drive-ai-commerce/",
  "type": "venue",
  "implements": [
   "amp-ant"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "amp-ant",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Ant International (Alipay+ network)",
    "role": "Payment network (Originator)",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Alipay+ clearing & settlement rail; 3-layer SD-JWT mandates (Immediate & Autonomous) and >24-bit CGCP one-time Payment Tokens",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.ant-intl.com/en/news/detail/ant-international-launches-open-sourced-agentic-mobile-protocol-to-drive-ai-commerce/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.ant-intl.com/en/news/detail/ant-international-launches-open-sourced-agentic-mobile-protocol-to-drive-ai-commerce/",
  "note": "Alipay+ clearing & settlement rail; 3-layer SD-JWT mandates (Immediate & Autonomous) and >24-bit CGCP one-time Payment Tokens"
 },
 {
  "id": "ant-international-amp-python-libraries",
  "org_id": "ant-international-amp-python-libraries",
  "name": "Ant International AMP Python Libraries (mandate_chain, schemas, common)",
  "url": "https://raw.githubusercontent.com/ant-intl/AMP/main/README.md",
  "type": "sdk",
  "implements": [
   "amp-ant"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "amp-ant",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Ant International AMP Python Libraries (`mandate_chain`, `schemas`, `common`)",
    "role": "Reference SDK (Originator)",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Python libraries for 3-layer SD-JWT mandate generation, validation, and AMP message schemas",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/ant-intl/AMP/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/ant-intl/AMP/main/README.md",
  "note": "Python libraries for 3-layer SD-JWT mandate generation, validation, and AMP message schemas"
 },
 {
  "id": "ant-international-reference-shopping-agent",
  "org_id": "ant-international-reference-shopping-agent",
  "name": "Ant International Reference Shopping Agent (ant-intl/AMP)",
  "url": "https://raw.githubusercontent.com/ant-intl/AMP/main/README.md",
  "type": "agent",
  "implements": [
   "amp-ant"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "amp-ant",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Ant International Reference Shopping Agent (`ant-intl/AMP`)",
    "role": "Reference agent (Originator)",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Local reference shopping agent driving `search → checkout → mandate → credential → pay` backed by per-run `.temp-db/` SQLite/JSON stores",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/ant-intl/AMP/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/ant-intl/AMP/main/README.md",
  "note": "Local reference shopping agent driving `search → checkout → mandate → credential → pay` backed by per-run `.temp-db/` SQLite/JSON stores"
 },
 {
  "id": "anthropic",
  "org_id": "anthropic",
  "name": "Anthropic (Claude Platform)",
  "url": "https://platform.claude.com/.well-known/ai-catalog.json",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Anthropic (Claude Platform)",
    "role": "Docs platform",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Level 2 catalog at `/.well-known/ai-catalog.json` with `Content-Type: application/ai-catalog+json`, advertising the docs MCP Server Card `urn:air:platform.claude.com:mcp:docs` at `https://platform.claude.com/docs/mcp/server-card`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://platform.claude.com/.well-known/ai-catalog.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://platform.claude.com/.well-known/ai-catalog.json",
  "note": "Level 2 catalog at `/.well-known/ai-catalog.json` with `Content-Type: application/ai-catalog+json`, advertising the docs MCP Server Card `urn:air:platform.claude.com:mcp:docs` at `https://platform.claude.com/docs/mcp/server-card`."
 },
 {
  "id": "anthropic-claude-platform",
  "org_id": "anthropic",
  "name": "Claude Platform",
  "url": "https://platform.claude.com/docs/en/manage-claude/workload-identity-federation",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Anthropic Claude Platform",
    "role": "Relying server / Gateway",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-11",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": null,
    "col4_md": "Accepts SPIFFE JWT-SVIDs from SPIRE or another conformant issuer and returns a short-lived Anthropic access token for the Claude API.",
    "full_detail_md": "Claude Platform Workload Identity Federation accepts workloads with SPIFFE JWT-SVIDs from SPIRE or another conformant issuer. The workload presents a signed JWT from its identity provider. Anthropic validates it against trust rules configured in the Claude Console and returns a short-lived Anthropic access token bound to a service account for the Claude API. SPIFFE is listed among standards-compliant OIDC issuers, with Kubernetes, Microsoft Entra ID, and Okta.",
    "facets": {
     "svid_or_bundle_format": "Inbound SPIFFE JWT-SVID from SPIRE or another conformant issuer.",
     "api_or_federation_surface": "Workload Identity Federation into the Claude API. Anthropic returns a short-lived access token bound to a service account.",
     "attestation_or_trust_domain": "Anthropic validates the signed JWT against trust rules configured in the Claude Console.",
     "verification_posture": "Claude Platform documentation lists SPIFFE as a supported OIDC issuer for Workload Identity Federation."
    },
    "telemetry": null,
    "source_url": "https://platform.claude.com/docs/en/manage-claude/workload-identity-federation"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "recorded",
  "source": "https://platform.claude.com/docs/en/manage-claude/workload-identity-federation",
  "note": "Accepts SPIFFE JWT-SVIDs from SPIRE or another conformant issuer and returns a short-lived Anthropic access token for the Claude API."
 },
 {
  "id": "anthropic-crawlers",
  "org_id": "anthropic",
  "name": "Anthropic crawlers",
  "url": "https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Anthropic",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-07",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-07",
    "col4_md": "`ClaudeBot` collects model training data; `Claude-SearchBot` indexes search results; `Claude-User` fetches pages for user queries.",
    "full_detail_md": "`ClaudeBot` collects web content that could contribute to training generative AI models. `Claude-User` supports user-initiated requests to Claude. `Claude-SearchBot` navigates the web to improve search result quality. Restricting each token is a separate control.",
    "facets": {
     "user_agent_token": [
      "ClaudeBot",
      "Claude-User",
      "Claude-SearchBot"
     ],
     "operator_purpose": "ClaudeBot: generative AI training; Claude-SearchBot: search result quality; Claude-User: user-initiated requests",
     "ip_verification_url": "https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler",
     "robots_directives_honored": "Separate robots.txt control per user-agent token"
    },
    "telemetry": null,
    "source_url": "https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler",
  "note": "`ClaudeBot` collects model training data; `Claude-SearchBot` indexes search results; `Claude-User` fetches pages for user queries."
 },
 {
  "id": "anthropic-ema-partner-cohort",
  "org_id": "anthropic",
  "name": "Enterprise-Managed Authorization launch partner cohort",
  "url": "https://claude.com/resources/articles/enterprise-managed-auth",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Asana, Canva, Datadog, Granola, Slack & Supabase (Anthropic EMA partner cohort)",
    "role": "Enterprise MCP connectors",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-24",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-24",
    "col4_md": "Anthropic's August 24, 2026 Enterprise-Managed Authorization announcement states that enterprise-managed authorization supports Datadog, Notion, and Slack alongside existing support for Asana, Atlassian, Box, Canva, Figma, Granola, Linear, Lovable, and Supabase (with Notion, Linear, Figma, Lovable, and Atlassian documented separately in rows above, while Box is named only on the protocol landing page).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://claude.com/resources/articles/enterprise-managed-auth"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://claude.com/resources/articles/enterprise-managed-auth",
  "note": "Anthropic's August 24, 2026 Enterprise-Managed Authorization announcement states that enterprise-managed authorization supports Datadog, Notion, and Slack alongside existing support for Asana, Atlassian, Box, Canva, Figma, Granola, Linear, Lovable, and Supabase (with Notion, Linear, Figma, Lovable, and Atlassian documented separately in rows above, while Box is named only on the protocol landing p"
 },
 {
  "id": "ap2-python-sdk",
  "org_id": "google-agentic-commerce",
  "name": "AP2 Python package",
  "url": "https://github.com/google-agentic-commerce/AP2",
  "type": "sdk",
  "implements": [
   "ap2"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ap2",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "google-agentic-commerce/AP2 Python package",
    "role": "Client SDK",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The repository defines the protocol's core objects under `code/sdk/python/ap2/`, with Pydantic models and canonical JSON schemas. A PyPI package will be published at a later time; until then the documented install is `uv pip install git+https://github.com/google-agentic-commerce/AP2.git@main`. The FAQ says sample agents were built around the core AP2 python library, that those samples mock actual payment service providers, and that an SDK and a MCP server are still in progress with payment service providers. That FAQ names the Checkout Mandate and the Payment Mandate as verifiable credentials.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/google-agentic-commerce/AP2"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/google-agentic-commerce/AP2",
  "note": "The repository defines the protocol's core objects under `code/sdk/python/ap2/`, with Pydantic models and canonical JSON schemas. A PyPI package will be published at a later time; until then the documented install is `uv pip install git+https://github.com/google-agentic-commerce/AP2.git@main`. The FAQ says sample agents were built around the core AP2 python library, that those samples mock actual "
 },
 {
  "id": "apify",
  "org_id": "apify",
  "name": "Apify",
  "url": "https://docs.apify.com/integrations/skyfire",
  "type": "venue",
  "implements": [
   "kyapay-token"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Apify",
    "role": "Seller",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Accepts and charges Skyfire `PAY` tokens passed in the legacy `skyfire-pay-id` HTTP header for Actor compute usage (marked experimental in Apify docs)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.apify.com/integrations/skyfire"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.apify.com/integrations/skyfire",
  "note": "Accepts and charges Skyfire `PAY` tokens passed in the legacy `skyfire-pay-id` HTTP header for Actor compute usage (marked experimental in Apify docs)"
 },
 {
  "id": "apify-as-meta",
  "org_id": "apify",
  "name": "Apify MCP authorization server",
  "url": "https://mcp.apify.com",
  "type": "authority",
  "implements": [
   "oauth-cimd",
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Apify",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`issuer` `https://console-backend.apify.com` (mismatches `https://mcp.apify.com`, so RFC 8414 §3.3 requires a client probing `https://mcp.apify.com` to reject this document and instead resolve metadata for the issuer named in protected-resource metadata); `S256`; `device_code`; `client_id_metadata_document_supported` `true`.",
    "full_detail_md": "GET https://mcp.apify.com/.well-known/oauth-authorization-server returned HTTP 200 `application/json` with `issuer` `https://console-backend.apify.com`. Under RFC 8414 Section 3.3, the returned `issuer` value must be identical to the issuer identifier used to construct the well-known URI, otherwise the response must not be used; a client that built this URL from `https://mcp.apify.com` must therefore reject the document, and if protected-resource metadata names `https://console-backend.apify.com`, the client instead resolves the well-known metadata URL for `https://console-backend.apify.com` and applies the same issuer check there. `registration_endpoint` is `https://console-backend.apify.com/oauth/apps` and `client_id_metadata_document_supported` is `true`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.apify.com/.well-known/oauth-authorization-server whose issuer is https://console-backend.apify.com (authorization_endpoint https://console.apify.com/authorize/oauth; registration_endpoint https://console-backend.apify.com/oauth/apps)",
     "registration_or_client_id_modes": "registration_endpoint on console-backend.apify.com; client_id_metadata_document_supported true; token_endpoint_auth_methods client_secret_basic, client_secret_post, none, private_key_jwt (RS256, RS384, RS512)",
     "pkce_or_grant_types": "PKCE S256; grants authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:device_code",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03); issuer host differs from the well-known URI host, so RFC 8414 issuer binding is only partial"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://console-backend.apify.com",
     "client_id_metadata_document_supported": true
    },
    "source_url": "https://mcp.apify.com/.well-known/oauth-authorization-server"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Apify",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; CIMD flag true; `issuer` is `https://console-backend.apify.com`.",
    "full_detail_md": "The HTTP 200 document sets `client_id_metadata_document_supported` true and `issuer` `https://console-backend.apify.com`, a different host from the metadata URL on `mcp.apify.com`. `code_challenge_methods_supported` is `S256`, `grant_types_supported` includes `authorization_code`, `refresh_token`, and `urn:ietf:params:oauth:grant-type:device_code`, `scopes_supported` is `full_api_access`, authorization is `https://console.apify.com/authorize/oauth`, and registration is `https://console-backend.apify.com/oauth/apps`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "client_id_metadata_document_supported true; issuer https://console-backend.apify.com differs from the mcp.apify.com metadata host",
     "auth_method_or_pkce": "code_challenge_methods_supported S256; grant_types_supported authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:device_code; token_endpoint_auth_methods include none and private_key_jwt",
     "uri_or_ssrf_rules": "authorization_endpoint https://console.apify.com/authorize/oauth; token and registration endpoints are on console-backend.apify.com",
     "draft_or_spec_version": "Live authorization-server metadata checked 2026-10-30; the JSON does not name a CIMD draft revision. This is not an MCP registry server.json record"
    },
    "telemetry": {
     "http_status": 200,
     "client_id_metadata_document_supported": true,
     "issuer": "https://console-backend.apify.com"
    },
    "source_url": "https://mcp.apify.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.apify.com/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://console-backend.apify.com` (mismatches `https://mcp.apify.com`, so RFC 8414 §3.3 requires a client probing `https://mcp.apify.com` to reject this document and instead resolve metadata for the issuer named in protected-resource metadata); `S256`; `device_code`; `client_id_metadata_document_supported` `true`."
 },
 {
  "id": "applebot-extended",
  "org_id": "apple",
  "name": "Applebot-Extended",
  "url": "https://support.apple.com/en-us/119829",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Apple",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-04",
    "col4_md": "Disallowing `Applebot-Extended` opts out of generative model training while keeping `Applebot` active for Spotlight, Siri, and Safari search.",
    "full_detail_md": "Publishers opt out of training generative foundation models by disallowing `Applebot-Extended` in robots.txt. Disallowing `Applebot-Extended` does not by itself stop `Applebot` from crawling, so content can stay discoverable in Spotlight, Siri, and Safari.",
    "facets": {
     "user_agent_token": [
      "Applebot-Extended",
      "Applebot"
     ],
     "operator_purpose": "Applebot-Extended: generative foundation model training opt-out; Applebot: Spotlight, Siri, and Safari search crawling",
     "ip_verification_url": "https://support.apple.com/en-us/119829",
     "robots_directives_honored": "Disallowing Applebot-Extended in robots.txt opts out of generative training without blocking Applebot"
    },
    "telemetry": null,
    "source_url": "https://support.apple.com/en-us/119829"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://support.apple.com/en-us/119829",
  "note": "Disallowing `Applebot-Extended` opts out of generative model training while keeping `Applebot` active for Spotlight, Siri, and Safari search."
 },
 {
  "id": "archestra-ai",
  "org_id": "archestra-ai",
  "name": "Archestra.AI",
  "url": "https://modelcontextprotocol.io/extensions/apps/overview",
  "type": "harness",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Archestra.AI",
    "role": "AI host",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Named among supported MCP Apps hosts on the official MCP Apps overview.",
    "full_detail_md": "The MCP Apps overview page lists Archestra.AI among the clients that currently support MCP Apps alongside Claude, Claude Desktop, VS Code GitHub Copilot, Microsoft 365 Copilot, Goose, Postman, and MCPJam.",
    "facets": {
     "transport_or_channel": "Listed MCP Apps host on modelcontextprotocol.io",
     "ui_resource_or_primitive": "MCP Apps host support listed on the official overview page",
     "sandbox_or_security": "Overview listing does not specify host-specific sandbox flags",
     "sdk_or_version": "Undated MCP Apps overview page"
    },
    "telemetry": null,
    "source_url": "https://modelcontextprotocol.io/extensions/apps/overview"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://modelcontextprotocol.io/extensions/apps/overview",
  "note": "Named among supported MCP Apps hosts on the official MCP Apps overview."
 },
 {
  "id": "arize-ax-openinference",
  "org_id": "arize",
  "name": "Arize AX",
  "url": "https://arize.com/docs/ax/observe/tracing/openinference-semantic-conventions",
  "type": "origin",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Arize AX",
    "role": "OpenInference mapping",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Arize AX preserves raw `gen_ai.*` attributes. An explicit OpenInference attribute wins, so `gen_ai.request.model` does not overwrite an existing `llm.model_name`. Span kind is inferred from `gen_ai.operation.name`. An unrecognized operation leaves the span kind unset.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://arize.com/docs/ax/observe/tracing/openinference-semantic-conventions"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://arize.com/docs/ax/observe/tracing/openinference-semantic-conventions",
  "note": "Arize AX preserves raw `gen_ai.*` attributes. An explicit OpenInference attribute wins, so `gen_ai.request.model` does not overwrite an existing `llm.model_name`. Span kind is inferred from `gen_ai.operation.name`. An unrecognized operation leaves the span kind unset."
 },
 {
  "id": "asana-as-meta",
  "org_id": "asana",
  "name": "Asana MCP authorization server",
  "url": "https://mcp.asana.com",
  "type": "authority",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Asana",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`issuer` `https://mcp.asana.com`; PKCE `plain` and `S256`; `authorization_code`, `refresh_token`; `registration_endpoint`.",
    "full_detail_md": "GET https://mcp.asana.com/.well-known/oauth-authorization-server returned HTTP 200 `application/json`. `issuer` is `https://mcp.asana.com`. `authorization_endpoint`, `token_endpoint`, and `registration_endpoint` are on that host. `grant_types_supported` are `authorization_code` and `refresh_token`. `code_challenge_methods_supported` are `plain` and `S256`. `token_endpoint_auth_methods_supported` includes `none`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.asana.com/.well-known/oauth-authorization-server (issuer https://mcp.asana.com; authorization, token, and registration endpoints on that host)",
     "registration_or_client_id_modes": "registration_endpoint https://mcp.asana.com/register; token_endpoint_auth_methods_supported includes none, client_secret_basic, and client_secret_post; client_id_metadata_document_supported not declared",
     "pkce_or_grant_types": "PKCE plain and S256; grant_types_supported authorization_code and refresh_token",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://mcp.asana.com"
    },
    "source_url": "https://mcp.asana.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.asana.com/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://mcp.asana.com`; PKCE `plain` and `S256`; `authorization_code`, `refresh_token`; `registration_endpoint`."
 },
 {
  "id": "atlassian-a2ui",
  "org_id": "atlassian",
  "name": "Atlassian",
  "url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "type": "harness",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Atlassian",
    "role": "Product host",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-11-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-11-11",
    "col4_md": "Atlassian is bringing A2UI to Jira, where teams can assign work items to AI agents, and is named among companies already building with A2UI.",
    "full_detail_md": "The NOV. 11, 2026 Google Developers Blog says Atlassian is bringing A2UI to Jira. When an agent needs a follow-up to finish a work item, it asks with an interactive card in the work item.",
    "facets": {
     "transport_or_binding": "Interactive A2UI card inside a Jira work item",
     "component_or_catalog": "Follow-up card in the work item",
     "spec_version": "Named in the A2UI 1.0 public-release announcement",
     "sdk_or_renderer": "Jira work-item card"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "note": "Atlassian is bringing A2UI to Jira, where teams can assign work items to AI agents, and is named among companies already building with A2UI."
 },
 {
  "id": "atlassian-mcp",
  "org_id": "atlassian",
  "name": "Atlassian Rovo MCP Server",
  "url": "https://mcp.atlassian.com/v2/mcp",
  "type": "origin",
  "implements": [
   "mcp",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Atlassian Rovo",
    "role": "Remote MCP server",
    "status": "Listed",
    "status_display": "Listed · as of 2026-09-09",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-09",
    "col4_md": "Registry entry `com.atlassian/atlassian-mcp-server` (`2.0.0`) advertising `streamable-http` at `https://mcp.atlassian.com/v2/mcp` and `https://mcp.atlassian.com/v1/mcp/authv2`.",
    "full_detail_md": "Published in the Official MCP Registry as `com.atlassian/atlassian-mcp-server` v`2.0.0` (Atlassian Rovo MCP Server), declaring `streamable-http` remote endpoints at `https://mcp.atlassian.com/v2/mcp` and `https://mcp.atlassian.com/v1/mcp/authv2` for Jira, Confluence, and Loom workflows.",
    "facets": {
     "transport": "streamable-http",
     "auth_or_oauth": "OAuth 2.1 (/v1/mcp/authv2)",
     "primitives": "tools",
     "sdk_or_package": "com.atlassian/atlassian-mcp-server v2.0.0"
    },
    "telemetry": null,
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/com.atlassian%2Fatlassian-mcp-server/versions/2.0.0"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Atlassian",
    "role": "Server publisher",
    "status": "Listed in Official Registry (HTTP 200 server.json)",
    "status_display": "Listed in Official Registry (HTTP 200 server.json) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-09",
    "col4_md": "`com.atlassian/atlassian-mcp-server` `2.0.0` (published 2026-09-09): remote `streamable-http` endpoint.",
    "full_detail_md": "HTTP 200 `application/json`. Latest `com.atlassian/atlassian-mcp-server` is version `2.0.0`, titled Atlassian Rovo MCP Server, on schema `2025-12-11`, with registry status `active` and `isLatest` true, published `2026-09-09`. Remotes are `streamable-http` at `https://mcp.atlassian.com/v2/mcp` and `https://mcp.atlassian.com/v1/mcp/authv2`.",
    "facets": {
     "registry_or_namespace": "com.atlassian/atlassian-mcp-server",
     "api_or_schema_version": "Record publishedAt 2026-09-09; validates against server.schema.json (2025-12-11).",
     "transport_or_package_types": "streamable-http remotes",
     "verification_posture": "HTTP 200 registry record probe (checked 2026-10-30, publishedAt 2026-09-09); proves registry metadata listing rather than live MCP server execution."
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "server_name": "com.atlassian/atlassian-mcp-server",
     "version": "2.0.0"
    },
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/com.atlassian%2Fatlassian-mcp-server/versions/2.0.0"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.modelcontextprotocol.io/v0.1/servers/com.atlassian%2Fatlassian-mcp-server/versions/2.0.0",
  "note": "Registry entry `com.atlassian/atlassian-mcp-server` (`2.0.0`) advertising `streamable-http` at `https://mcp.atlassian.com/v2/mcp` and `https://mcp.atlassian.com/v1/mcp/authv2`."
 },
 {
  "id": "atlassian-rovo-mcp",
  "org_id": "atlassian",
  "name": "Atlassian Rovo MCP",
  "url": "https://www.atlassian.com",
  "type": "origin",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Atlassian",
    "role": "Rovo MCP resource server",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Atlassian says it added Enterprise-Managed Authorization in the Atlassian Rovo MCP server using Cross-App Access (XAA) and the Identity Assertion JWT Authorization Grant (ID-JAG). This feature is currently in private beta. An admin can centrally authorize MCP access for approved clients like Claude.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.atlassian.com/blog/development/enterprise-managed-authorization-rovo-mcp-xaa-id-jag"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.atlassian.com/blog/development/enterprise-managed-authorization-rovo-mcp-xaa-id-jag",
  "note": "Atlassian says it added Enterprise-Managed Authorization in the Atlassian Rovo MCP server using Cross-App Access (XAA) and the Identity Assertion JWT Authorization Grant (ID-JAG). This feature is currently in private beta. An admin can centrally authorize MCP access for approved clients like Claude."
 },
 {
  "id": "atproto-oauth",
  "org_id": "bluesky",
  "name": "AT Protocol OAuth",
  "url": "https://atproto.com/specs/oauth",
  "type": "origin",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Bluesky, AT Protocol",
    "role": "OAuth client profile",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`client_id` is a public metadata URL; there is no shared `client_secret`.",
    "full_detail_md": "The published AT Protocol OAuth specification says the client_id is a fully-qualified web URL pointing at public client metadata JSON, and that there is no client_secret shared between servers and clients. The Bluesky OAuth proposal describes the authorization server loading that client metadata document from the client_id during an authorization request; the Supported grade follows the published spec, not that main-branch README.",
    "facets": {
     "metadata_flag_or_profile": "AT Protocol OAuth profile: client_id is a fully-qualified web URL of a public client metadata JSON document",
     "auth_method_or_pkce": "No client_secret is shared between servers and clients, per the published AT Protocol OAuth spec",
     "uri_or_ssrf_rules": "The client_id URL is fetched as the metadata document; the proposal says that load happens during an authorization request",
     "draft_or_spec_version": "Grade follows https://atproto.com/specs/oauth. The bluesky-social proposals main README is design history and is not graded Supported on its own"
    },
    "telemetry": null,
    "source_url": "https://atproto.com/specs/oauth"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://atproto.com/specs/oauth",
  "note": "`client_id` is a public metadata URL; there is no shared `client_secret`."
 },
 {
  "id": "auth-md-skill",
  "org_id": "auth-md",
  "name": "auth-md skill",
  "url": "https://auth-md.com/auth.md",
  "type": "sdk",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "auth-md skill",
    "role": "Agent skill",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "Generates and validates `auth.md` plus Protected Resource Metadata from codebase; static site hosts no registration endpoints.",
    "full_detail_md": "The `auth-md` skill generates a complete `auth.md` file and Protected Resource Metadata from a developer's codebase and validates existing `auth.md` files against the protocol specification, while `auth-md.com` itself is a static documentation site with no APIs, no protected resources, and no registration endpoints.",
    "facets": {
     "metadata_endpoints_served": "Skill generates a static auth.md file and Protected Resource Metadata from a developer's codebase; auth-md.com does not serve an OAuth metadata endpoint",
     "registration_or_client_id_modes": "auth-md.com has no registration endpoints; the skill validates an existing auth.md against the protocol specification",
     "pkce_or_grant_types": "Not declared; auth-md.com has no APIs and no protected resources",
     "verification_posture": "Documentation citation of https://auth-md.com/auth.md (checked 2026-10-31)"
    },
    "telemetry": null,
    "source_url": "https://auth-md.com/auth.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://auth-md.com/auth.md",
  "note": "Generates and validates `auth.md` plus Protected Resource Metadata from codebase; static site hosts no registration endpoints."
 },
 {
  "id": "auth0-cimd",
  "org_id": "auth0",
  "name": "Auth0",
  "url": "https://auth0.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Auth0",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Manual and dynamic CIMD registration; hosted document stays the source of truth.",
    "full_detail_md": "Auth0 supports manual CIMD and dynamic CIMD registration. Manual registration imports an application from its CIMD URL, and Auth0 fetches and validates the document; dynamic CIMD registration lets the application register itself via that URL. The hosted document remains the source of truth.",
    "facets": {
     "metadata_flag_or_profile": "Manual CIMD import from a URL, and dynamic CIMD registration; the hosted document remains the source of truth",
     "auth_method_or_pkce": "Auth0 fetches and validates the CIMD; the overview does not name a PKCE method",
     "uri_or_ssrf_rules": "Registration uses the application's CIMD URL; the overview does not state a separate SSRF rule",
     "draft_or_spec_version": "Undated Auth0 CIMD overview; it does not name a CIMD draft revision"
    },
    "telemetry": null,
    "source_url": "https://auth0.com/docs/get-started/auth0-overview/create-applications/cimd-overview"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://auth0.com/docs/get-started/auth0-overview/create-applications/cimd-overview",
  "note": "Manual and dynamic CIMD registration; hosted document stays the source of truth."
 },
 {
  "id": "auth0-cross-app-access",
  "org_id": "auth0",
  "name": "Auth0 Cross App Access",
  "url": "https://auth0.com",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Auth0",
    "role": "Cross App Access identity platform",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The changelog entry dated August 31, 2026 says Cross-App Access Requesting App is now in Early Access, and that Auth0 supports acting as a requesting application in Cross-App Access flows in Early Access. The blog dated 2026-08-06 says resource apps can expose APIs and MCP servers to trusted external agents with zero code changes, and that native requesting-app support was anticipated by August 31, 2026 through Token Vault.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://auth0.com/changelog"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://auth0.com/changelog",
  "note": "The changelog entry dated August 31, 2026 says Cross-App Access Requesting App is now in Early Access, and that Auth0 supports acting as a requesting application in Cross-App Access flows in Early Access. The blog dated 2026-08-06 says resource apps can expose APIs and MCP servers to trusted external agents with zero code changes, and that native requesting-app support was anticipated by August 31"
 },
 {
  "id": "awesome-ai-catalogs",
  "org_id": "awesome-ai-catalogs",
  "name": "Awesome AI Catalogs",
  "url": "https://raw.githubusercontent.com/Agent-Card/awesome-ai-catalogs/main/README.md",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Awesome AI Catalogs",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Working-group meta-catalog. `https://agent-card.github.io/awesome-ai-catalogs/ai-catalog.json` lists other public catalogs (Netlify, Buildkite, Railway, Fly.io, Supabase, Zapier, ClickHouse, and others). Each listed catalog is validated with the ai-catalog CLI.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/Agent-Card/awesome-ai-catalogs/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/Agent-Card/awesome-ai-catalogs/main/README.md",
  "note": "Working-group meta-catalog. `https://agent-card.github.io/awesome-ai-catalogs/ai-catalog.json` lists other public catalogs (Netlify, Buildkite, Railway, Fly.io, Supabase, Zapier, ClickHouse, and others). Each listed catalog is validated with the ai-catalog CLI."
 },
 {
  "id": "awesome-mpp",
  "org_id": "mbeato",
  "name": "Awesome MPP",
  "url": "https://github.com/mbeato/awesome-mpp",
  "type": "authority",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Awesome MPP",
    "role": "Community registry",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Curated list of MPP specifications, SDKs, and services.",
    "full_detail_md": "Community list of MPP specifications, SDKs, payment methods, framework integrations, and services beyond the single mpp.dev catalog page.",
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/mbeato/awesome-mpp"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/mbeato/awesome-mpp",
  "note": "Curated list of MPP specifications, SDKs, and services."
 },
 {
  "id": "aws-bedrock-agentcore",
  "org_id": "amazon",
  "name": "Amazon Bedrock AgentCore",
  "url": "https://aws.amazon.com/bedrock/agentcore/",
  "type": "origin",
  "implements": [
   "mpp",
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "AWS (Amazon Bedrock AgentCore payments)",
    "role": "Agent platform / runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-18",
    "col4_md": "GA runtime supporting x402 `exact` and `upto` with Coinbase/Privy USDC wallets and AgentCore Gateway MCP discovery.",
    "full_detail_md": "Generally available on August 18, 2026, Amazon Bedrock AgentCore payments equips agents to pay x402 endpoints using `exact` and `upto` schemes (alongside MPP) via Coinbase and Stripe Privy USDC wallets, enforcing infrastructure-layer session spend caps and exposing curated x402 endpoints as an MCP server through AgentCore Gateway.",
    "facets": {
     "settlement_rail": "Managed x402 (`exact` and `upto`) and MPP orchestration with Coinbase and Stripe Privy wallets",
     "supported_assets": "USDC stablecoin wallets (funded via credit cards or USDC)",
     "chains_or_networks": "Coinbase and Stripe Privy stablecoin networks",
     "headers_or_methods": "AgentCore Identity Secrets Manager short-lived tokens, scoped payment sessions, and AgentCore Gateway MCP discovery"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-agentcore-payments-is-now-generally-available-enabling-agents-to-transact-safely-and-autonomously-at-scale/"
   },
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "AWS (Amazon Bedrock AgentCore payments)",
    "role": "Agent platform / runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-18",
    "col4_md": "GA 18 August 2026: AgentCore payments pays an MPP service with no extra code.",
    "full_detail_md": "Amazon Bedrock AgentCore payments became generally available on 18 AUG 2026. At GA it includes the Machine Payment Protocol (MPP), another standard for machine payments co-authored by Stripe and Tempo, so a developer can pay an MPP-compatible service without an additional line of code.",
    "facets": {
     "settlement_rail": "Amazon Bedrock AgentCore payments, including MPP at general availability",
     "challenge_or_scheme": "Machine Payment Protocol (MPP), co-authored by Stripe and Tempo",
     "headers_or_methods": "Pays an MPP-compatible service without an additional line of code",
     "sdk_or_endpoint": "AgentCore payments, generally available 18 AUG 2026"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-agentcore-payments-is-now-generally-available-enabling-agents-to-transact-safely-and-autonomously-at-scale/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://aws.amazon.com/blogs/machine-learning/amazon-bedrock-agentcore-payments-is-now-generally-available-enabling-agents-to-transact-safely-and-autonomously-at-scale/",
  "note": "GA runtime supporting x402 `exact` and `upto` with Coinbase/Privy USDC wallets and AgentCore Gateway MCP discovery."
 },
 {
  "id": "aws-iam-roles-anywhere",
  "org_id": "amazon",
  "name": "AWS IAM Roles Anywhere",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "AWS IAM Roles Anywhere",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Commercial works-with listing: X.509 SVID authentication only.",
    "full_detail_md": "The SPIFFE overview lists AWS IAM Roles Anywhere under commercial software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID only.",
    "facets": {
     "svid_or_bundle_format": "A single mark, for X.509 SVID-based authentication.",
     "api_or_federation_surface": "JWT SVID, SPIFFE Authentication, and the Workload API are not marked.",
     "attestation_or_trust_domain": "No trust-domain federation mark. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Commercial works-with listing: X.509 SVID authentication only."
 },
 {
  "id": "aws-kiro",
  "org_id": "amazon",
  "name": "AWS Kiro",
  "url": "https://thenewstack.io/kiro-agent-client-protocol/",
  "type": "harness",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AWS Kiro",
    "role": "Standalone coding agent & client harness",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-08-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-06",
    "col4_md": "Uses ACP over local `stdio` and `WebSocket` between Kiro clients and agent with `_kiro/` extensions.",
    "full_detail_md": "As reported in August 2026, AWS adopted ACP as the boundary between Kiro's clients and Kiro's standalone coding agent process over `stdio` for local workstation execution and `WebSocket` for web and iOS clients, extending the protocol with more than 20 agent-callable methods, 15 client-callable methods, and 20 notification types namespaced under `_kiro/`.",
    "facets": {
     "role_in_acp": "Agent server and first-party client harness",
     "integration_mode": "Standalone agent process with _kiro/ extension namespace",
     "transport": "stdio (local) and WebSocket (web and iOS clients)",
     "verification_posture": "Reported architectural disclosure in trade press (The New Stack, 2026-08-06)",
     "sdk_or_package": "AWS Kiro (_kiro/ ACP extensions)"
    },
    "telemetry": null,
    "source_url": "https://thenewstack.io/kiro-agent-client-protocol/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://thenewstack.io/kiro-agent-client-protocol/",
  "note": "Uses ACP over local `stdio` and `WebSocket` between Kiro clients and agent with `_kiro/` extensions."
 },
 {
  "id": "aws-strands-agents",
  "org_id": "amazon",
  "name": "AWS Strands Agents",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "AWS Strands Agents",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists AWS Strands Agents as Supported under Agent Framework - 1st Party.",
    "full_detail_md": "The AG-UI overview lists AWS Strands Agents as Supported under Agent Framework - 1st Party, with Docs and Demos. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "1st-party agent framework (directory listing)",
     "sdk_or_package": "Not named; Docs and Demos only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "Overview lists AWS Strands Agents as Supported under Agent Framework - 1st Party."
 },
 {
  "id": "aws-waf",
  "org_id": "amazon",
  "name": "AWS WAF",
  "url": "https://aws.amazon.com/about-aws/whats-new/2025/11/aws-waf-web-bot-auth-support/",
  "type": "authority",
  "implements": [
   "http-message-signatures",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "AWS WAF",
    "role": "CDN / WAF verifier",
    "status": "Partial",
    "status_display": "Partial · as of 2025-11-21",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-21",
    "col4_md": "Automatically allows verified Web Bot Auth AI agents on AWS WAF rules protecting Amazon CloudFront distributions.",
    "full_detail_md": "AWS WAF verifies cryptographic HTTP message signatures under Web Bot Auth (WBA) and automatically allows verified AI agent traffic by default (announced 2025-11-21). Graded partial because availability is restricted to AWS WAF deployments protecting Amazon CloudFront distributions.",
    "facets": {
     "signature_or_key_format": "Cryptographic signatures in HTTP messages (Web Bot Auth)",
     "directory_or_header": "HTTP message signature verification on Amazon CloudFront distributions",
     "signing_algorithm": "HTTP message cryptographic signatures",
     "verification_role": "CDN / WAF verifier (scoped to AWS WAF protecting Amazon CloudFront distributions)"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/about-aws/whats-new/2025/11/aws-waf-web-bot-auth-support/"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "AWS WAF",
    "role": "CDN / WAF verifier (Web Bot Auth profile)",
    "status": "Partial",
    "status_display": "Partial · as of 2025-11-21",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-21",
    "col4_md": "Verifies Web Bot Auth HTTP message signatures for AI agents on AWS WAF protecting Amazon CloudFront.",
    "full_detail_md": "AWS WAF validates cryptographic signatures in HTTP messages under the Web Bot Auth (WBA) profile and automatically allows verified AI agent traffic by default (announced 2025-11-21). Graded partial because support is scoped to Web Bot Auth on AWS WAF deployments protecting Amazon CloudFront distributions.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth (WBA) profile of HTTP message signatures",
     "signature_fields": "Cryptographic signatures in HTTP messages",
     "algorithms_or_keys": "Web Bot Auth bot and AI agent signature verification",
     "verification_posture": "CDN / WAF verifier (scoped to AWS WAF protecting Amazon CloudFront distributions)"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/about-aws/whats-new/2025/11/aws-waf-web-bot-auth-support/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://aws.amazon.com/about-aws/whats-new/2025/11/aws-waf-web-bot-auth-support/",
  "note": "Automatically allows verified Web Bot Auth AI agents on AWS WAF rules protecting Amazon CloudFront distributions."
 },
 {
  "id": "bankee-kya-os",
  "org_id": "bankee-ai",
  "name": "Bankee",
  "url": "https://github.com/bankee-ai/bankee-kya-os",
  "type": "sdk",
  "implements": [
   "kya-os"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "kya-os",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Bankee",
    "role": "KYA-OS payment server",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Production DID `did:web:bankee.ai`. The DID document is at `/.well-known/did.json` and holds an Ed25519 key. Tools over a threshold use `wrapWithDelegation` and return `needs_authorization` without a credential.",
    "full_detail_md": "Bankee describes a payment server whose production DID method is `did:web` and whose dev method is `did:key`. Every tool response carries a detached JWS in `_meta.proof` covering SHA-256 hashes of the request and the response, the session ID, a timestamp, and a nonce. The audit service exposes `/api/verify`.",
    "facets": {
     "passport_or_credential": "Production identity did:web:bankee.ai. High-value tools require a W3C Verifiable Credential via wrapWithDelegation.",
     "cryptographic_alg": "Ed25519 public key in /.well-known/did.json. Detached JWS in _meta.proof over SHA-256 hashes.",
     "transport_or_binding": "MCP payment tools. Missing scope returns needs_authorization and a consent URL.",
     "sdk_or_package": "bankee-ai/bankee-kya-os, built on the KYA-OS MCP protocol. Audit endpoint /api/verify."
    },
    "telemetry": null,
    "source_url": "https://github.com/bankee-ai/bankee-kya-os"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/bankee-ai/bankee-kya-os",
  "note": "Production DID `did:web:bankee.ai`. The DID document is at `/.well-known/did.json` and holds an Ed25519 key. Tools over a threshold use `wrapWithDelegation` and return `needs_authorization` without a credential."
 },
 {
  "id": "bbc-co-uk-robots-txt",
  "org_id": "bbc",
  "name": "BBC",
  "url": "https://www.bbc.co.uk/robots.txt",
  "type": "origin",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "BBC",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Sets `Disallow: /` across 14 named AI crawler groups (plus `Scrapy` and `PetalBot`), including `GPTBot`, `OAI-SearchBot`, `ClaudeBot`, `Google-Extended`, `Applebot-Extended`, and `PerplexityBot`.",
    "full_detail_md": "Sets `Disallow: /` across 14 named AI crawler groups (plus `Scrapy` and `PetalBot`): `User-agent: GPTBot`, `User-agent: ChatGPT-User`, `User-agent: OAI-SearchBot`, `User-agent: ClaudeBot`, `User-agent: anthropic-ai`, `User-agent: Google-Extended`, `User-agent: Google-CloudVertexBot`, `User-agent: Applebot-Extended`, `User-agent: CCBot`, `User-agent: Amazonbot`, `User-agent: cohere-ai`, `User-agent: Perplexity-User`, `User-Agent: PerplexityBot`, and `User-agent: meta-externalagent`.",
    "facets": {
     "scope_host": "https://www.bbc.co.uk/robots.txt",
     "policy_role": "Publisher robots.txt policy declaration",
     "published_rules": [
      {
       "tokens": [
        "GPTBot",
        "ChatGPT-User",
        "OAI-SearchBot",
        "ClaudeBot",
        "anthropic-ai",
        "Google-Extended",
        "Google-CloudVertexBot",
        "Applebot-Extended",
        "CCBot",
        "Amazonbot",
        "cohere-ai",
        "Perplexity-User",
        "PerplexityBot",
        "meta-externalagent"
       ],
       "directives": [
        "Disallow: /"
       ]
      }
     ],
     "content_signals": null
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "robots_txt",
     "marker": "User-agent: GPTBot"
    },
    "source_url": "https://www.bbc.co.uk/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.bbc.co.uk/robots.txt",
  "note": "Sets `Disallow: /` across 14 named AI crawler groups (plus `Scrapy` and `PetalBot`), including `GPTBot`, `OAI-SearchBot`, `ClaudeBot`, `Google-Extended`, `Applebot-Extended`, and `PerplexityBot`."
 },
 {
  "id": "better-auth-cimd",
  "org_id": "better-auth",
  "name": "Better Auth",
  "url": "https://better-auth.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Better Auth",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-28",
    "col4_md": "`client_id` is the metadata URL; MCP profile `mcp-2026-07-28`.",
    "full_detail_md": "Better Auth treats `client_id` as the exact HTTPS URL of a metadata document the client hosts, validates that document, and persists the client through its OAuth Provider registration path. For MCP it documents `metadataProfile` value `mcp-2026-07-28` when composing `cimd()` with `mcp()`; that string is a profile identifier, not a publication date of this page.",
    "facets": {
     "metadata_flag_or_profile": "client_id is the exact HTTPS URL of a hosted metadata document; MCP composition uses metadataProfile mcp-2026-07-28",
     "auth_method_or_pkce": "The document is validated and the client is persisted through the OAuth Provider registration path",
     "uri_or_ssrf_rules": "The client hosts the metadata document at an HTTPS URL; the page does not state a separate SSRF rule",
     "draft_or_spec_version": "metadataProfile mcp-2026-07-28 names the MCP specification profile. It is not an OAuth registry schema date and not a publication date of the Better Auth page"
    },
    "telemetry": null,
    "source_url": "https://better-auth.com/docs/plugins/cimd"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://better-auth.com/docs/plugins/cimd",
  "note": "`client_id` is the metadata URL; MCP profile `mcp-2026-07-28`."
 },
 {
  "id": "bitrefill",
  "org_id": "bitrefill",
  "name": "Bitrefill",
  "url": "https://www.bitrefill.com",
  "type": "origin",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Bitrefill",
    "role": "Seller",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-11-06",
    "col4_md": "HTTP 402 `PAYMENT-REQUIRED` (`x402Version` 2, `exact`) on `eip155:8453`, `eip155:42161`, `eip155:137`, Solana, and Lightning (`bolt11`, `upfront`).",
    "full_detail_md": "Probing `https://api.bitrefill.com/x402/gift-cards/search?q=amazon` returns HTTP 402 with `PAYMENT-REQUIRED` (`x402Version: 2`, `extensions.bazaar`) accepting `exact` payments of `amount: \"2000\"` across Base (`eip155:8453`), Arbitrum (`eip155:42161`), Polygon (`eip155:137`), and Solana (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`), plus `amount: \"3000\"` BTC over Lightning (`lnbtc:000000000019d6689c085ae165831e93`, `assetTransferMethod: \"bolt11\"`, `paymentFlow: \"upfront\"`).",
    "facets": {
     "settlement_rail": "x402 v2 exact scheme and Lightning `bolt11` (`upfront` paymentFlow)",
     "supported_assets": "USD Coin, USD₮0, Tether (`Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB`), and BTC (`amount: \"3000\"` via `bolt11`)",
     "chains_or_networks": "Base (`eip155:8453`), Arbitrum (`eip155:42161`), Polygon (`eip155:137`), Solana (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`), Lightning (`lnbtc:000000000019d6689c085ae165831e93`)",
     "headers_or_methods": "HTTP 402 `PAYMENT-REQUIRED` header (`x402Version: 2`) with `extensions.bazaar` metadata on `/x402/gift-cards/search`",
     "amount_raw_atomic": "1000",
     "amount_display": "amount: `1000` atomic USDC units (0.001 USDC)"
    },
    "telemetry": {
     "http_status": 402,
     "transport": "http_header",
     "spec_version": "2",
     "scheme": "exact"
    },
    "source_url": "https://api.bitrefill.com/x402/gift-cards/search?q=amazon"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.bitrefill.com/x402/gift-cards/search?q=amazon",
  "note": "HTTP 402 `PAYMENT-REQUIRED` (`x402Version` 2, `exact`) on `eip155:8453`, `eip155:42161`, `eip155:137`, Solana, and Lightning (`bolt11`, `upfront`)."
 },
 {
  "id": "blamejs",
  "org_id": "blamejs",
  "name": "blamejs",
  "url": "https://blamejs.com/ai-pref",
  "type": "sdk",
  "implements": [
   "aipref-content-usage-attachment"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "blamejs",
    "role": "Middleware",
    "status": "Development",
    "status_display": "Development · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Documents support for the IETF AIPREF `Content-Usage` HTTP response header (citing `draft-ietf-aipref-attach-04` and the WG's `2026-08` milestone target), the matching robots.txt grammar, and Cloudflare Content Signals plus Pay-Per-Crawl (HTTP 402). Operators declare train / infer / snippet preferences once; the middleware emits both the `Content-Usage` header and `CF-Content-Signals`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://blamejs.com/ai-pref"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://blamejs.com/ai-pref",
  "note": "Documents support for the IETF AIPREF `Content-Usage` HTTP response header (citing `draft-ietf-aipref-attach-04` and the WG's `2026-08` milestone target), the matching robots.txt grammar, and Cloudflare Content Signals plus Pay-Per-Crawl (HTTP 402). Operators declare train / infer / snippet preferences once; the middleware emits both the `Content-Usage` header and `CF-Content-Signals`."
 },
 {
  "id": "bloomberg-a2ui",
  "org_id": "bloomberg",
  "name": "Bloomberg",
  "url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "type": "harness",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Bloomberg",
    "role": "Named builder",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-11-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-11-11",
    "col4_md": "Named among companies already building with A2UI, together with Atlassian, Alation, and ByteDance.",
    "full_detail_md": "The NOV. 11, 2026 Google Developers Blog lists Bloomberg among companies already building with A2UI. The post does not describe a Bloomberg product surface.",
    "facets": {
     "transport_or_binding": "Not described beyond the company being named as already building with A2UI",
     "component_or_catalog": "Not described in the announcement",
     "spec_version": "Named in the A2UI 1.0 public-release announcement",
     "sdk_or_renderer": "Not named"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "note": "Named among companies already building with A2UI, together with Atlassian, Alation, and ByteDance."
 },
 {
  "id": "booking-com",
  "org_id": "booking",
  "name": "Booking.com",
  "url": "https://www.booking.com",
  "type": "origin",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Booking.com",
    "role": "ChatGPT app",
    "status": "Listed",
    "status_display": "Listed · as of 2025-10-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-06",
    "col4_md": "Named in the 2025-10-06 DevDay launch set, alongside the Apps SDK preview.",
    "full_detail_md": "TechCrunch and The Verge name Booking.com among the apps inside ChatGPT at the October 6, 2025 DevDay launch, together with Expedia, Spotify, Figma, Coursera, Zillow, and Canva. OpenAI launched a preview of the Apps SDK at the same time.",
    "facets": {
     "transport_or_manifest": "No manifest file cited; named only in launch coverage",
     "ui_or_widget_surface": "Interactive application inside ChatGPT",
     "auth_or_permissions": "No permission model named in the cited launch coverage",
     "sdk_or_version": "Apps SDK preview announced 2025-10-06"
    },
    "telemetry": null,
    "source_url": "https://techcrunch.com/2025/10/06/openai-launches-apps-inside-of-chatgpt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://techcrunch.com/2025/10/06/openai-launches-apps-inside-of-chatgpt/",
  "note": "Named in the 2025-10-06 DevDay launch set, alongside the Apps SDK preview."
 },
 {
  "id": "box-prm",
  "org_id": "box",
  "name": "Box MCP",
  "url": "https://mcp.box.com",
  "type": "origin",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Box",
    "role": "Protected resource",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`resource` `https://mcp.box.com/`, `resource_name` `Box Model Context Protocol Server`, `authorization_servers` `https://api.box.com/`, `bearer_methods_supported` `header`.",
    "full_detail_md": "GET https://mcp.box.com/.well-known/oauth-protected-resource returned HTTP 200 `application/json`. `resource` is `https://mcp.box.com/` and `resource_name` is `Box Model Context Protocol Server`. `authorization_servers` is `https://api.box.com/`. `bearer_methods_supported` is `header`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.box.com/.well-known/oauth-protected-resource (resource https://mcp.box.com/; resource_name Box Model Context Protocol Server; authorization_servers https://api.box.com/)",
     "registration_or_client_id_modes": "Not declared in this protected-resource document",
     "pkce_or_grant_types": "Not declared in this protected-resource document; bearer_methods_supported header",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-protected-resource",
     "resource": "https://mcp.box.com/"
    },
    "source_url": "https://mcp.box.com/.well-known/oauth-protected-resource"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.box.com/.well-known/oauth-protected-resource",
  "note": "`resource` `https://mcp.box.com/`, `resource_name` `Box Model Context Protocol Server`, `authorization_servers` `https://api.box.com/`, `bearer_methods_supported` `header`."
 },
 {
  "id": "brave-leo",
  "org_id": "brave",
  "name": "Brave (Leo AI)",
  "url": "https://github.com/brave/brave-browser/issues/55232",
  "type": "harness",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Brave (Leo AI)",
    "role": "AI agent",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-07",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-10-07",
    "col4_md": "Experimental in Leo AI chat; flag `brave://flags/#enable-webmcp-testing`.",
    "full_detail_md": "The implementation-status page says experimental support is added to Leo AI chat and links issue 55232, which is open, updated 2026-10-07, and titled Add support for the WebMCP protocol to Leo. The issue says associated pages expose tools to AI Chat, and the test plan turns on `brave://flags/#enable-webmcp-testing`.",
    "facets": {
     "engine_or_runtime": "Brave Leo AI chat",
     "api_surface_or_flag": "brave://flags/#enable-webmcp-testing",
     "position_or_status": "Experimental; Brave issue 55232 is open",
     "package_or_version": "Issue updated 2026-10-07; no Brave version named on the status page"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md",
  "note": "Experimental in Leo AI chat; flag `brave://flags/#enable-webmcp-testing`."
 },
 {
  "id": "britecity-com",
  "org_id": "britecity",
  "name": "BRITECITY",
  "url": "https://britecity.com/it-health-check",
  "type": "origin",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "BRITECITY",
    "role": "In-page caller",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Reads `navigator.modelContext` or `document.modelContext`, then `mc.registerTool`.",
    "full_detail_md": "The HTTP 200 text/html page fetched 2026-11-04 reads `navigator.modelContext` or `document.modelContext`, then calls `mc.registerTool`. Tool names in that script are `get_britecity_services`, `lookup_knowledge`, `navigate_to_page`, and `open_book_a_call`.",
    "facets": {
     "engine_or_runtime": "In-page script on britecity.com/it-health-check",
     "api_surface_or_flag": "navigator.modelContext or document.modelContext, then mc.registerTool",
     "position_or_status": "Live HTTP 200 text/html (fetched 2026-11-04)",
     "package_or_version": "Tools get_britecity_services, lookup_knowledge, navigate_to_page, open_book_a_call"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/html; charset=utf-8",
     "observed_member": "mc.registerTool",
     "legacy_member": "navigator.modelContext",
     "also_reads": "document.modelContext",
     "spec_member": "document.modelContext.registerTool",
     "tool_names": [
      "get_britecity_services",
      "lookup_knowledge",
      "navigate_to_page",
      "open_book_a_call"
     ]
    },
    "source_url": "https://britecity.com/it-health-check"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://britecity.com/it-health-check",
  "note": "Reads `navigator.modelContext` or `document.modelContext`, then `mc.registerTool`."
 },
 {
  "id": "browserbase",
  "org_id": "browserbase",
  "name": "Browserbase",
  "url": "https://browserbase.com",
  "type": "origin",
  "implements": [
   "http-message-signatures",
   "mpp",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto",
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Browserbase",
    "role": "Seller",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 402 on POST `/browser/session/create`; catalog `tempo` and `stripe` intent `charge`.",
    "full_detail_md": "The catalog lists Browserbase as active, with method tempo intent charge asset 0x20c000000000000000000000b9537d11c60e8b50 and method stripe intent charge asset usd. POST /browser/session/create is a payment-required problem document, HTTP 402, for pay-per-use browser sessions via x402 or MPP.",
    "facets": {
     "settlement_rail": "tempo charge on asset 0x20c000000000000000000000b9537d11c60e8b50, and stripe charge on asset usd",
     "challenge_or_scheme": "Catalog status active; the session-create probe returns a payment-required problem document",
     "headers_or_methods": "HTTP 402 problem document (status 402) for pay-per-use browser sessions via x402 or MPP",
     "sdk_or_endpoint": "POST /browser/session/create on https://mpp.browserbase.com"
    },
    "telemetry": {
     "http_status": 402,
     "problem_type": "https://paymentauth.org/problems/payment-required",
     "catalog_id": "browserbase",
     "snapshot_fetch_status": 200
    },
    "source_url": "https://mpp.browserbase.com/browser/session/create"
   },
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Browserbase",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Publishes two `Ed25519` JWKs (`purpose` `rag`) and directory-response signature headers; signature validation not established by HTTP observation.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` at Browserbase's key directory, publishing two `Ed25519` JWKs (`\"purpose\":\"rag\"`) and directory-response `binding0`/`binding1` signature headers (`tag=\"http-message-signatures-directory\"`); cryptographic signature validation is not established by the recorded HTTP observation.",
    "facets": {
     "signature_or_key_format": "Publishes 2 OKP Ed25519 JWKs (`purpose: rag`, `use: sig`) and directory-response signature headers; signature validation not established by the recorded HTTP observation",
     "directory_or_header": "HTTP 200 `application/http-message-signatures-directory+json` (`binding0`, `binding1` response signatures)",
     "signing_algorithm": "Ed25519 (`tag=\"http-message-signatures-directory\"`)",
     "verification_role": "Bot / Agent signer (Cloudflare Signed Agents program participant)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 2,
     "purpose": "rag",
     "kids": [
      "NVhTndQWodGQ47Kmhm1bhTdt0swWS7EHmUEMo-opsXU",
      "DJuTDnlBxNZzalQhhvktwvkF3lWss-T56g7s4xubuhU"
     ],
     "signature_labels": [
      "binding0",
      "binding1"
     ],
     "use": "sig"
    },
    "source_url": "https://www.browserbase.com/.well-known/http-message-signatures-directory"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Browserbase",
    "role": "Bot / Agent signer (Web Bot Auth profile)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Web Bot Auth profile: publishes two `Ed25519` JWKs (`purpose` `rag`) and directory-response `binding0`/`binding1` signature headers.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` at the Browserbase key directory endpoint, publishing two `OKP` `Ed25519` JWKs (`\"purpose\":\"rag\"`) and dual directory-response `binding0`/`binding1` signature headers (`tag=\"http-message-signatures-directory\"`); cryptographic signature validation is not established by the recorded HTTP observation.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth profile of RFC 9421 (`tag=\"http-message-signatures-directory\"`)",
     "signature_fields": "HTTP 200 `application/http-message-signatures-directory+json` (`binding0`, `binding1` response signatures)",
     "algorithms_or_keys": "Publishes 2 OKP `Ed25519` JWKs (`purpose: rag`, `use: sig`) and directory-response signature headers",
     "verification_posture": "Bot / Agent signer (Web Bot Auth directory publisher; runtime signature validation not established by HTTP observation)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 2,
     "purpose": "rag",
     "kids": [
      "NVhTndQWodGQ47Kmhm1bhTdt0swWS7EHmUEMo-opsXU",
      "DJuTDnlBxNZzalQhhvktwvkF3lWss-T56g7s4xubuhU"
     ],
     "signature_labels": [
      "binding0",
      "binding1"
     ],
     "use": "sig"
    },
    "source_url": "https://www.browserbase.com/.well-known/http-message-signatures-directory"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.browserbase.com/browser/session/create",
  "note": "HTTP 402 on POST `/browser/session/create`; catalog `tempo` and `stripe` intent `charge`."
 },
 {
  "id": "buildkite",
  "org_id": "buildkite",
  "name": "Buildkite",
  "url": "https://buildkite.com/.well-known/ard.json",
  "type": "origin",
  "implements": [
   "ard",
   "mcp-server-cards"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Buildkite",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"1.0\"`) with 1 entry, first `urn:air:buildkite.com:mcp:buildkite` type `application/mcp-server-card+json` at https://mcp.buildkite.com/mcp/server-card",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://buildkite.com/.well-known/ard.json"
   },
   {
    "protocol_id": "mcp-server-cards",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Buildkite (remote MCP server)",
    "role": "Server Card publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GET https://mcp.buildkite.com/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://mcp.buildkite.com/mcp, card name com.buildkite/remote-mcp-server. Buildkite's docs tell tools to use the OAuth remote server at https://mcp.buildkite.com/mcp.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://mcp.buildkite.com/mcp/server-card"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://buildkite.com/.well-known/ard.json",
  "note": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"1.0\"`) with 1 entry, first `urn:air:buildkite.com:mcp:buildkite` type `application/mcp-server-card+json` at https://mcp.buildkite.com/mcp/server-card"
 },
 {
  "id": "bun-agents-md",
  "org_id": "oven-sh",
  "name": "oven-sh/bun",
  "url": "https://raw.githubusercontent.com/oven-sh/bun/main/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "oven-sh/bun",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves a 9-byte root `AGENTS.md` (`text/plain`) containing only `CLAUDE.md` as a cross-file pointer.",
    "full_detail_md": "Serves a 9-byte root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, `content-length: 9`, checked 2026-11-04) whose body is the single line `CLAUDE.md`, delegating coding-agent instructions to `CLAUDE.md` via a cross-file pointer.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/oven-sh/bun/main/AGENTS.md",
     "repo_scope": "Bun runtime repository root (9-byte pointer file)",
     "heading_structure": "None (single-line plain-text pointer: CLAUDE.md)",
     "precedence_or_nested_files": "Delegates root AGENTS.md instructions to CLAUDE.md"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "CLAUDE.md"
    },
    "source_url": "https://raw.githubusercontent.com/oven-sh/bun/main/AGENTS.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/oven-sh/bun/main/AGENTS.md",
  "note": "Serves a 9-byte root `AGENTS.md` (`text/plain`) containing only `CLAUDE.md` as a cross-file pointer."
 },
 {
  "id": "bun-llms-txt",
  "org_id": "oven-sh",
  "name": "Bun",
  "url": "https://bun.sh/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Bun",
    "role": "Runtime docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://bun.sh/llms.txt` (`# Bun`, `text/plain`), indexing runtime, package manager, bundler, and TypeScript `.md` documentation pages.",
    "full_detail_md": "Serves `https://bun.sh/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 35,373 bytes, fetched 2026-11-04) opening `# Bun` and indexing `.md` documentation pages across runtime APIs, package management, bundling, testing, and TypeScript configuration under `https://bun.com/docs/`.",
    "facets": {
     "artifact_path": "https://bun.sh/llms.txt",
     "companion_files": ".md documentation twins under https://bun.com/docs/*.md",
     "content_type_or_bytes": "text/plain; charset=utf-8 (35,373 bytes)",
     "generator_or_consumer_mode": "Root documentation index linking .md page twins"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Bun"
    },
    "source_url": "https://bun.sh/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://bun.sh/llms.txt",
  "note": "Serves `https://bun.sh/llms.txt` (`# Bun`, `text/plain`), indexing runtime, package manager, bundler, and TypeScript `.md` documentation pages."
 },
 {
  "id": "buyer-agent",
  "org_id": "iab-tech-lab",
  "name": "IAB Tech Lab Buyer Agent",
  "url": "https://github.com/IABTechLab/buyer-agent",
  "type": "sdk",
  "implements": [
   "aamp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "aamp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "IAB Tech Lab Buyer Agent",
    "role": "Reference buyer agent",
    "status": "Development",
    "status_display": "Development · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "The standards page says IAB Tech Lab included an open-source reference implementation for Ad Buyer Systems, and that companies can download the Buyer Agent SDK. The Buyer Agent README marks the repo `V2 - Active Development`. It is a media buying system for DSPs, agencies, and advertisers. It obtains Deal IDs for The Trade Desk, DV360, and Amazon DSP. Sellers are called through an `MCP Client`, an `A2A Client` using `JSON-RPC 2.0`, and a `REST Client`. Optional vendor approval gating (`SGP_ENFORCE=true`) is off by default: when `SGP_ENFORCE` is unset there are zero SGP calls. The hub README calls it a reference implementation of demand-side agent logic.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/IABTechLab/buyer-agent/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/IABTechLab/buyer-agent/main/README.md",
  "note": "The standards page says IAB Tech Lab included an open-source reference implementation for Ad Buyer Systems, and that companies can download the Buyer Agent SDK. The Buyer Agent README marks the repo `V2 - Active Development`. It is a media buying system for DSPs, agencies, and advertisers. It obtains Deal IDs for The Trade Desk, DV360, and Amazon DSP. Sellers are called through an `MCP Client`, an"
 },
 {
  "id": "bytedance-a2ui",
  "org_id": "bytedance",
  "name": "ByteDance",
  "url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "ByteDance",
    "role": "Renderer publisher",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-11-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-11-11",
    "col4_md": "ByteDance released an A2UI renderer for Lynx and is named among companies already building with A2UI. Lynx supports A2UI 0.9 today and is adapting to 1.0.",
    "full_detail_md": "The NOV. 11, 2026 Google Developers Blog says ByteDance released an A2UI renderer for Lynx, its cross-platform framework, in June 2026. Lynx supports A2UI 0.9 today and is adapting to 1.0 with the A2UI team.",
    "facets": {
     "transport_or_binding": "Lynx cross-platform renderer",
     "component_or_catalog": "Default Lynx component set",
     "spec_version": "A2UI 0.9 today; adapting to 1.0",
     "sdk_or_renderer": "ByteDance Lynx A2UI renderer"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://developers.googleblog.com/a2ui-10-build-delightful-fast-reliable-agentic-experiences/",
  "note": "ByteDance released an A2UI renderer for Lynx and is named among companies already building with A2UI. Lynx supports A2UI 0.9 today and is adapting to 1.0."
 },
 {
  "id": "canva",
  "org_id": "canva",
  "name": "Canva",
  "url": "https://www.canva.com",
  "type": "sdk",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Canva",
    "role": "Plugin package",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Main-branch `canva` `14.0.0`; invoke `@Canva`; id in `.app.json`.",
    "full_detail_md": "Canva is a DevDay launch app and an openai/plugins main-branch package: `.codex-plugin/plugin.json` is version `14.0.0`, names author Canva Pty Ltd., points at `./skills`, requires connecting a Canva account (Bulk Create needs an eligible Enterprise plan), and says to invoke the plugin with `@Canva`. `.app.json` binds app id `connector_68df33b1a2d081918778431a9cfca8ba`; those cited files are the floating main branch, so this row is Partial rather than Supported.",
    "facets": {
     "transport_or_manifest": "openai/plugins main: .codex-plugin/plugin.json and .app.json",
     "ui_or_widget_surface": "Codex and ChatGPT plugin invoked with @Canva",
     "auth_or_permissions": "Connect a Canva account; Bulk Create needs an eligible Enterprise plan",
     "sdk_or_version": "plugin.json version 14.0.0 on main; also a DevDay launch app"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/openai/plugins/main/plugins/canva/.codex-plugin/plugin.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/openai/plugins/main/plugins/canva/.codex-plugin/plugin.json",
  "note": "Main-branch `canva` `14.0.0`; invoke `@Canva`; id in `.app.json`."
 },
 {
  "id": "ccbot",
  "org_id": "common-crawl",
  "name": "CCBot",
  "url": "https://commoncrawl.org/ccbot",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Common Crawl",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`CCBot` (`CCBot/2.0`) crawls open web archive datasets; honors `User-agent: CCBot` with `Disallow: /` and publishes `ccbot.json` IPs.",
    "full_detail_md": "CCBot identifies itself as `CCBot/2.0 (https://commoncrawl.org/faq/)`. The opt-out in robots.txt is `User-agent: CCBot` and `Disallow: /`.",
    "facets": {
     "user_agent_token": [
      "CCBot",
      "CCBot/2.0 (https://commoncrawl.org/faq/)"
     ],
     "operator_purpose": "Open web archive corpus crawling",
     "ip_verification_url": "https://commoncrawl.org/ccbot",
     "robots_directives_honored": [
      "User-agent: CCBot",
      "Disallow: /"
     ]
    },
    "telemetry": null,
    "source_url": "https://commoncrawl.org/ccbot"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://commoncrawl.org/ccbot",
  "note": "`CCBot` (`CCBot/2.0`) crawls open web archive datasets; honors `User-agent: CCBot` with `Disallow: /` and publishes `ccbot.json` IPs."
 },
 {
  "id": "chaoschain",
  "org_id": "chaoschain",
  "name": "ChaosChain",
  "url": "https://raw.githubusercontent.com/ChaosChain/chaoschain/main/README.md",
  "type": "authority",
  "implements": [
   "erc-8004"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "ChaosChain",
    "role": "Verifier SDK / Runtime",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Main-branch RewardsDistributor V4 writes verifier accuracy to ERC-8004.",
    "full_detail_md": "The ChaosChain README on the main branch says RewardsDistributor V4 publishes verifier consensus accuracy to ERC-8004 so both sides of the reputation record are populated. Support is Partial because that statement sits on the unreleased main branch, not a tagged release artifact.",
    "facets": {
     "registry_or_contract": "RewardsDistributor V4 publishes verifier consensus accuracy into ERC-8004 reputation",
     "chains_or_networks": "The README row does not name the chain of the ERC-8004 write",
     "standards_profile": "ERC-8004 reputation, with both sides of the record populated",
     "sdk_or_deployment": "ChaosChain RewardsDistributor V4, described on the main-branch README"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/ChaosChain/chaoschain/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/ChaosChain/chaoschain/main/README.md",
  "note": "Main-branch RewardsDistributor V4 writes verifier accuracy to ERC-8004."
 },
 {
  "id": "chatgpt",
  "org_id": "openai",
  "name": "ChatGPT",
  "url": "https://developers.openai.com/plugins/build/chatgpt-ui",
  "type": "harness",
  "implements": [
   "mcp-apps",
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "ChatGPT",
    "role": "Apps host",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "MCP Apps host: `_meta.ui.resourceUri`, `ui/*` postMessage, `text/html;profile=mcp-app`.",
    "full_detail_md": "ChatGPT implements the open MCP Apps standard for UI returned by an MCP server: a component declares `_meta.ui.resourceUri`, talks to the host with the `ui/*` JSON-RPC bridge over postMessage, and the dice sample registers `ui://widget/dice.html` with mimeType `text/html;profile=mcp-app`. ChatGPT-specific calls use `window.openai`, and the same UI can run in other compatible MCP Apps hosts.",
    "facets": {
     "transport_or_manifest": "MCP server UI resource declared with _meta.ui.resourceUri",
     "ui_or_widget_surface": "iframe component; dice sample ui://widget/dice.html; mimeType text/html;profile=mcp-app",
     "auth_or_permissions": "No separate auth handshake named in the cited UI guide",
     "sdk_or_version": "MCP Apps ui/* JSON-RPC over postMessage; ChatGPT-only calls use window.openai"
    },
    "telemetry": null,
    "source_url": "https://developers.openai.com/plugins/build/chatgpt-ui"
   },
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "ChatGPT",
    "role": "AI host",
    "status": "Supported",
    "status_display": "Supported · as of 2026-02-22",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-03",
    "as_of": "2026-02-22",
    "col4_md": "ChatGPT uses JSON-RPC over `postMessage`; changelog 2026-02-22 says it is fully compatible.",
    "full_detail_md": "ChatGPT implements the open MCP Apps standard for UI returned by an MCP server, using JSON-RPC over postMessage, and the changelog dated 2026-02-22 says ChatGPT is now fully compatible with the MCP Apps spec. OpenAI extensions are optional and live in window.openai, which is a ChatGPT-specific addition rather than a shared MCP Apps requirement.",
    "facets": {
     "transport_or_channel": "JSON-RPC over postMessage for UI returned by an MCP server",
     "ui_resource_or_primitive": "Open MCP Apps standard for UI; optional ChatGPT extensions in window.openai",
     "sandbox_or_security": "Shared MCP Apps fields stay separate from optional window.openai extensions",
     "sdk_or_version": "Changelog 2026-02-22 says ChatGPT is fully compatible with the MCP Apps spec"
    },
    "telemetry": null,
    "source_url": "https://developers.openai.com/plugins/build/chatgpt-ui"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://developers.openai.com/plugins/build/chatgpt-ui",
  "note": "MCP Apps host: `_meta.ui.resourceUri`, `ui/*` postMessage, `text/html;profile=mcp-app`."
 },
 {
  "id": "chatgpt-desktop",
  "org_id": "openai",
  "name": "OpenAI ChatGPT Desktop",
  "url": "https://chatgpt.com/download/",
  "type": "harness",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "OpenAI ChatGPT Desktop",
    "role": "AI agent",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": null,
    "col4_md": "Status page: supported in ChatGPT Desktop; no version named.",
    "full_detail_md": "The implementation-status page says WebMCP is supported in ChatGPT Desktop and names no product version. That statement is the group's status page, not a numbered ChatGPT Desktop release.",
    "facets": {
     "engine_or_runtime": "OpenAI ChatGPT Desktop",
     "api_surface_or_flag": "WebMCP as stated on the implementation-status page",
     "position_or_status": "Supported on the implementation-status page; no version named",
     "package_or_version": "No product version on the status page"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md",
  "note": "Status page: supported in ChatGPT Desktop; no version named."
 },
 {
  "id": "checkout-com",
  "org_id": "checkout-com",
  "name": "Checkout.com",
  "url": "https://www.checkout.com/newsroom/checkout-adopts-acp-backed-by-openai-to-power-agentic-commerce-for-enterprise-merchants",
  "type": "venue",
  "implements": [
   "agentic-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Checkout.com",
    "role": "Payment rail",
    "status": "Supported",
    "status_display": "Supported · as of 2025-11-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-25",
    "col4_md": "Adopted ACP to power agentic commerce payments for enterprise merchants (announced November 25, 2025).",
    "full_detail_md": "Checkout.com announced on November 25, 2025 its support for the Agentic Commerce Protocol (ACP) to power agentic commerce for enterprise merchants.",
    "facets": {
     "commerce_role_or_surface": "Enterprise payment service provider for ACP",
     "payment_or_token_rail": "ACP payment processing for enterprise merchants",
     "api_or_spec_version": "Agentic Commerce Protocol (ACP)",
     "availability_or_eligibility_posture": "Announced November 25, 2025"
    },
    "telemetry": null,
    "source_url": "https://www.checkout.com/newsroom/checkout-adopts-acp-backed-by-openai-to-power-agentic-commerce-for-enterprise-merchants"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.checkout.com/newsroom/checkout-adopts-acp-backed-by-openai-to-power-agentic-commerce-for-enterprise-merchants",
  "note": "Adopted ACP to power agentic commerce payments for enterprise merchants (announced November 25, 2025)."
 },
 {
  "id": "christian-posta",
  "org_id": "christian-posta",
  "name": "Christian Posta (Keycloak extension)",
  "url": "https://www.ietf.org/archive/id/draft-hardt-oauth-aauth-protocol-11.txt",
  "type": "authority",
  "implements": [
   "aauth-hardt"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "aauth-hardt",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Christian Posta (Keycloak extension)",
    "role": "Authorization server / IdP",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "SPI extension for Keycloak 26.2.5. draft-hardt-oauth-aauth-protocol-11 lists it as an exploratory AAuth access server extension, and the repository description says to load it as a Keycloak SPI.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-hardt-oauth-aauth-protocol-11.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.ietf.org/archive/id/draft-hardt-oauth-aauth-protocol-11.txt",
  "note": "SPI extension for Keycloak 26.2.5. draft-hardt-oauth-aauth-protocol-11 lists it as an exploratory AAuth access server extension, and the repository description says to load it as a Keycloak SPI."
 },
 {
  "id": "chrome",
  "org_id": "google",
  "name": "Google Chrome",
  "url": "https://developer.chrome.com/docs/ai/webmcp",
  "type": "harness",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Google Chrome",
    "role": "Browser engine",
    "status": "Origin trial",
    "status_display": "Origin trial · as of 2026-11-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Origin trial in Chrome 149 (`about:flags#enable-webmcp-testing`); ChromeStatus feature 5117755740913664 lists status `Proposed` (`origintrial`: `false`; desktop trial stage 149–156).",
    "full_detail_md": "The implementation-status page fetched 2026-11-04 says an origin trial is live in Chrome 149 and names the local flag `about:flags#enable-webmcp-testing`; Chrome's WebMCP docs (dateModified 2026-10-07) say extensions can query and execute WebMCP tools with content scripts, and the origin-trial post says sites can sign up in Chrome 149. ChromeStatus updated 2026-11-02 sets Chrome status text to Proposed with origintrial false and flag false, while its origin-trial stage lists desktop_first 149 and desktop_last 156 for web feature `document-modelcontext` and use counter `kModelContextRegisterTool`, and the blink-dev intent separately lists shipping on desktop 157 with origin-trial desktop first 149 and last 156; this row follows the implementation-status page rather than the ChromeStatus Proposed label.",
    "facets": {
     "engine_or_runtime": "Google Chrome",
     "api_surface_or_flag": "about:flags#enable-webmcp-testing (implementation-status); docs also name chrome://flags/#enable-webmcp-testing",
     "position_or_status": "Origin trial in Chrome 149 on the implementation-status page; ChromeStatus status.text is Proposed and origintrial is false",
     "package_or_version": "Chrome 149 origin trial; ChromeStatus desktop_first 149 and desktop_last 156; blink-dev intent lists shipping on desktop 157"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md",
  "note": "Origin trial in Chrome 149 (`about:flags#enable-webmcp-testing`); ChromeStatus feature 5117755740913664 lists status `Proposed` (`origintrial`: `false`; desktop trial stage 149–156)."
 },
 {
  "id": "chrome-lighthouse",
  "org_id": "google",
  "name": "Chrome Lighthouse",
  "url": "https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file",
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Chrome Lighthouse",
    "role": "Validator / CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-05-05",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05-05",
    "col4_md": "Agentic browsing audit fetches `llms.txt` and flags server errors; 404 is marked Not Applicable (updated 2026-05-05).",
    "full_detail_md": "Chrome Lighthouse includes an `llms.txt` check in its experimental Agentic Browsing audits (documentation updated 2026-05-05). The audit attempts to retrieve `/llms.txt` and flags server errors (5xx), while marking HTTP 404 responses as Not Applicable (N/A) because providing the file is optional.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "None",
     "content_type_or_bytes": "HTTP status check (flags server errors; 404 marked Not Applicable)",
     "generator_or_consumer_mode": "Browser DevTools / CLI agentic browsing validator (updated 2026-05-05)"
    },
    "telemetry": null,
    "source_url": "https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt"
   },
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Chrome Lighthouse",
    "role": "Security / Audit scanner",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-09",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-09",
    "col4_md": "v13.5.0 (18 September 2026) ships the `ard-schema` audit. Gatherer `core/gather/gatherers/agentic/ard.js` requests an HTML <link rel=\"ai-catalog\">, HTTP `Link` headers, and `/.well-known/ai-catalog.json` (issue #17251, closed 2026-10-09).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/repos/GoogleChrome/lighthouse/releases/tags/v13.5.0"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt",
  "note": "Agentic browsing audit fetches `llms.txt` and flags server errors; 404 is marked Not Applicable (updated 2026-05-05)."
 },
 {
  "id": "cilium",
  "org_id": "cilium",
  "name": "Cilium",
  "url": "https://www.cncf.io/blog/2026/09/14/cilium-1-20-gateway-api-externalauth-tcproute-udproute-eni-ipam-for-ipv6-and-more/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Cilium",
    "role": "Relying proxy",
    "status": "Supported (preview)",
    "status_display": "Supported (preview) · as of 2026-09-14",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-09-14",
    "col4_md": "Cilium 1.20 (2026-09-14) spire mode uses SPIFFE workload identities, with SPIRE issuing and rotating certificates. ztunnel remains Beta.",
    "full_detail_md": "The CNCF Cilium 1.20 announcement, posted September 14, 2026, says ztunnel remains Beta. The certificate authority is configurable: the default internal mode runs ztunnel mTLS without requiring SPIRE, while spire mode uses SPIFFE workload identities, with SPIRE issuing and rotating certificates for teams that want the CNCF-graduated SPIFFE and SPIRE identity stack. ztunnel is the per-node proxy for sidecarless mutual TLS and builds on the upstream ztunnel project originally created for Istio's ambient mesh.",
    "facets": {
     "svid_or_bundle_format": "spire mode uses SPIFFE workload identities. SPIRE issues and rotates the certificates.",
     "api_or_federation_surface": "ztunnel sidecarless mTLS. The default internal mode does not require SPIRE.",
     "attestation_or_trust_domain": "CNCF-graduated SPIFFE and SPIRE identity stack, selected by the configurable certificate authority.",
     "verification_posture": "Cilium 1.20 release announcement. ztunnel remains Beta, so the row is graded preview."
    },
    "telemetry": null,
    "source_url": "https://www.cncf.io/blog/2026/09/14/cilium-1-20-gateway-api-externalauth-tcproute-udproute-eni-ipam-for-ipv6-and-more/"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "source",
  "source": "https://www.cncf.io/blog/2026/09/14/cilium-1-20-gateway-api-externalauth-tcproute-udproute-eni-ipam-for-ipv6-and-more/",
  "note": "Cilium 1.20 (2026-09-14) spire mode uses SPIFFE workload identities, with SPIRE issuing and rotating certificates. ztunnel remains Beta."
 },
 {
  "id": "circle",
  "org_id": "circle",
  "name": "Circle (AgenticCommerce on Arc Testnet)",
  "url": "https://docs.arc.io/arc/references/contract-addresses",
  "type": "venue",
  "implements": [
   "erc-8183"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8183",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Circle (`AgenticCommerce` on Arc Testnet)",
    "role": "Reference escrow contract",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-10-29",
    "col4_md": "USDC job escrow & post-evaluation settlement contract on Arc Testnet (`0x0747EEf0706327138c69792bF28Cd525089e4583`, 629,018 testnet txns as of 2026-10-29; no mainnet address)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.arc.io/arc/references/contract-addresses"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://docs.arc.io/arc/references/contract-addresses",
  "note": "USDC job escrow & post-evaluation settlement contract on Arc Testnet (`0x0747EEf0706327138c69792bF28Cd525089e4583`, 629,018 testnet txns as of 2026-10-29; no mainnet address)"
 },
 {
  "id": "circle-wallets",
  "org_id": "circle-wallets",
  "name": "Circle Wallets (Arc Testnet walkthrough)",
  "url": "https://www.arc.io/blog/running-an-agentic-economic-flow-on-arc-with-erc-8183",
  "type": "authority",
  "implements": [
   "erc-8183"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8183",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Circle Wallets (Arc Testnet walkthrough)",
    "role": "Wallet (Testnet Demo)",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "Circle programmable wallets driving the ERC-8183 USDC job escrow lifecycle on Arc Testnet",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.arc.io/blog/running-an-agentic-economic-flow-on-arc-with-erc-8183"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://www.arc.io/blog/running-an-agentic-economic-flow-on-arc-with-erc-8183",
  "note": "Circle programmable wallets driving the ERC-8183 USDC job escrow lifecycle on Arc Testnet"
 },
 {
  "id": "cisco-outshift-agntcy-directory",
  "org_id": "cisco-outshift-agntcy-directory",
  "name": "Cisco Outshift AGNTCY Directory",
  "url": "https://ai-catalog.outshift.io/.well-known/ai-catalog.json",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cisco Outshift AGNTCY Directory",
    "role": "Publisher",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Implementations-directory testbed at `ai-catalog.outshift.io/.well-known/ai-catalog.json` (`displayName` AGNTCY Directory) with filtered collections for A2A Agent Cards, MCP Server Cards, and Agent Skills.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://ai-catalog.outshift.io/.well-known/ai-catalog.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://ai-catalog.outshift.io/.well-known/ai-catalog.json",
  "note": "Implementations-directory testbed at `ai-catalog.outshift.io/.well-known/ai-catalog.json` (`displayName` AGNTCY Directory) with filtered collections for A2A Agent Cards, MCP Server Cards, and Agent Skills."
 },
 {
  "id": "claude",
  "org_id": "anthropic",
  "name": "Claude",
  "url": "https://claude.com",
  "type": "harness",
  "implements": [
   "anthropic-agent-skills-format",
   "mcp",
   "mcp-apps",
   "oauth-cimd"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Claude",
    "role": "AI host application",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Remote MCP connectors (OAuth or headers) and local `claude_desktop_config.json` servers; stateless `2026-07-28` rollout in progress.",
    "full_detail_md": "Claude supports remote MCP custom connectors brokered from Anthropic cloud infrastructure (using published OAuth client identity, automatic registration, custom OAuth client credentials, or request headers) across claude.ai, Claude Desktop, and Cowork, local `claude_desktop_config.json` and `.mcpb` servers on desktop, and is rolling out stateless `2026-07-28` support.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1 (published identity, DCR, custom client) and request headers",
     "primitives": "tools, resources, prompts, MCP Apps, Tasks",
     "sdk_or_package": "Claude Desktop, claude.ai, Claude Code, Cowork"
    },
    "telemetry": null,
    "source_url": "https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp"
   },
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Claude.ai and Claude Desktop",
    "role": "Web & desktop host apps",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-16",
    "col4_md": "Supports uploaded and admin-provisioned skills on `claude.ai` and Desktop, strictly validating the six standard `SKILL.md` frontmatter keys.",
    "full_detail_md": "Claude web (`claude.ai`) and Claude Desktop manage user and Team/Enterprise admin-provisioned skills from settings and the `claude.com/connectors` partner directory; uploaded `SKILL.md` files are strictly validated against the six standard frontmatter properties (`allowed-tools`, `compatibility`, `description`, `license`, `metadata`, `name`), rejecting unrecognized keys with a hard error and omitting Claude Code-only dynamic context injection.",
    "facets": {
     "transport_or_packaging": "Zip/folder upload to claude.ai, Desktop Customize sidebar, and Team/Enterprise admin provisioning",
     "manifest_or_entry": "Strict 6-key SKILL.md frontmatter validation (rejects non-spec keys such as argument-hint)",
     "execution_or_sandbox": "Managed Claude execution environment; Claude Code-only body features do not run",
     "verification_posture": "First-party product documentation and launch announcements (2025-10-16, checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://claude.com/resources/articles/skills"
   },
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Claude",
    "role": "AI host",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-26",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-26",
    "col4_md": "January 26, 2026: MCP Apps on mobile, web, and desktop, plus Claude Cowork.",
    "full_detail_md": "On January 26, 2026, Anthropic brought interactive connectors to Claude with MCP Apps, available on mobile, web, and desktop for Free, Pro, Max, Team, and Enterprise plans, and also on Claude Cowork. That article is a product announcement, not an HTTP endpoint probe and not a registry JSON record.",
    "facets": {
     "transport_or_channel": "Claude host renders MCP Apps inside the conversation; the article does not name a separate transport",
     "ui_resource_or_primitive": "Interactive connectors brought to Claude with MCP Apps",
     "sandbox_or_security": "Announcement does not restate CSP; host rendering follows the MCP Apps sandbox model",
     "sdk_or_version": "January 26, 2026 announcement; mobile, web, and desktop for Free, Pro, Max, Team, and Enterprise, plus Claude Cowork"
    },
    "telemetry": null,
    "source_url": "https://claude.com/resources/articles/interactive-tools-in-claude"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Anthropic, Claude",
    "role": "OAuth client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `client_name` Claude; grant includes `jwt-bearer`.",
    "full_detail_md": "`https://claude.ai/oauth/mcp-oauth-client-metadata` returned HTTP 200 `application/json`, with `client_id` equal to that URL, `client_name` Claude, and `token_endpoint_auth_method` `none`. `redirect_uris` contains `https://claude.ai/api/mcp/auth_callback`, and `grant_types` are `authorization_code`, `refresh_token`, and `urn:ietf:params:oauth:grant-type:jwt-bearer`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "Published client metadata JSON; client_name Claude; client_id equals https://claude.ai/oauth/mcp-oauth-client-metadata",
     "auth_method_or_pkce": "token_endpoint_auth_method none; grant_types authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:jwt-bearer",
     "uri_or_ssrf_rules": "redirect_uris is https://claude.ai/api/mcp/auth_callback; the client_id URL itself is on claude.ai",
     "draft_or_spec_version": "Live client metadata JSON checked 2026-10-30; the document does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_name": "Claude",
     "token_endpoint_auth_method": "none"
    },
    "source_url": "https://claude.ai/oauth/mcp-oauth-client-metadata"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp",
  "note": "Remote MCP connectors (OAuth or headers) and local `claude_desktop_config.json` servers; stateless `2026-07-28` rollout in progress."
 },
 {
  "id": "claude-agent-acp",
  "org_id": "agentclientprotocol",
  "name": "claude-agent-acp",
  "url": "https://github.com/agentclientprotocol/claude-agent-acp",
  "type": "sdk",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Claude Agent (claude-agent-acp)",
    "role": "External ACP adapter (Claude Agent SDK)",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "External adapter (`@agentclientprotocol/claude-agent-acp`) wrapping the `Claude Agent SDK` with `@-mentions`, terminals, subagents, and `/mcp`.",
    "full_detail_md": "Anthropic's Claude connects to ACP editors via the external `@agentclientprotocol/claude-agent-acp` adapter (`ACP wrapper for Anthropic's Claude` in the ACP Registry), which wraps the official `Claude Agent SDK` to support context `@-mentions`, images, tool permissions, interactive and background terminals, child subagent sessions, AIR diff-patch extensions, and `/mcp` server management.",
    "facets": {
     "role_in_acp": "External agent bridge / wrapper",
     "integration_mode": "External adapter (@agentclientprotocol/claude-agent-acp wrapping Claude Agent SDK)",
     "transport": "JSON-RPC 2.0 over stdio",
     "verification_posture": "Adapter repository README & ACP Registry listing (external SDK wrapper, not native CLI mode)",
     "sdk_or_package": "@agentclientprotocol/claude-agent-acp"
    },
    "telemetry": null,
    "source_url": "https://github.com/agentclientprotocol/claude-agent-acp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/agentclientprotocol/claude-agent-acp",
  "note": "External adapter (`@agentclientprotocol/claude-agent-acp`) wrapping the `Claude Agent SDK` with `@-mentions`, terminals, subagents, and `/mcp`."
 },
 {
  "id": "claude-api-skills",
  "org_id": "anthropic",
  "name": "Claude API",
  "url": "https://claude.com/resources/articles/skills",
  "type": "sdk",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Claude API",
    "role": "API runtime",
    "status": "Supported (preview)",
    "status_display": "Supported (preview) · as of 2025-10-16",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-16",
    "col4_md": "Exposes `/v1/skills` for Messages API skill versioning; requires the Code Execution Tool beta and standard `SKILL.md` frontmatter.",
    "full_detail_md": "Anthropic's Claude Developer Platform exposes the `/v1/skills` endpoint for programmatic skill versioning and attachment to Messages API requests; execution requires the Code Execution Tool beta environment and validates that `SKILL.md` frontmatter contains only the six standard properties (`name`, `description`, `license`, `compatibility`, `metadata`, `allowed-tools`).",
    "facets": {
     "transport_or_packaging": "HTTPS REST API (/v1/skills and Messages API requests)",
     "manifest_or_entry": "SKILL.md limited to the 6 standard frontmatter keys (packaged via package_skill.py)",
     "execution_or_sandbox": "Managed container requiring the Code Execution Tool beta",
     "verification_posture": "First-party release announcement (2025-10-16) and Claude Code portability documentation"
    },
    "telemetry": null,
    "source_url": "https://claude.com/resources/articles/skills"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://claude.com/resources/articles/skills",
  "note": "Exposes `/v1/skills` for Messages API skill versioning; requires the Code Execution Tool beta and standard `SKILL.md` frontmatter."
 },
 {
  "id": "claude-code",
  "org_id": "anthropic",
  "name": "Claude Code",
  "url": "https://code.claude.com/docs/en/skills",
  "type": "harness",
  "implements": [
   "agents-md",
   "anthropic-agent-skills-format",
   "cloudflare-markdown-for-agents",
   "llms-txt",
   "oauth-cimd"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Claude Code",
    "role": "CLI & IDE coding agent",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Loads `~/.claude/skills/<skill-name>/SKILL.md` on demand and adds Claude Code extensions (subagents, invocation control, dynamic context injection).",
    "full_detail_md": "Claude Code loads personal skills from `~/.claude/skills/<skill-name>/SKILL.md` and project skills on demand so the `SKILL.md` body is read only when invoked, and extends the 6-field Agent Skills standard with Claude Code-specific frontmatter and body features (invocation control, subagent execution, and dynamic context injection) that are not accepted by `claude.ai` uploads or the Skills API.",
    "facets": {
     "transport_or_packaging": "Local filesystem folders (~/.claude/skills/<skill-name>/SKILL.md) and plugin marketplaces",
     "manifest_or_entry": "SKILL.md with 6 standard frontmatter fields plus Claude Code-specific extension fields",
     "execution_or_sandbox": "Progressive disclosure with permission-gated allowed-tools, dynamic context injection, and subagent execution",
     "verification_posture": "First-party product documentation checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://code.claude.com/docs/en/skills"
   },
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Claude Code",
    "role": "Coding agent / IDE",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-05",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05",
    "col4_md": "Observed fetching (`Claude-Code` trailed `GPTBot` and `statespace-indexer` among named AI fetchers in Ahrefs study); automatic discovery, parsing, and answer use unconfirmed.",
    "full_detail_md": "Observed fetching `llms.txt` in Ahrefs' May 2026 server-log telemetry study, where `Claude-Code` trailed `GPTBot` and `statespace-indexer` among named AI fetchers and out-fetched every AI retrieval bot, AI assistant, and other AI training crawler; automatic discovery, parsing, and downstream answer use are not confirmed by server-log observation alone.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "Linked .md documentation pages",
     "content_type_or_bytes": "On-demand Markdown index consumption during coding tasks",
     "generator_or_consumer_mode": "Observed fetching (`Claude-Code` User-Agent in Ahrefs May 2026 server logs; automatic discovery, parsing, and answer use unconfirmed)"
    },
    "telemetry": null,
    "source_url": "https://ahrefs.com/blog/llmstxt-study/"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Anthropic (Claude Code)",
    "role": "Coding agent / CLI",
    "status": "Partial",
    "status_display": "Partial · as of 2026-11-02",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-02",
    "col4_md": "Reads `AGENTS.md` and `.claude/AGENTS.md` by default only when no `CLAUDE.md` exists in or above CWD.",
    "full_detail_md": "Requires Claude Code v2.1.277 or later (`dateModified` 2026-11-02). Under the default `claude-md-or-agents-md` mode, Claude reads `AGENTS.md` and `.claude/AGENTS.md` in the working directory and parent directories at session start—and lazily loads a subdirectory's `AGENTS.md` via the `Read` tool—only when no `CLAUDE.md`, `.claude/CLAUDE.md`, or `CLAUDE.local.md` exists in the working directory or above it (or loads both when `/config` sets `claude-md-and-agents-md`). Does not read `AGENTS.local.md`, `AGENTS.override.md`, or `.agents/`.",
    "facets": {
     "discovery_behavior": "Session-start scan of CWD and parent directories plus on-demand Read-tool loading in subdirectories (v2.1.277+)",
     "hierarchy_precedence": "Suppressed by default (claude-md-or-agents-md) if CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md exists in/above CWD; co-loaded after CLAUDE.md if set to claude-md-and-agents-md",
     "fallback_files": "CLAUDE.md; .claude/CLAUDE.md; CLAUDE.local.md; .claude/AGENTS.md (ignores AGENTS.override.md, AGENTS.local.md, .agents/)",
     "verification_posture": "Documented in Claude Code memory documentation (modified 2026-11-02)"
    },
    "telemetry": null,
    "source_url": "https://code.claude.com/docs/en/memory"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Anthropic, Claude Code",
    "role": "OAuth client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `client_name` Claude Code; loopback `redirect_uris` only.",
    "full_detail_md": "`https://claude.ai/oauth/claude-code-client-metadata` returned HTTP 200 `application/json`, with `client_id` equal to that URL, `client_name` Claude Code, and `token_endpoint_auth_method` `none`. `grant_types` are `authorization_code` and `refresh_token`, and `redirect_uris` are `http://localhost/callback` and `http://127.0.0.1/callback`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "Published client metadata JSON; client_name Claude Code; client_id equals the document URL",
     "auth_method_or_pkce": "token_endpoint_auth_method none; grant_types authorization_code and refresh_token; no code_challenge_methods_supported field in this document",
     "uri_or_ssrf_rules": "redirect_uris are only http://localhost/callback and http://127.0.0.1/callback; the client_id URL itself is https://claude.ai/oauth/claude-code-client-metadata",
     "draft_or_spec_version": "Live client metadata JSON checked 2026-10-30; the document does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_name": "Claude Code",
     "token_endpoint_auth_method": "none"
    },
    "source_url": "https://claude.ai/oauth/claude-code-client-metadata"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Anthropic Claude Code",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-02-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02-19",
    "col4_md": "`WebFetch` (`v2.1.38`) sends `Accept: text/markdown, text/html, */*` in Checkly's 2026-02-19 test.",
    "full_detail_md": "Anthropic's Claude Code Tools reference documents that `WebFetch` sets a `User-Agent` header beginning with `Claude-User` and an `Accept` header preferring Markdown over HTML. In Checkly's 2026-02-19 test of Claude Code (`v2.1.38`), `Fetch` sent `Accept: text/markdown, text/html, */*` (`User-Agent: axios/1.8.4`) without `q` values.",
    "facets": {
     "negotiation_or_artifact": "WebFetch prefers Markdown over HTML; Checkly recorded Fetch in v2.1.38 requesting text/markdown without q values, using header order",
     "response_headers": "Request Accept: text/markdown, text/html, */*; User-Agent prefix Claude-User (Checkly recorded axios/1.8.4). Cherny's 2025-11-13 post quotes Accept starting text/markdown, *",
     "content_type_or_tokens": "Requests text/markdown; no response token count is recorded for this client",
     "verification_posture": "Documented in Claude Code Tools reference and observed sending `Accept: text/markdown, text/html, */*` in Checkly's 2026-02-19 capture (`v2.1.38`)."
    },
    "telemetry": null,
    "source_url": "https://code.claude.com/docs/en/tools-reference"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://code.claude.com/docs/en/skills",
  "note": "Loads `~/.claude/skills/<skill-name>/SKILL.md` on demand and adds Claude Code extensions (subagents, invocation control, dynamic context injection)."
 },
 {
  "id": "claude-sep-990",
  "org_id": "anthropic",
  "name": "Claude Enterprise-Managed Authorization",
  "url": "https://claude.com/resources/articles/enterprise-managed-auth",
  "type": "harness",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Claude / Model Context Protocol SEP-990",
    "role": "MCP client and Enterprise-Managed Authorization profile",
    "status": "Partial",
    "status_display": "Partial · as of 2026-08-24",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-24",
    "col4_md": "Anthropic says enterprise-managed authorization is now generally available (August 24, 2026) and that enterprise-managed auth is the first implementation of the Enterprise-Managed Authorization extension to the Model Context Protocol. Admins provision MCP connectors through their identity provider, starting with Okta. SEP-990 is Status Final, Type Standards Track, Created 2025-06-04. The extension identifier is `io.modelcontextprotocol/enterprise-managed-authorization`. Protocol revision `2026-07-28`. The MCP client requests an Identity Assertion JWT Authorization Grant, or ID-JAG. Extensions are opt-in and never active by default.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://claude.com/resources/articles/enterprise-managed-auth"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://claude.com/resources/articles/enterprise-managed-auth",
  "note": "Anthropic says enterprise-managed authorization is now generally available (August 24, 2026) and that enterprise-managed auth is the first implementation of the Enterprise-Managed Authorization extension to the Model Context Protocol. Admins provision MCP connectors through their identity provider, starting with Okta. SEP-990 is Status Final, Type Standards Track, Created 2025-06-04. The extension"
 },
 {
  "id": "clerk-llms-txt",
  "org_id": "clerk",
  "name": "Clerk",
  "url": "https://clerk.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Clerk",
    "role": "Developer docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://clerk.com/llms.txt` (`# Clerk`, `text/plain`), documenting `.md` URL suffixes and linking Backend and Frontend OpenAPI specs.",
    "full_detail_md": "Serves `https://clerk.com/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 5,901 bytes, fetched 2026-11-04) opening `# Clerk`, instructing agents to append `.md` to any `/docs`, `/articles`, `/blog`, `/changelog`, or `/glossary` URL, and linking Backend (`https://clerk.com/openapi.json`) and Frontend OpenAPI specifications.",
    "facets": {
     "artifact_path": "https://clerk.com/llms.txt",
     "companion_files": "https://clerk.com/openapi.json; https://clerk.com/openapi.yaml; .md suffixes on /docs, /articles, /blog, /changelog, /glossary",
     "content_type_or_bytes": "text/plain; charset=utf-8 (5,901 bytes)",
     "generator_or_consumer_mode": "Root documentation index with .md URL suffix rule and OpenAPI specs"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Clerk"
    },
    "source_url": "https://clerk.com/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://clerk.com/llms.txt",
  "note": "Serves `https://clerk.com/llms.txt` (`# Clerk`, `text/plain`), documenting `.md` URL suffixes and linking Backend and Frontend OpenAPI specs."
 },
 {
  "id": "cleverbridge",
  "org_id": "cleverbridge",
  "name": "Cleverbridge",
  "url": "https://grow.cleverbridge.com/news/cleverbridge-visa-trusted-agent-protocol",
  "type": "authority",
  "implements": [
   "tap"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "tap",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Cleverbridge",
    "role": "Relying server / Gateway",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-02",
    "col4_md": "Cleverbridge's 2026-07-02 announcement says it is enabling and testing TAP and the Agentic Directory so the commerce platform can separate trusted agents from other traffic and set how approved agents reach the catalog and product data.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://grow.cleverbridge.com/news/cleverbridge-visa-trusted-agent-protocol"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://grow.cleverbridge.com/news/cleverbridge-visa-trusted-agent-protocol",
  "note": "Cleverbridge's 2026-07-02 announcement says it is enabling and testing TAP and the Agentic Directory so the commerce platform can separate trusted agents from other traffic and set how approved agents reach the catalog and product data."
 },
 {
  "id": "clickhouse-api-catalog",
  "org_id": "clickhouse",
  "name": "ClickHouse",
  "url": "https://clickhouse.com/.well-known/api-catalog",
  "type": "origin",
  "implements": [
   "api-catalog-rfc9727"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "ClickHouse",
    "role": "Cloud database API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Profiled `application/linkset+json` with `item` `https://api.clickhouse.cloud/v1` and an absolute `Link`.",
    "full_detail_md": "On 2026-11-04, `https://clickhouse.com/.well-known/api-catalog` returned HTTP 200 (`content-length: 593`) as `application/linkset+json` with profile `https://www.rfc-editor.org/info/rfc9727` and `Link: <https://clickhouse.com/.well-known/api-catalog>; rel=\"api-catalog\"`. The `item` href is `https://api.clickhouse.cloud/v1`, with `service-desc` on that same URL, two `service-doc` HTML pages, and `status` `https://status.clickhouse.com`.",
    "facets": {
     "well_known_endpoint": "https://clickhouse.com/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_relations": "item (https://api.clickhouse.cloud/v1); service-desc; service-doc (two HTML docs); status (https://status.clickhouse.com)",
     "http_or_link_header": "HTTP 200; Link: <https://clickhouse.com/.well-known/api-catalog>; rel=\"api-catalog\""
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_header_rel_api_catalog": true,
     "has_item_array": true
    },
    "source_url": "https://clickhouse.com/.well-known/api-catalog"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://clickhouse.com/.well-known/api-catalog",
  "note": "Profiled `application/linkset+json` with `item` `https://api.clickhouse.cloud/v1` and an absolute `Link`."
 },
 {
  "id": "cloudflare",
  "org_id": "cloudflare",
  "name": "Cloudflare Monetization Gateway",
  "url": "https://blog.cloudflare.com/monetization-gateway-beta/",
  "type": "venue",
  "implements": [
   "ai-crawler-tokens-robots",
   "cloudflare-content-signals-policy",
   "cloudflare-markdown-for-agents",
   "cloudflare-pay-per-crawl",
   "http-message-signatures",
   "nlweb",
   "tap",
   "webbotauth",
   "x402"
  ],
  "archetypes": [
   "crawler_policy",
   "harnesses_rpc_ui",
   "identity_auth_crypto",
   "payments_onchain",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Cloudflare Monetization Gateway",
    "role": "Platform",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-09-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-30",
    "col4_md": "Closed-beta HTTP 402 edge paywall and AI Gateway (`Payment-Method: x402`) settling USDC on Base via Coinbase's Facilitator.",
    "full_detail_md": "Launched in closed beta on September 30, 2026, Cloudflare Monetization Gateway lets domain owners gate websites, APIs, MCP tools, and datasets with HTTP 402 pricing rules settled in USDC on Base through Coinbase's x402 Facilitator, while Cloudflare AI Gateway accepts per-request inference payments via the `Payment-Method: x402` header.",
    "facets": {
     "settlement_rail": "Closed-beta HTTP 402 edge gateway settling via Coinbase x402 Facilitator",
     "supported_assets": "USDC stablecoin",
     "chains_or_networks": "Base blockchain",
     "headers_or_methods": "HTTP 402 edge pricing rules on URLs/headers/query params, plus `Payment-Method: x402` on Cloudflare AI Gateway"
    },
    "telemetry": null,
    "source_url": "https://blog.cloudflare.com/monetization-gateway-beta/"
   },
   {
    "protocol_id": "nlweb",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Cloudflare (AI Search NLWeb template)",
    "role": "NLWeb site",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-07-10",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-10",
    "col4_md": "The AI Search template crawls a site, indexes it, and deploys NLWeb endpoints. Docs (updated 2026-07-10) mark it a public preview and name `/mcp` as the NLWeb MCP server endpoint for trusted agents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/ai-search/how-to/nlweb/index.md"
   },
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cloudflare",
    "role": "CDN / Edge",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-22",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-22",
    "col4_md": "Bot Preference Sync writes managed robots.txt from the zone's Search, Agent, and Training policies when at least one policy is Block, Block on pages with ads, or, for Training, Disallow. Cloudflare prepends those directives and the Content Signals Policy to the zone's existing robots.txt (docs last updated 22 October 2026). `https://www.cloudflare.com/robots.txt` and `https://contentsignals.org/robots.txt` both serve `Content-Signal: ai-train=yes, search=yes, ai-input=yes`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/bots/additional-configurations/managed-robots-txt/"
   },
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Cloudflare",
    "role": "CDN / WAF verifier",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-08",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-08",
    "col4_md": "Validates edge signatures per `draft-meunier-web-bot-auth-architecture-02` and `draft-meunier-http-message-signatures-directory-03` structured-string `Signature-Agent` headers; Verified bots declare Web Bot Auth, IP, or reverse DNS identity, and BotBase tracks Direct versus Intermediary access.",
    "full_detail_md": "Automatically validates Web Bot Auth signatures on the Cloudflare edge for Verified Bots and Signed Agents; graded partial because the verifier documentation (updated 2026-10-08) implements a subset of RFC 9421 and `draft-meunier-http-message-signatures-directory-03` structured-string `Signature-Agent` syntax rather than the `draft-ietf-webbotauth-httpsig-protocol-01` dictionary syntax. The Verified bots page, last updated Nov 2, 2026, says honest self-identification is a cryptographic Web Bot Auth signature, a published IP list with a stable user-agent, or reverse DNS, and that a Verified bot obeys robots.txt and crawl directives. As of July 1, 2026, BotBase expresses the distinction between a Verified bot and a signed agent as Direct versus Intermediary access, which tracks who can operate the bot.",
    "facets": {
     "signature_or_key_format": "Implements `draft-meunier-http-message-signatures-directory-03` (RFC 9421 subset)",
     "directory_or_header": "Requires `Signature-Agent` as structured string (`\"https://signature-agent.test\"`); rejects dictionary form `sig2=\"https://signature-agent.test\"`",
     "signing_algorithm": "HTTP Message Signatures (RFC 9421 subset)",
     "verification_role": "CDN / WAF edge verifier. Verified-bot identity is a Web Bot Auth signature, a published IP list, or reverse DNS, and BotBase tracks Direct versus Intermediary access."
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Cloudflare",
    "role": "CDN / WAF verifier (Web Bot Auth profile)",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-08",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-08",
    "col4_md": "Web Bot Auth edge verifier (`draft-meunier-http-message-signatures-directory-03`); supports RFC 9421 subset and rejects dictionary `Signature-Agent`.",
    "full_detail_md": "Validates Web Bot Auth cryptographic signatures at the Cloudflare edge for Verified Bots and Signed Agents. Graded partial because Cloudflare's documentation (updated 2026-10-08) targets `draft-meunier-http-message-signatures-directory-03` expecting `Signature-Agent` as a structured string (`\"https://signature-agent.test\"`), fails verification when sent the dictionary form (`sig2=\"https://signature-agent.test\"`), and supports only a subset of RFC 9421 components and parameters.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth profile (`draft-meunier-http-message-signatures-directory-03`; RFC 9421 subset)",
     "signature_fields": "`Signature`, `Signature-Input`, and structured-string `Signature-Agent` (rejects dictionary `sig2=\"https://signature-agent.test\"`)",
     "algorithms_or_keys": "HTTP Message Signatures (RFC 9421 subset) against JWKS key directories",
     "verification_posture": "CDN / WAF edge verifier (Cloudflare Bot Management / Verified Bots)"
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/"
   },
   {
    "protocol_id": "tap",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Cloudflare",
    "role": "CDN / WAF verifier",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-24",
    "col4_md": "Merchants set the rules and use Cloudflare as the validator. TAP uses Web Bot Auth so Cloudflare can verify agents that registered with the payment network. Browsing signatures use tag `agent-browser-auth`. Payment signatures use tag `agent-payer-auth`. Post dated 2025-10-24.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://blog.cloudflare.com/secure-agentic-commerce/"
   },
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Cloudflare Managed robots.txt",
    "role": "Managed policy publisher",
    "status": "Partial",
    "status_display": "Partial · as of 2026-11-02",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": "2026-11-02",
    "col4_md": "Bot Preference Sync generates managed `robots.txt` directives from Search, Agent, and Training policies (including `Content-Signal: search=yes, ai-train=no`); `robots.txt` compliance remains voluntary.",
    "full_detail_md": "Bot Preference Sync generates managed `robots.txt` directives from Search, Agent, and Training policies when at least one policy is set to Block, Block on pages with ads, or, for Training, Disallow. `robots.txt` compliance is voluntary: the file expresses preferences and does not prevent crawlers from accessing content at a technical level. The managed service also publishes exclusions and AI-training preferences (`Content-Signal: search=yes, ai-train=no`, omitting `ai-input`) across more than 3.8 million customer domains; Cloudflare states that these signals express operator preferences and are not technical countermeasures against scraping, so technical enforcement requires separate WAF or bot-management controls.",
    "facets": {
     "scope_host": ">3.8M Cloudflare-managed customer domains",
     "policy_role": "Managed policy publisher (declares exclusions and preferences; not a technical countermeasure by itself)",
     "published_rules": [
      {
       "tokens": [
        "User-Agent: *"
       ],
       "directives": [
        "Content-Signal: search=yes, ai-train=no",
        "Allow: /"
       ]
      }
     ],
     "content_signals": "Bot Preference Sync generates managed robots.txt directives from Search, Agent, and Training policies. Content-Signal: search=yes, ai-train=no expresses preferences; robots.txt compliance is voluntary and technical enforcement requires separate controls."
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/bots/additional-configurations/managed-robots-txt/"
   },
   {
    "protocol_id": "cloudflare-pay-per-crawl",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Cloudflare",
    "role": "Edge platform & Merchant of Record",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-07-28",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-07-28",
    "col4_md": "Closed/private beta edge gateway returning HTTP 402 (`crawler-price`) or HTTP 200 (`crawler-charged`) as Merchant of Record.",
    "full_detail_md": "Operates Pay Per Crawl in private/closed beta (introduced 2025-07-01; documentation updated 2026-07-28) as both technical infrastructure and Merchant of Record. After existing WAF policies and Bot Management rules run, Cloudflare enforces per-crawler Allow, Charge, or Block rules: unaccepted requests receive `HTTP/2 402 Payment Required` with `crawler-price` (for example, `crawler-price: USD 0.01`), whereas Web Bot Auth-signed requests carrying `crawler-exact-price` or `crawler-max-price` receive `HTTP 200` with `crawler-charged` (or `HTTP/2 402` with `crawler-error: InvalidCrawlerExactPrice`). Since 2025-12-10 and 2026-06-16, Cloudflare also exposes the signed Discovery API (`GET https://crawlers-api.ai-audit.cfdata.org/charged_zones`), per-URI Configuration Rule exemptions, and dynamic pricing via origin `crawler-price` response headers or Cloudflare Workers (`cf-pay-per-crawl`).",
    "facets": {
     "scope_host": "Cloudflare-proxied customer zones and GET https://crawlers-api.ai-audit.cfdata.org/charged_zones",
     "policy_or_enforcement_role": "Edge gateway and Merchant of Record enforcing Allow, Charge, or Block after WAF and Bot Management rules",
     "pricing_or_headers": "HTTP 402 with crawler-price (e.g., USD 0.01), request headers crawler-exact-price or crawler-max-price, HTTP 200 with crawler-charged, error header crawler-error, and origin header cf-pay-per-crawl",
     "auth_mechanism": "Web Bot Auth (RFC 9421 Ed25519 HTTP Message Signatures via Signature-Agent, Signature-Input, and Signature covering the payment header)",
     "beta_or_availability_posture": "Closed / private beta (introduced 2025-07-01; docs updated 2026-07-28; latest changelog entry 2026-06-16)"
    },
    "telemetry": null,
    "source_url": "https://blog.cloudflare.com/introducing-pay-per-crawl/"
   },
   {
    "protocol_id": "cloudflare-pay-per-crawl",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Cloudflare Web Bot Auth",
    "role": "Crawler authentication & signing SDKs",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-08",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-10-08",
    "col4_md": "Ed25519 `RFC 9421` request signing (`Signature-Agent`, `Signature-Input`, `Signature`) covering `crawler-exact-price` or `crawler-max-price`; subset of `RFC 9421` supported.",
    "full_detail_md": "Paid crawling and Discovery API queries (`GET https://crawlers-api.ai-audit.cfdata.org/charged_zones`) require crawlers to comply with Web Bot Auth by hosting an Ed25519 JWK directory at `/.well-known/http-message-signatures-directory` (`application/http-message-signatures-directory+json`) and signing requests with `Signature-Agent`, `Signature-Input`, and `Signature` headers that include `crawler-exact-price` or `crawler-max-price` in the signed `signature-input` components. Cloudflare publishes unaudited TypeScript and Rust `web-bot-auth` reference libraries implementing `draft-meunier-webbotauth-httpsig-protocol-00` and notes that its verifier does not support every component and parameter defined in IETF `RFC 9421`.",
    "facets": {
     "scope_host": "https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/ and https://raw.githubusercontent.com/cloudflare/web-bot-auth/main/README.md",
     "policy_or_enforcement_role": "Mandatory cryptographic bot identity layer for Pay Per Crawl paid requests and Discovery API queries",
     "pricing_or_headers": "Requires crawler-exact-price or crawler-max-price to be covered inside Signature-Input alongside @authority and signature-agent",
     "auth_mechanism": "Ed25519 HTTP Message Signatures (IETF RFC 9421 subset / draft-meunier-webbotauth-httpsig-protocol-00) with JWKS directory at /.well-known/http-message-signatures-directory",
     "beta_or_availability_posture": "Verifier active on Cloudflare edge (docs updated 2026-10-08); unaudited TypeScript and Rust reference libraries"
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cloudflare (Edge network, Developer Docs & Blog)",
    "role": "Edge network & documentation",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Per-zone edge conversion (`Accept: text/markdown` -> `text/markdown; charset=utf-8`, `content-signal: ai-train=yes, search=yes, ai-input=yes`); live on Docs and Blog.",
    "full_detail_md": "Generally Available as of 2026-11-09 (Beta launch 2026-02-12), enabled per zone at no cost for Pro, Business, and Enterprise plans and SSL for SaaS customers (enable via AI Crawl Control or PATCH `/client/v4/zones/{zone_tag}/settings/content_converter` with `{\"value\": \"on\"}`; HTML conversion capped at 6 MiB / 6,291,456 bytes decompressed). Clients sending `Accept: text/markdown` receive `content-type: text/markdown; charset=utf-8` with `vary: accept-encoding, accept` and default `content-signal: ai-train=yes, search=yes, ai-input=yes` (`x-markdown-tokens` documented at launch). Live probes of Cloudflare Developer Documentation and Blog on 2026-11-04 both returned `HTTP 200` with `content-type: text/markdown; charset=utf-8` and `content-signal: ai-train=yes, search=yes, ai-input=yes`.",
    "facets": {
     "negotiation_or_artifact": "Per-zone edge conversion of origin HTML when the request Accept includes text/markdown (dashboard toggle or PATCH content_converter value on), live on developers.cloudflare.com and blog.cloudflare.com",
     "response_headers": "HTTP 200; content-type: text/markdown; charset=utf-8; vary: accept-encoding, accept; default content-signal: ai-train=yes, search=yes, ai-input=yes; x-markdown-tokens documented at launch",
     "content_type_or_tokens": "text/markdown; charset=utf-8, capped at 6 MiB (6,291,456 bytes) of decompressed HTML",
     "verification_posture": "Live HTTP 200 probes of developers.cloudflare.com and blog.cloudflare.com checked 2026-11-04 plus vendor docs (modified 2026-10-09) and 2026-02-12 launch post"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "content_signal": "ai-train=yes, search=yes, ai-input=yes",
     "vary": "accept-encoding, accept"
    },
    "source_url": "https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.cloudflare.com/monetization-gateway-beta/",
  "note": "Closed-beta HTTP 402 edge paywall and AI Gateway (`Payment-Method: x402`) settling USDC on Base via Coinbase's Facilitator."
 },
 {
  "id": "cloudflare-agent-readiness",
  "org_id": "cloudflare",
  "name": "Cloudflare Agent Readiness",
  "url": "https://blog.cloudflare.com/agent-readiness/",
  "type": "authority",
  "implements": [
   "api-catalog-rfc9727"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cloudflare Agent Readiness",
    "role": "Readiness checker",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-17",
    "col4_md": "`isitagentready.com` scores API Catalog (RFC 9727) under Capabilities by requesting the entered site.",
    "full_detail_md": "Cloudflare's Agent Readiness post (André Jesus and Vance Morrison, `datePublished` 2026-04-17) names `isitagentready.com` as the checker: entering a site makes Cloudflare request it and score four dimensions. Capabilities includes API Catalog (RFC 9727), alongside Agent Skills, OAuth server discovery via RFC 8414 and RFC 9728, MCP Server Card, and WebMCP.",
    "facets": {
     "well_known_endpoint": "/.well-known/api-catalog (scored capability, hosted location named in the post)",
     "content_type_or_profile": "API Catalog (RFC 9727) linkset discovery, checked as a Capabilities item",
     "link_relations": "Checker looks for the RFC 9727 catalog; the post also names Link Headers (RFC 8288) under Discoverability",
     "http_or_link_header": "Doc-cited: Cloudflare requests the entered site; Capabilities includes API Catalog (RFC 9727)"
    },
    "telemetry": null,
    "source_url": "https://blog.cloudflare.com/agent-readiness/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.cloudflare.com/agent-readiness/",
  "note": "`isitagentready.com` scores API Catalog (RFC 9727) under Capabilities by requesting the entered site."
 },
 {
  "id": "cloudflare-agents-sdk",
  "org_id": "cloudflare",
  "name": "Cloudflare Agents SDK",
  "url": "https://developers.cloudflare.com/agents/model-context-protocol/",
  "type": "sdk",
  "implements": [
   "cloudflare-markdown-for-agents",
   "mcp",
   "mpp",
   "x402"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "payments_onchain",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Cloudflare Agents SDK",
    "role": "Server & client runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-27",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "Workers runtime supporting stateless `2026-07-28` MCP servers, `Streamable HTTP`, `insufficientScope()` OAuth challenges, and `MCPClientManager`.",
    "full_detail_md": "Cloudflare's Agents SDK enables developers to deploy remote MCP servers on Cloudflare Workers with day-zero support for stateless revision `2026-07-28`, `Streamable HTTP`, granular OAuth `insufficientScope()` step-up challenges, Code Mode tool loading, and `MCPClientManager` client connections.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1 with insufficientScope() step-up authorization",
     "primitives": "tools, prompts, resources, elicitation",
     "sdk_or_package": "Cloudflare Agents SDK (MCPClientManager)"
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/agents/model-context-protocol/"
   },
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Cloudflare Agents SDK",
    "role": "Agent SDK / runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-04",
    "col4_md": "Supports x402 transactions in Cloudflare Agents SDK and MCP integrations, paired with Cloudflare Wallets for stablecoin payments.",
    "full_detail_md": "Cloudflare shipped x402 support in the Cloudflare Agents SDK and its MCP integrations on September 23, 2025 (while proposing the `deferred` payment scheme), and announced Cloudflare Wallets on August 4, 2026 so agents can store stablecoins and pay x402-compatible endpoints and Monetization Gateway origins.",
    "facets": {
     "settlement_rail": "x402 HTTP and MCP tool payment integration with programmable stablecoin wallets",
     "supported_assets": "Stablecoins",
     "chains_or_networks": "x402-compatible stablecoin networks",
     "headers_or_methods": "Agents SDK x402 client/MCP integrations and Cloudflare Wallets handles"
    },
    "telemetry": null,
    "source_url": "https://blog.cloudflare.com/x402/"
   },
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Cloudflare Agents SDK",
    "role": "Agent SDK / runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-05",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-05",
    "col4_md": "Agents SDK pays HTTP and MCP tools via `mppx`; the example creates `tempo.charge`.",
    "full_detail_md": "The Cloudflare Agents SDK pays HTTP services and Model Context Protocol (MCP) tools with MPP, and the mppx SDK handles payment retries. Docs say MPP standardizes the HTTP 402 Payment Required status code and supports stablecoins, cards through Stripe, and custom payment methods, with intents charge, session, and subscription; the SDK example creates tempo.charge.",
    "facets": {
     "settlement_rail": "Stablecoins, cards through Stripe, and custom payment methods",
     "challenge_or_scheme": "Intents charge, session, and subscription on the HTTP 402 Payment scheme",
     "headers_or_methods": "HTTP 402 Payment Required; mppx handles payment retries for HTTP and MCP calls",
     "sdk_or_endpoint": "Cloudflare Agents SDK example creates tempo.charge"
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/agents/tools/payments/mpp/pay-from-agents-sdk/"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cloudflare Agents SDK",
    "role": "SDK tool",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-12",
    "col4_md": "Agents SDK `web_fetch` tool requests Markdown directly from supporting sites (2026-10-12).",
    "full_detail_md": "The Agents SDK `web_fetch` tool, announced 12 October 2026, reads webpages and documents and requests Markdown directly from sites that support Markdown for Agents, then formats JSON for the model.",
    "facets": {
     "negotiation_or_artifact": "Agents SDK web_fetch reads webpages and documents and requests Markdown from sites that support Markdown for Agents",
     "response_headers": "Requests Markdown directly; the changelog does not publish the Accept string. JSON is formatted for the model",
     "content_type_or_tokens": "Markdown from supporting sites, then JSON for the model",
     "verification_posture": "Cloudflare AI changelog announcement dated 2026-10-12 (checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/changelog/product-group/ai/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.cloudflare.com/agents/model-context-protocol/",
  "note": "Workers runtime supporting stateless `2026-07-28` MCP servers, `Streamable HTTP`, `insufficientScope()` OAuth challenges, and `MCPClientManager`."
 },
 {
  "id": "cloudflare-ai-crawl-control",
  "org_id": "cloudflare-ai-crawl-control",
  "name": "Cloudflare AI Crawl Control",
  "url": "https://developers.cloudflare.com/changelog/post/2025-10-21-track-robots-txt/",
  "type": "authority",
  "implements": [
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cloudflare AI Crawl Control",
    "role": "Validator / CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-21",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-21",
    "col4_md": "The Robots.txt tab (changelog 21 October 2025) checks whether a zone's robots.txt contains Content Signals directives for AI training, search, and AI input.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/changelog/post/2025-10-21-track-robots-txt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.cloudflare.com/changelog/post/2025-10-21-track-robots-txt/",
  "note": "The Robots.txt tab (changelog 21 October 2025) checks whether a zone's robots.txt contains Content Signals directives for AI training, search, and AI input."
 },
 {
  "id": "cloudflare-as-meta",
  "org_id": "cloudflare",
  "name": "Cloudflare MCP authorization server",
  "url": "https://mcp.cloudflare.com",
  "type": "authority",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Cloudflare",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-31",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-31",
    "as_of": "2026-10-31",
    "col4_md": "`issuer` `https://mcp.cloudflare.com`; `S256`; `authorization_code`, `refresh_token`; `client_id_metadata_document_supported` `true`; `registration_endpoint`; 403 scopes.",
    "full_detail_md": "GET https://mcp.cloudflare.com/.well-known/oauth-authorization-server returned HTTP 200 `application/json`. `issuer` is `https://mcp.cloudflare.com`. `authorization_endpoint`, `token_endpoint`, and `registration_endpoint` are on that host. `protected_resources` is `https://mcp.cloudflare.com/mcp`. `grant_types_supported` are `authorization_code` and `refresh_token`. `code_challenge_methods_supported` is `S256`. `client_id_metadata_document_supported` is `true`. `scopes_supported` lists 403 values, starting with `offline_access`, `user:read`, and `account:read`. Checked 2026-10-31.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.cloudflare.com/.well-known/oauth-authorization-server (issuer https://mcp.cloudflare.com; protected_resources https://mcp.cloudflare.com/mcp; registration_endpoint https://mcp.cloudflare.com/register)",
     "registration_or_client_id_modes": "Dynamic registration endpoint on the issuer host; client_id_metadata_document_supported true; token_endpoint_auth_methods client_secret_basic, client_secret_post, none, private_key_jwt (RS256, ES256)",
     "pkce_or_grant_types": "PKCE S256; grant_types_supported authorization_code and refresh_token",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-10-31); scopes_supported lists 403 values"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://mcp.cloudflare.com",
     "scopes_supported_count": 403,
     "client_id_metadata_document_supported": true
    },
    "source_url": "https://mcp.cloudflare.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://mcp.cloudflare.com/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://mcp.cloudflare.com`; `S256`; `authorization_code`, `refresh_token`; `client_id_metadata_document_supported` `true`; `registration_endpoint`; 403 scopes."
 },
 {
  "id": "cloudflare-browser-run-crawl",
  "org_id": "cloudflare-browser-run-crawl",
  "name": "Cloudflare Browser Run /crawl",
  "url": "https://developers.cloudflare.com/changelog/post/2026-08-31-crawl-content-use/",
  "type": "agent",
  "implements": [
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cloudflare Browser Run /crawl",
    "role": "AI crawler",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-31",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-31",
    "col4_md": "The `/crawl` endpoint (changelog 31 August 2026) enforces the Content Signals `use` directive and the yes/no purpose directives `search`, `ai-input`, and `ai-train`. Cloudflare says Content Signals are trust-based.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/changelog/post/2026-08-31-crawl-content-use/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.cloudflare.com/changelog/post/2026-08-31-crawl-content-use/",
  "note": "The `/crawl` endpoint (changelog 31 August 2026) enforces the Content Signals `use` directive and the yes/no purpose directives `search`, `ai-input`, and `ai-train`. Cloudflare says Content Signals are trust-based."
 },
 {
  "id": "cloudflare-content-signals-policy",
  "org_id": "cloudflare",
  "name": "Cloudflare Content Signals Policy",
  "url": "https://blog.cloudflare.com/content-signals-policy/",
  "type": "authority",
  "implements": [
   "aipref-vocabulary"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-vocabulary",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Cloudflare Content Signals Policy",
    "role": "Platform",
    "status": "Partial",
    "status_display": "Partial · as of 2026-09-15",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-15",
    "col4_md": "`draft-romm-aipref-contentsignals-00` Table 1 maps Search to `search`, AI Input to `ai-input`, and AI Training to `ai-train`. Michael Tremante called Cloudflare's Content Signal Policy an interim measure and wrote that they will revisit the policy once a consensus position has happened. Bryan Becker wrote that as standards such as `ai-prefs` mature, Cloudflare will revisit this approach. The September 15, 2026 press release says today's controls are designed to work alongside these emerging standards.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://datatracker.ietf.org/doc/html/draft-romm-aipref-contentsignals-00"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://datatracker.ietf.org/doc/html/draft-romm-aipref-contentsignals-00",
  "note": "`draft-romm-aipref-contentsignals-00` Table 1 maps Search to `search`, AI Input to `ai-input`, and AI Training to `ai-train`. Michael Tremante called Cloudflare's Content Signal Policy an interim measure and wrote that they will revisit the policy once a consensus position has happened. Bryan Becker wrote that as standards such as `ai-prefs` mature, Cloudflare will revisit this approach. The Septe"
 },
 {
  "id": "cloudflare-developer-documentation",
  "org_id": "cloudflare",
  "name": "Cloudflare Developer Documentation",
  "url": "https://developers.cloudflare.com/llms.txt",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file",
   "api-catalog-rfc9727",
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cloudflare (Developer docs)",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `https://developers.cloudflare.com/llms.txt` as `text/plain` (`# Cloudflare Developer Documentation`), linking each Cloudflare product to its own `llms.txt` index.",
    "full_detail_md": "Serves `https://developers.cloudflare.com/llms.txt` as `text/plain; charset=utf-8` (45,365 bytes, fetched 2026-10-30). The file opens `# Cloudflare Developer Documentation` and acts as a master directory where each Cloudflare product links to its own subpath `llms.txt` containing that product's full page index.",
    "facets": {
     "artifact_path": "https://developers.cloudflare.com/llms.txt",
     "companion_files": "Per-product subpath llms.txt indexes across Cloudflare products",
     "content_type_or_bytes": "text/plain; charset=utf-8 (45,365 bytes)",
     "generator_or_consumer_mode": "Master product directory linking per-product llms.txt indexes"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "marker": "# Cloudflare Developer Documentation",
     "content_type": "text/plain; charset=utf-8"
    },
    "source_url": "https://developers.cloudflare.com/llms.txt"
   },
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cloudflare Developer Documentation",
    "role": "Docs platform",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Level 2 catalog, `Content-Type: application/ai-catalog+json`, `identifier` `did:web:developers.cloudflare.com`, indexing the REST OpenAPI document, the MCP Servers card, the Agent Skills index, and `llms.txt`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/.well-known/ai-catalog.json"
   },
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cloudflare Developer Documentation",
    "role": "Developer docs API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Profiled `application/linkset+json` anchored at `https://developers.cloudflare.com/api/` with `service-desc`, not `item`.",
    "full_detail_md": "On 2026-11-04, `https://developers.cloudflare.com/.well-known/api-catalog` returned HTTP 200 (`content-length: 351`) as `application/linkset+json` with profile `https://www.rfc-editor.org/info/rfc9727`, and the response did not include a `Link` header or an `item` array. The single anchor `https://developers.cloudflare.com/api/` carries `service-desc` `https://developers.cloudflare.com/openapi.json`, `service-doc` on the same API path, and `status` `https://www.cloudflarestatus.com/api/v2/status.json`.",
    "facets": {
     "well_known_endpoint": "https://developers.cloudflare.com/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_relations": "service-desc (openapi.json); service-doc (https://developers.cloudflare.com/api/); status; no item array",
     "http_or_link_header": "HTTP 200; no Link rel=api-catalog response header"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_header_rel_api_catalog": false,
     "has_item_array": false
    },
    "source_url": "https://developers.cloudflare.com/.well-known/api-catalog"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.cloudflare.com/llms.txt",
  "note": "Serves `https://developers.cloudflare.com/llms.txt` as `text/plain` (`# Cloudflare Developer Documentation`), linking each Cloudflare product to its own `llms.txt` index."
 },
 {
  "id": "cloudflare-docs-mcp",
  "org_id": "cloudflare",
  "name": "Cloudflare Documentation MCP Server",
  "url": "https://docs.mcp.cloudflare.com/mcp",
  "type": "origin",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Cloudflare Docs",
    "role": "Remote MCP server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Streamable HTTP at `https://docs.mcp.cloudflare.com/mcp` (`docs-ai-search` `0.5.0`) advertising `2026-07-28`, `tools`, and `prompts`.",
    "full_detail_md": "Cloudflare hosts a public Streamable HTTP documentation server at `https://docs.mcp.cloudflare.com/mcp` (`docs-ai-search` v`0.5.0`) supporting stateless MCP revision `2026-07-28` (`resultType: \"complete\"`, `cacheScope: \"private\"`) with `tools` and `prompts` capabilities alongside managed account MCP servers.",
    "facets": {
     "transport": "Streamable HTTP",
     "auth_or_oauth": "Public (no auth for docs); OAuth 2.1 on account servers",
     "primitives": "tools, prompts",
     "sdk_or_package": "docs-ai-search v0.5.0"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "spec_version": "2026-07-28",
     "server_name": "docs-ai-search",
     "server_version": "0.5.0"
    },
    "source_url": "https://docs.mcp.cloudflare.com/mcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.mcp.cloudflare.com/mcp",
  "note": "Streamable HTTP at `https://docs.mcp.cloudflare.com/mcp` (`docs-ai-search` `0.5.0`) advertising `2026-07-28`, `tools`, and `prompts`."
 },
 {
  "id": "cloudflare-radar",
  "org_id": "cloudflare-radar",
  "name": "Cloudflare Radar",
  "url": "https://assets.radar.cloudflare.com/bots/signature-agent-registry.txt",
  "type": "authority",
  "implements": [
   "web-bot-auth-signature-agent-card"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "web-bot-auth-signature-agent-card",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Cloudflare Radar",
    "role": "Key directory publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "https://assets.radar.cloudflare.com/bots/signature-agent-registry.txt returned status 200 on 2026-10-29 as a newline-delimited registry of 500 https URLs of signed bot key directories, in the section 4.2 registry shape. Quoted entries include https://assistbot.duckduckgo.com/.well-known/http-message-signatures-directory and https://chatgpt.com/.well-known/http-message-signatures-directory, plus Cloudflare Browser Rendering workers and regional Amazon Bedrock AgentCore signer endpoints.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://assets.radar.cloudflare.com/bots/signature-agent-registry.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://assets.radar.cloudflare.com/bots/signature-agent-registry.txt",
  "note": "https://assets.radar.cloudflare.com/bots/signature-agent-registry.txt returned status 200 on 2026-10-29 as a newline-delimited registry of 500 https URLs of signed bot key directories, in the section 4.2 registry shape. Quoted entries include https://assistbot.duckduckgo.com/.well-known/http-message-signatures-directory and https://chatgpt.com/.well-known/http-message-signatures-directory, plus Cl"
 },
 {
  "id": "cloudflare-workers-client",
  "org_id": "cloudflare",
  "name": "web-bot-auth Workers client",
  "url": "https://github.com/cloudflare/web-bot-auth",
  "type": "sdk",
  "implements": [
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Cloudflare Workers",
    "role": "Reference client",
    "status": "Reference implementation (pre-WG draft)",
    "status_display": "Reference implementation (pre-WG draft) · as of 2026-10-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Open-source TypeScript reference client in Appendix F.1 (`https://github.com/cloudflare/web-bot-auth`) targeting `draft-meunier-webbotauth-httpsig-protocol-00`; `draft-ietf-webbotauth-httpsig-protocol-01` conformance not established.",
    "full_detail_md": "Listed in Appendix F.1 of `draft-ietf-webbotauth-httpsig-protocol-01` at `https://github.com/cloudflare/web-bot-auth` as a TypeScript Cloudflare Workers reference client grouped under `draft-meunier-webbotauth-httpsig-protocol-00`.",
    "facets": {
     "signature_or_key_format": "HTTP Message Signatures (`draft-meunier-webbotauth-httpsig-protocol-00`)",
     "directory_or_header": "`cloudflare/web-bot-auth` TypeScript Workers client",
     "signing_algorithm": "HTTP Message Signatures",
     "verification_role": "Reference client (TypeScript implementation listed in IETF draft Appendix F.1)"
    },
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-ietf-webbotauth-httpsig-protocol-01.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ietf.org/archive/id/draft-ietf-webbotauth-httpsig-protocol-01.txt",
  "note": "Open-source TypeScript reference client in Appendix F.1 (`https://github.com/cloudflare/web-bot-auth`) targeting `draft-meunier-webbotauth-httpsig-protocol-00`; `draft-ietf-webbotauth-httpsig-protocol-01` conformance not established."
 },
 {
  "id": "codecompanion-nvim",
  "org_id": "codecompanion",
  "name": "CodeCompanion.nvim",
  "url": "https://codecompanion.olimorris.dev/agent-client-protocol",
  "type": "harness",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "CodeCompanion.nvim",
    "role": "Community Neovim client plugin",
    "status": "Partial",
    "status_display": "Partial · as of 2025-08-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-08-27",
    "col4_md": "Neovim plugin supporting `JSON-RPC 2.0` sessions, `readTextFile`, and `writeTextFile`; omits agent plans and terminals.",
    "full_detail_md": "CodeCompanion.nvim (initial ACP support added in `17.18.0` on `2025-08-27`) implements an ACP client in Neovim supporting `JSON-RPC 2.0`, streaming responses, message buffering, session create/list/load, MCP server forwarding, tool permission diff previews, and `readTextFile`/`writeTextFile`, while documenting that agent execution plans and Neovim terminal operations are unsupported.",
    "facets": {
     "role_in_acp": "Editor plugin client",
     "integration_mode": "Community Neovim plugin with explicit capability matrix (omits agent plans and terminals)",
     "transport": "JSON-RPC 2.0 over stdio",
     "verification_posture": "Plugin feature-matrix documentation & changelog (17.18.0, 2025-08-27)",
     "sdk_or_package": "olimorris/codecompanion.nvim"
    },
    "telemetry": null,
    "source_url": "https://codecompanion.olimorris.dev/agent-client-protocol"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://codecompanion.olimorris.dev/agent-client-protocol",
  "note": "Neovim plugin supporting `JSON-RPC 2.0` sessions, `readTextFile`, and `writeTextFile`; omits agent plans and terminals."
 },
 {
  "id": "codex",
  "org_id": "openai",
  "name": "Codex",
  "url": "https://learn.chatgpt.com/docs/build-skills",
  "type": "harness",
  "implements": [
   "agents-md",
   "anthropic-agent-skills-format",
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "OpenAI Codex",
    "role": "Coding agent & app",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Scans `$CWD/.agents/skills`, `$REPO_ROOT/.agents/skills`, `$HOME/.agents/skills`, and `/etc/codex/skills` for `SKILL.md` (plus optional `agents/openai.yaml`), capping startup metadata via `skills.max_context_tokens`.",
    "full_detail_md": "ChatGPT and Codex implement the Agent Skills standard across the ChatGPT desktop app, `Codex CLI`, and IDE extension, scanning `$CWD/.agents/skills`, `$REPO_ROOT/.agents/skills`, `$HOME/.agents/skills`, and `/etc/codex/skills` for `SKILL.md` folders (with optional `agents/openai.yaml` metadata) and capping startup discovery metadata at 2% of the context window or 8,000 characters (configurable up to 10,000 tokens via `skills.max_context_tokens`).",
    "facets": {
     "transport_or_packaging": "Filesystem directories ($CWD/.agents/skills, $REPO_ROOT/.agents/skills, $HOME/.agents/skills, /etc/codex/skills) and plugins",
     "manifest_or_entry": "SKILL.md (required name and description) plus optional agents/openai.yaml",
     "execution_or_sandbox": "Two-stage progressive disclosure (@ or $skill explicit or implicit invocation; instruction-only default)",
     "verification_posture": "First-party OpenAI documentation checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://learn.chatgpt.com/docs/build-skills"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "OpenAI Codex",
    "role": "Coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2025-05-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-05-16",
    "col4_md": "Guided by repository `AGENTS.md` files since `2025-05-16`; in configuration docs (checked `2026-10-30`), reads `~/.codex` and walks root-to-CWD loading `AGENTS.override.md` or `AGENTS.md`, concatenating closer files last.",
    "full_detail_md": "Introduced repository `AGENTS.md` guidance at launch on `2025-05-16`. In OpenAI's Custom instructions documentation (checked `2026-10-30`), Codex reads global guidance from `~/.codex` (`CODEX_HOME`, preferring `AGENTS.override.md` over `AGENTS.md`) before doing any work and then walks from the Git project root down to the current working directory, selecting at most one file per directory in order `AGENTS.override.md`, `AGENTS.md`, and `project_doc_fallback_filenames` and concatenating them root-down so subdirectory files override broader guidance.",
    "facets": {
     "discovery_behavior": "Automatic pre-task scan of CODEX_HOME (~/.codex) and Git root-to-CWD directory path",
     "hierarchy_precedence": "Root-to-CWD concatenation (at most one file per directory: AGENTS.override.md > AGENTS.md > fallback names); closer files override earlier ones",
     "fallback_files": "AGENTS.override.md; configurable project_doc_fallback_filenames (e.g., TEAM_GUIDE.md, .agents.md)",
     "verification_posture": "Documented in OpenAI Codex configuration docs and 2025-05-16 launch post"
    },
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20261022165127/https://openai.com/index/introducing-codex/"
   },
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Codex",
    "role": "Plugin host",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Shared plugin directory; root `plugin.json`, `skills/`, `mcp.json`, and `extensions.com.openai`.",
    "full_detail_md": "ChatGPT and Codex share one universal plugin directory. A portable package adds `plugin.json` at the plugin root and can include a `skills/` directory and an `mcp.json` file; OpenAI-specific presentation, MCP server mappings, and hooks go under `extensions.com.openai` in root `plugin.json`, existing `.codex-plugin/plugin.json` files remain a compatibility fallback, and `@plugin-creator` scaffolds that OpenAI path.",
    "facets": {
     "transport_or_manifest": "Root plugin.json; optional skills/ and mcp.json; .codex-plugin/plugin.json fallback",
     "ui_or_widget_surface": "Universal plugin directory shared by ChatGPT and Codex",
     "auth_or_permissions": "No separate auth handshake named in the cited packaging guide",
     "sdk_or_version": "Agent Plugins package with OpenAI extensions.com.openai; @plugin-creator scaffold"
    },
    "telemetry": null,
    "source_url": "https://developers.openai.com/plugins/concepts/plugins"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://learn.chatgpt.com/docs/build-skills",
  "note": "Scans `$CWD/.agents/skills`, `$REPO_ROOT/.agents/skills`, `$HOME/.agents/skills`, and `/etc/codex/skills` for `SKILL.md` (plus optional `agents/openai.yaml`), capping startup metadata via `skills.max_context_tokens`."
 },
 {
  "id": "codex-acp",
  "org_id": "agentclientprotocol",
  "name": "codex-acp",
  "url": "https://github.com/agentclientprotocol/codex-acp",
  "type": "sdk",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "OpenAI Codex (codex-acp)",
    "role": "External ACP adapter (Codex App Server)",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "External `stdio` adapter (`@agentclientprotocol/codex-acp`) translating ACP requests into `Codex App Server` operations.",
    "full_detail_md": "OpenAI Codex integrates with ACP clients through the external `@agentclientprotocol/codex-acp` `stdio` adapter (`ACP adapter for OpenAI's coding assistant` in the ACP Registry), which starts the `Codex App Server`, translates ACP requests into Codex operations, maps Codex events back to the client, and supports native subagent sessions and mid-turn input via the `_session/steering` extension.",
    "facets": {
     "role_in_acp": "External agent bridge / adapter",
     "integration_mode": "External stdio adapter (@agentclientprotocol/codex-acp bridging Codex App Server)",
     "transport": "JSON-RPC 2.0 over stdio",
     "verification_posture": "Adapter repository README & ACP Registry listing (external bridge, not native CLI mode)",
     "sdk_or_package": "@agentclientprotocol/codex-acp"
    },
    "telemetry": null,
    "source_url": "https://github.com/agentclientprotocol/codex-acp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/agentclientprotocol/codex-acp",
  "note": "External `stdio` adapter (`@agentclientprotocol/codex-acp`) translating ACP requests into `Codex App Server` operations."
 },
 {
  "id": "codex-cli-accept",
  "org_id": "openai",
  "name": "Codex CLI",
  "url": "https://acceptmarkdown.com/status",
  "type": "harness",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Codex CLI",
    "role": "Coding agent",
    "status": "Partial",
    "status_display": "Partial · as of 2026-04-18",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-04-18",
    "col4_md": "Partial: follows an alternate `text/markdown` link (verified 2026-04-18).",
    "full_detail_md": "AcceptMarkdown marks Codex CLI as Partial, verified 2026-04-18, and cites RFC 8288 alongside RFC 7763. The matrix contrasts that path with agents that send Accept: text/markdown.",
    "facets": {
     "negotiation_or_artifact": "Follows an alternate text/markdown link rather than sending Accept: text/markdown",
     "response_headers": "Not an Accept: text/markdown sender on this matrix row",
     "content_type_or_tokens": "Partial",
     "verification_posture": "AcceptMarkdown matrix verified 2026-04-18"
    },
    "telemetry": null,
    "source_url": "https://acceptmarkdown.com/status"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://acceptmarkdown.com/status",
  "note": "Partial: follows an alternate `text/markdown` link (verified 2026-04-18)."
 },
 {
  "id": "cofide-wimse-s2s-httpsig-poc",
  "org_id": "cofide",
  "name": "wimse-s2s-httpsig-poc",
  "url": "https://github.com/cofide/wimse-s2s-httpsig-poc",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Cofide",
    "role": "WIT issuer",
    "status": "Experimental",
    "status_display": "Experimental · as of 2025-11-13",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-13",
    "col4_md": "draft-ietf-wimse-http-signature-08 section 4.1 records Cofide's implementation at `cofide/wimse-s2s-httpsig-poc` with maturity proof-of-concept for WIT plus HTTP Message Signatures, Apache 2.0, last updated 13-Nov-2025. The repository is a proof-of-concept demo of WIMSE workload-to-workload authentication with HTTP signatures, based on draft-ietf-wimse-s2s-protocol. It extends minispire, a lightweight SPIFFE implementation, to issue WIMSE Workload Identity Token SVIDs to a demo client and server, as an approximation of the in-development WIT-SVID, without a whole SPIRE setup. Cofide describes the system as a demonstrator and says minispire issues a developmental version of the proposed WIT-SVID credential.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-ietf-wimse-http-signature-08.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ietf.org/archive/id/draft-ietf-wimse-http-signature-08.txt",
  "note": "draft-ietf-wimse-http-signature-08 section 4.1 records Cofide's implementation at `cofide/wimse-s2s-httpsig-poc` with maturity proof-of-concept for WIT plus HTTP Message Signatures, Apache 2.0, last updated 13-Nov-2025. The repository is a proof-of-concept demo of WIMSE workload-to-workload authentication with HTTP signatures, based on draft-ietf-wimse-s2s-protocol. It extends minispire, a lightwe"
 },
 {
  "id": "cognition-devin",
  "org_id": "cognition",
  "name": "Devin",
  "url": "https://docs.devin.ai/onboard-devin/agents-md",
  "type": "harness",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cognition (Devin)",
    "role": "Coding agent",
    "status": "Partial",
    "status_display": "Partial · as of 2026-09-25",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-25",
    "col4_md": "Automatically injects up to 16 KiB (16,384 bytes) per `AGENTS.md` before coding; longer files truncate.",
    "full_detail_md": "Scans the repository for `AGENTS.md` files before coding and automatically injects up to 16 KiB (16,384 bytes) from the beginning of each `AGENTS.md` file into context (`dateModified` 2026-09-25); files exceeding 16 KiB trigger a truncation notice requiring Devin to read the remainder on demand.",
    "facets": {
     "discovery_behavior": "Pre-coding scan of project root and repository directories with 16 KiB (16,384-byte) automatic context injection cap per file",
     "hierarchy_precedence": "Supports root and nested AGENTS.md files; content beyond 16 KiB is truncated with an on-demand read notice",
     "fallback_files": ".devin/rules/",
     "verification_posture": "Documented in Devin onboarding documentation (modified 2026-09-25)"
    },
    "telemetry": null,
    "source_url": "https://docs.devin.ai/onboard-devin/agents-md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.devin.ai/onboard-devin/agents-md",
  "note": "Automatically injects up to 16 KiB (16,384 bytes) per `AGENTS.md` before coding; longer files truncate."
 },
 {
  "id": "coinbase-cdp",
  "org_id": "coinbase",
  "name": "Coinbase CDP Facilitator",
  "url": "https://docs.cdp.coinbase.com/x402/seller/facilitator",
  "type": "venue",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Coinbase CDP Facilitator",
    "role": "Payment rail (Originator)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Hosted `exact`, `upto`, and `batch-settlement` facilitator on `eip155:8453`, `eip155:137`, `eip155:42161`, and Solana with OFAC/KYT screening.",
    "full_detail_md": "Coinbase Developer Platform operates a hosted x402 v2 Facilitator supporting `exact`, `upto`, and `batch-settlement` across Base (`eip155:8453`), Polygon (`eip155:137`), Arbitrum (`eip155:42161`), Monad (`eip155:143`), and World (`eip155:480`) via EIP-3009 or Permit2, plus `exact` and `upto` on Solana (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`), with built-in OFAC/KYT screening and over 100 million transactions ($28M+ volume) processed.",
    "facets": {
     "settlement_rail": "Hosted x402 Facilitator (`exact`, `upto`, `batch-settlement`) via EIP-3009, Permit2, and SPL",
     "supported_assets": "ERC-20 tokens on supported EVM networks and SPL tokens on Solana",
     "chains_or_networks": "Base (`eip155:8453`), Polygon (`eip155:137`), Arbitrum (`eip155:42161`), Monad (`eip155:143`), World (`eip155:480`), Solana (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`)",
     "headers_or_methods": "Facilitator `/verify` and `/settle` REST APIs, `createX402Server`, `HTTPFacilitatorClient`, and Bazaar indexing"
    },
    "telemetry": null,
    "source_url": "https://docs.cdp.coinbase.com/x402/seller/facilitator"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.cdp.coinbase.com/x402/seller/facilitator",
  "note": "Hosted `exact`, `upto`, and `batch-settlement` facilitator on `eip155:8453`, `eip155:137`, `eip155:42161`, and Solana with OFAC/KYT screening."
 },
 {
  "id": "coinbase-cdp-llms-txt",
  "org_id": "coinbase",
  "name": "Coinbase Developer Platform",
  "url": "https://docs.cdp.coinbase.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Coinbase Developer Platform",
    "role": "Developer docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://docs.cdp.coinbase.com/llms.txt` (`# Coinbase Developer Documentation`, `text/plain`), linking `/_llms/` sub-indexes, `.md` recipes, and OpenAPI specs.",
    "full_detail_md": "Serves `https://docs.cdp.coinbase.com/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 60,601 bytes, fetched 2026-11-04) opening `# Coinbase Developer Documentation` and routing agents to partitioned sub-indexes (`/_llms/docs.txt` for 526 pages, `/_llms/api-reference.txt` for 906 pages, `/_llms/sdks.txt` for 1,523 pages), `.md` stablecoin recipes, and OpenAPI specs.",
    "facets": {
     "artifact_path": "https://docs.cdp.coinbase.com/llms.txt",
     "companion_files": "/_llms/docs.txt; /_llms/api-reference.txt; /_llms/sdks.txt; OpenAPI JSON/YAML specs",
     "content_type_or_bytes": "text/plain; charset=utf-8 (60,601 bytes)",
     "generator_or_consumer_mode": "Hierarchical Mintlify index with partitioned /_llms/*.txt sub-indexes"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Coinbase Developer Documentation"
    },
    "source_url": "https://docs.cdp.coinbase.com/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://docs.cdp.coinbase.com/llms.txt",
  "note": "Serves `https://docs.cdp.coinbase.com/llms.txt` (`# Coinbase Developer Documentation`, `text/plain`), linking `/_llms/` sub-indexes, `.md` recipes, and OpenAPI specs."
 },
 {
  "id": "coingecko",
  "org_id": "coingecko",
  "name": "CoinGecko",
  "url": "https://www.coingecko.com",
  "type": "origin",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "CoinGecko",
    "role": "Seller",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-11-06",
    "col4_md": "HTTP 402 `PAYMENT-REQUIRED` (`x402Version` 2, `exact`) accepting USDC across Base, Solana, and Polygon.",
    "full_detail_md": "Probing `https://pro-api.coingecko.com/api/v3/x402/onchain/search/pools?query=weth` returns HTTP 402 with a `PAYMENT-REQUIRED` header (`x402Version: 2`) offering three `exact` options with amount: `5000` atomic USDC units (0.005 USDC per offered option) across Base (`eip155:8453`), Solana (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`), and Polygon (`eip155:137`), alongside `extensions.bazaar` input/output schema metadata.",
    "facets": {
     "settlement_rail": "x402 v2 exact scheme",
     "supported_assets": "USD Coin (USDC, 6 decimals): amount `5000` atomic USDC units (0.005 USDC per offered option) on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), Solana (`EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`), and Polygon (`0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359`)",
     "chains_or_networks": "Base (`eip155:8453`), Solana (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`), Polygon (`eip155:137`)",
     "headers_or_methods": "HTTP 402 `PAYMENT-REQUIRED` header (`x402Version: 2`) with `extensions.bazaar` metadata on `/api/v3/x402/onchain/search/pools`",
     "amount_raw_atomic": "5000",
     "amount_display": "amount: `5000` atomic USDC units (0.005 USDC per offered option)"
    },
    "telemetry": {
     "http_status": 402,
     "transport": "http_header",
     "spec_version": "2",
     "scheme": "exact"
    },
    "source_url": "https://pro-api.coingecko.com/api/v3/x402/onchain/search/pools?query=weth"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pro-api.coingecko.com/api/v3/x402/onchain/search/pools?query=weth",
  "note": "HTTP 402 `PAYMENT-REQUIRED` (`x402Version` 2, `exact`) accepting USDC across Base, Solana, and Polygon."
 },
 {
  "id": "coinmarketcap",
  "org_id": "coinmarketcap",
  "name": "CoinMarketCap",
  "url": "https://coinmarketcap.com",
  "type": "origin",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "CoinMarketCap",
    "role": "Seller",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-11-06",
    "col4_md": "HTTP 402 `PAYMENT-REQUIRED` (`x402Version` 2, `exact`, `eip3009` / `permit2-exact`) on `eip155:8453` (USDC) and `eip155:56` (4 stablecoins).",
    "full_detail_md": "Live HTTP 402 `PAYMENT-REQUIRED` challenge on `eip155:8453` (USD Coin via `eip3009`) and `eip155:56` (USD Coin, Tether USD, World Liberty Financial USD, and United Stables via `permit2-exact`).",
    "facets": {
     "settlement_rail": "x402 v2 exact scheme (`eip3009` and `permit2-exact`)",
     "supported_assets": "USD Coin (`amount: \"10000\"` on Base; `10000000000000000` on BNB Chain), United Stables, World Liberty Financial USD, and Tether USD",
     "chains_or_networks": "Base (`eip155:8453`) and BNB Chain (`eip155:56`)",
     "headers_or_methods": "HTTP 402 `PAYMENT-REQUIRED` header and JSON body (`x402Version: 2`) on `/x402/v3/cryptocurrency/quotes/latest`",
     "amount_raw_atomic": "50000",
     "amount_display": "amount: `50000` atomic units (0.05 USDC / USDT per request)"
    },
    "telemetry": {
     "http_status": 402,
     "transport": "http_header",
     "spec_version": "2",
     "scheme": "exact"
    },
    "source_url": "https://pro-api.coinmarketcap.com/x402/v3/cryptocurrency/quotes/latest?id=1"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pro-api.coinmarketcap.com/x402/v3/cryptocurrency/quotes/latest?id=1",
  "note": "HTTP 402 `PAYMENT-REQUIRED` (`x402Version` 2, `exact`, `eip3009` / `permit2-exact`) on `eip155:8453` (USDC) and `eip155:56` (4 stablecoins)."
 },
 {
  "id": "com-notion-mcp",
  "org_id": "notion",
  "name": "Notion MCP",
  "url": "https://mcp.notion.com",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Notion",
    "role": "MCP authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`https://mcp.notion.com/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://mcp.notion.com`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. Scopes include `ema_issuer:manage`. `client_id_metadata_document_supported` is true.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "issuer": "https://mcp.notion.com",
     "grant_profile": "urn:ietf:params:oauth:grant-profile:id-jag"
    },
    "source_url": "https://mcp.notion.com/.well-known/oauth-authorization-server"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Notion",
    "role": "Server publisher",
    "status": "Listed in Official Registry (HTTP 200 server.json)",
    "status_display": "Listed in Official Registry (HTTP 200 server.json) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-11",
    "col4_md": "`com.notion/mcp` `1.0.1` (published 2025-09-11): remote `streamable-http` and `sse` endpoints.",
    "full_detail_md": "HTTP 200 `application/json`. Latest `com.notion/mcp` is version `1.0.1`, described as the Official Notion MCP server, with registry status `active` and `isLatest` true. The record uses schema `2025-09-29` while `publishedAt` records `2025-09-11T22:25:50.737872Z`. Remotes are `streamable-http` at `https://mcp.notion.com/mcp` and `sse` at `https://mcp.notion.com/sse`.",
    "facets": {
     "registry_or_namespace": "com.notion/mcp",
     "api_or_schema_version": "Record publishedAt 2025-09-11; validates against server.schema.json (2025-09-29).",
     "transport_or_package_types": "streamable-http and sse remotes",
     "verification_posture": "HTTP 200 registry record probe (checked 2026-10-30, publishedAt 2025-09-11); proves registry metadata listing rather than live MCP server execution."
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "server_name": "com.notion/mcp",
     "version": "1.0.1"
    },
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/com.notion%2Fmcp/versions/1.0.1"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mcp.notion.com/.well-known/oauth-authorization-server",
  "note": "`https://mcp.notion.com/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://mcp.notion.com`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. Scopes include `ema_issuer:manage`. `client_id_metadata_document_supported` is true."
 },
 {
  "id": "com-stripe-mcp",
  "org_id": "stripe",
  "name": "Stripe MCP",
  "url": "https://mcp.stripe.com",
  "type": "origin",
  "implements": [
   "mcp-registry",
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Protected resource",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-31",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-31",
    "as_of": "2026-10-31",
    "col4_md": "`resource` `https://mcp.stripe.com`, `scopes_supported` `mcp`, `authorization_servers` `https://access.stripe.com/mcp`.",
    "full_detail_md": "GET https://mcp.stripe.com/.well-known/oauth-protected-resource returned HTTP 200 `application/json` with `access-control-allow-origin` `*`. `resource` is `https://mcp.stripe.com`. `scopes_supported` is `mcp`. `authorization_servers` is `https://access.stripe.com/mcp`. Checked 2026-10-31.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.stripe.com/.well-known/oauth-protected-resource (resource https://mcp.stripe.com; scopes_supported mcp; authorization_servers https://access.stripe.com/mcp)",
     "registration_or_client_id_modes": "Not declared in this protected-resource document; authorization server is https://access.stripe.com/mcp",
     "pkce_or_grant_types": "Not declared in this protected-resource document",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-10-31); access-control-allow-origin *"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-protected-resource",
     "resource": "https://mcp.stripe.com"
    },
    "source_url": "https://mcp.stripe.com/.well-known/oauth-protected-resource"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Server publisher",
    "status": "Listed in Official Registry (HTTP 200 server.json)",
    "status_display": "Listed in Official Registry (HTTP 200 server.json) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-28",
    "col4_md": "`com.stripe/mcp` `0.2.4` (published 2025-10-28): remote `streamable-http` at `https://mcp.stripe.com`.",
    "full_detail_md": "HTTP 200 `application/json`. Latest `com.stripe/mcp` is version `0.2.4` on schema `2025-10-17`, with registry status `active` and `isLatest` true, published `2025-10-28`. The repository is `https://github.com/stripe/agent-toolkit`. The remote is `streamable-http` at `https://mcp.stripe.com`.",
    "facets": {
     "registry_or_namespace": "com.stripe/mcp",
     "api_or_schema_version": "Record publishedAt 2025-10-28; validates against server.schema.json (2025-10-17).",
     "transport_or_package_types": "streamable-http remote at https://mcp.stripe.com",
     "verification_posture": "HTTP 200 registry record probe (checked 2026-10-30, publishedAt 2025-10-28); proves registry metadata listing rather than live MCP server execution."
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "server_name": "com.stripe/mcp",
     "version": "0.2.4"
    },
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/com.stripe%2Fmcp/versions/0.2.4"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://mcp.stripe.com/.well-known/oauth-protected-resource",
  "note": "`resource` `https://mcp.stripe.com`, `scopes_supported` `mcp`, `authorization_servers` `https://access.stripe.com/mcp`."
 },
 {
  "id": "commercetools",
  "org_id": "commercetools",
  "name": "commercetools",
  "url": "https://commercetools.com/press-releases/commercetools-partners-with-stripe-to-launch-acp",
  "type": "venue",
  "implements": [
   "agentic-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "commercetools",
    "role": "Commerce platform",
    "status": "Supported",
    "status_display": "Supported · as of 2025-09-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-30",
    "col4_md": "Joined Stripe and OpenAI as an ACP launch partner for enterprise merchants (announced September 30, 2025).",
    "full_detail_md": "commercetools announced on September 30, 2025 that it joined Stripe and OpenAI as a launch partner of the Agentic Commerce Protocol (ACP).",
    "facets": {
     "commerce_role_or_surface": "Composable commerce platform launch partner",
     "payment_or_token_rail": "ACP partner integration with Stripe and OpenAI",
     "api_or_spec_version": "Agentic Commerce Protocol (ACP)",
     "availability_or_eligibility_posture": "Announced September 30, 2025"
    },
    "telemetry": null,
    "source_url": "https://commercetools.com/press-releases/commercetools-partners-with-stripe-to-launch-acp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://commercetools.com/press-releases/commercetools-partners-with-stripe-to-launch-acp",
  "note": "Joined Stripe and OpenAI as an ACP launch partner for enterprise merchants (announced September 30, 2025)."
 },
 {
  "id": "concise-koopman-me",
  "org_id": "concise-koopman-me",
  "name": "concise.koopman.me",
  "url": "https://transparency.ans.godaddy.com/tile/entries/000",
  "type": "agent",
  "implements": [
   "ans"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "ans",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "concise.koopman.me",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Log tile 0 records agent host concise.koopman.me, name Concise Rewrite, version v1.0.0. Badge `_ra-badge.concise.koopman.me` is `v=ra-badge1; url=https://transparency.ans.godaddy.com/v1/agents/cb0f6ca3-b9a9-408f-8e0b-8605fa438773`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://transparency.ans.godaddy.com/tile/entries/000"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://transparency.ans.godaddy.com/tile/entries/000",
  "note": "Log tile 0 records agent host concise.koopman.me, name Concise Rewrite, version v1.0.0. Badge `_ra-badge.concise.koopman.me` is `v=ra-badge1; url=https://transparency.ans.godaddy.com/v1/agents/cb0f6ca3-b9a9-408f-8e0b-8605fa438773`."
 },
 {
  "id": "copilot-chat-accept",
  "org_id": "github",
  "name": "Copilot Chat (VS Code)",
  "url": "https://acceptmarkdown.com/status",
  "type": "harness",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Copilot Chat (VS Code)",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-06-22",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-22",
    "col4_md": "Sends q-valued `Accept: text/markdown` (verified 2026-06-22).",
    "full_detail_md": "AcceptMarkdown's client matrix, last updated 2026-06-22, records Copilot Chat (VS Code) as sending an Accept header that includes text/markdown. Verified date on that row is 2026-06-22.",
    "facets": {
     "negotiation_or_artifact": "Accept header includes text/markdown",
     "response_headers": "Accept: text/markdown, text/html;q=0.9, application/xhtml+xml;q=0.9, application/xml;q=0.8, */*;q=0.7",
     "content_type_or_tokens": "Requests text/markdown",
     "verification_posture": "AcceptMarkdown matrix verified 2026-06-22; matrix last updated 2026-06-22"
    },
    "telemetry": null,
    "source_url": "https://acceptmarkdown.com/status"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://acceptmarkdown.com/status",
  "note": "Sends q-valued `Accept: text/markdown` (verified 2026-06-22)."
 },
 {
  "id": "copilot-cli-accept",
  "org_id": "github",
  "name": "Copilot CLI",
  "url": "https://acceptmarkdown.com/status",
  "type": "harness",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Copilot CLI",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-06-22",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-22",
    "col4_md": "Sends `Accept: text/markdown, text/html, */*` (verified 2026-06-22).",
    "full_detail_md": "AcceptMarkdown's client matrix, last updated 2026-06-22, records Copilot CLI as sending an Accept header that includes text/markdown. Verified date on that row is 2026-06-22.",
    "facets": {
     "negotiation_or_artifact": "Accept header includes text/markdown",
     "response_headers": "Accept: text/markdown, text/html, */*",
     "content_type_or_tokens": "Requests text/markdown",
     "verification_posture": "AcceptMarkdown matrix verified 2026-06-22; matrix last updated 2026-06-22"
    },
    "telemetry": null,
    "source_url": "https://acceptmarkdown.com/status"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://acceptmarkdown.com/status",
  "note": "Sends `Accept: text/markdown, text/html, */*` (verified 2026-06-22)."
 },
 {
  "id": "copilotkit",
  "org_id": "copilotkit",
  "name": "CopilotKit",
  "url": "https://docs.copilotkit.ai/generative-ui/a2ui",
  "type": "harness",
  "implements": [
   "a2ui",
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "CopilotKit",
    "role": "Chat renderer",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-15",
    "col4_md": "Day-zero A2UI via AG-UI; docs apply `A2UIMiddleware` and name `@copilotkit/react-core/v2`.",
    "full_detail_md": "The December 15, 2025 introduction says AG-UI fully supports the A2UI spec and that CopilotKit provides day-0 compatibility between AG-UI and A2UI, and the ecosystem page extends that day-zero compatibility to React, Vue, and Angular surfaces through CopilotKit. The CopilotKit docs apply A2UIMiddleware to registered agents and name @copilotkit/react-core/v2 as the browser half, and the Cloud guide says CopilotKit owns the chat shell with an A2UI renderer registered inside it for rich cards.",
    "facets": {
     "transport_or_binding": "AG-UI, with day-0 / day-zero A2UI compatibility",
     "component_or_catalog": "A2UI renderer registered in the CopilotKit chat shell for rich cards",
     "spec_version": "Day-0 announcement 2025-12-15; current docs describe A2UIMiddleware",
     "sdk_or_renderer": "A2UIMiddleware server-side; @copilotkit/react-core/v2 in the browser; React, Vue, and Angular"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/introducing-a2ui-an-open-project-for-agent-driven-interfaces/"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "CopilotKit",
    "role": "Frontend client",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Client quickstart names CopilotKit for production; the overview lists it as 1st Party.",
    "full_detail_md": "The client quickstart says that for production use, a full-featured client like CopilotKit should be used. The overview lists CopilotKit as Supported, with Getting Started, and marks it 1st Party.",
    "facets": {
     "transport": "Not stated on the client quickstart row",
     "event_or_state_model": "User-facing AG-UI client (event rendering not further specified)",
     "integration_role": "1st-party production frontend client",
     "sdk_or_package": "CopilotKit (package name not in the cited lines)"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/quickstart/clients"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.googleblog.com/introducing-a2ui-an-open-project-for-agent-driven-interfaces/",
  "note": "Day-zero A2UI via AG-UI; docs apply `A2UIMiddleware` and name `@copilotkit/react-core/v2`."
 },
 {
  "id": "coronet-arcade",
  "org_id": "lueva-labs",
  "name": "Coronet Arcade",
  "url": "https://coronet.one/mcp",
  "type": "origin",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Coronet Arcade",
    "role": "MCP App server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`https://coronet.one/mcp` returned HTTP 200 and JSON-RPC `-32000` (`text/event-stream`).",
    "full_detail_md": "Coronet Arcade publishes https://coronet.one/mcp and says playable boards require MCP Apps support, and that adding the server does not confirm the client can display a board. The endpoint returned HTTP 200 with JSON-RPC error -32000 saying the client must accept text/event-stream, which is an Accept error rather than a rendered board or a registry record.",
    "facets": {
     "transport_or_channel": "MCP URL https://coronet.one/mcp; HTTP 200 JSON-RPC -32000 requires Accept text/event-stream",
     "ui_resource_or_primitive": "Playable boards that require an MCP Apps host; the GET body is not the board UI",
     "sandbox_or_security": "Connect page does not publish a CSP; display depends on the client's MCP Apps support",
     "sdk_or_version": "Published connector named Coronet Arcade; HTTP probe checked 2026-10-30"
    },
    "telemetry": {
     "http_status": 200,
     "jsonrpc_error_code": -32000,
     "accept_hint": "text/event-stream"
    },
    "source_url": "https://coronet.one/connect/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://coronet.one/connect/",
  "note": "`https://coronet.one/mcp` returned HTTP 200 and JSON-RPC `-32000` (`text/event-stream`)."
 },
 {
  "id": "coursera",
  "org_id": "coursera",
  "name": "Coursera",
  "url": "https://www.coursera.org",
  "type": "origin",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Coursera",
    "role": "ChatGPT app",
    "status": "Listed",
    "status_display": "Listed · as of 2025-10-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-06",
    "col4_md": "Named with Booking.com, Canva, Expedia, Figma, Spotify, and Zillow in the launch set.",
    "full_detail_md": "The Verge lists Coursera among the apps available inside ChatGPT at launch, with Booking.com, Canva, Expedia, Figma, Spotify, and Zillow. TechCrunch includes Coursera in the same company list and notes the Apps SDK preview.",
    "facets": {
     "transport_or_manifest": "No manifest file cited; named only in launch coverage",
     "ui_or_widget_surface": "Application available inside ChatGPT at launch",
     "auth_or_permissions": "No permission model named in the cited launch coverage",
     "sdk_or_version": "Apps SDK preview period (launch coverage dated 2025-10-06)"
    },
    "telemetry": null,
    "source_url": "https://www.theverge.com/news/793039/openai-chatgpt-apps-developers-sdk-canva-zillow-devday-2025"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.theverge.com/news/793039/openai-chatgpt-apps-developers-sdk-canva-zillow-devday-2025",
  "note": "Named with Booking.com, Canva, Expedia, Figma, Spotify, and Zillow in the launch set."
 },
 {
  "id": "crewai",
  "org_id": "crewai",
  "name": "CrewAI",
  "url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "type": "sdk",
  "implements": [
   "a2a",
   "ag-ui",
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry",
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "CrewAI",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-27",
    "col4_md": "AAIF proposal lists `CrewAI AMP` production hosting across `REST`/`JSON-RPC`/`gRPC` transports with `OIDC`, `OAuth2`, and `mTLS`.",
    "full_detail_md": "The A2A project blog (2026-08-27) names CrewAI among supporting frameworks, and the AAIF Growth Stage proposal (#37) states that the `CrewAI AMP` platform provides A2A hosting via `A2AServerConfig` with distributed state, `OIDC`, `OAuth2`, and `mTLS` authentication, `REST`/`JSON-RPC`/`gRPC` transports, and signed webhook push notifications.",
    "facets": {
     "transport_bindings": "REST, JSON-RPC, and gRPC transports with signed webhook push notifications (reported in AAIF proposal)",
     "discovery_artifact": "CrewAI AMP hosted A2A server configuration (A2AServerConfig)",
     "protocol_version": "Not specified in AAIF proposal (2026-08-27 blog / proposal #37)",
     "auth_schemes": "OIDC, OAuth2, and mTLS (reported in AAIF proposal)",
     "verification_posture": "Listed in A2A blog (2026-08-27) and AAIF proposal #37"
    },
    "telemetry": null,
    "source_url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "CrewAI",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`ag-ui-crewai` exposes a Crew or Flow over FastAPI for CopilotKit React hooks.",
    "full_detail_md": "The `ag-ui-crewai` package exposes any Crew or Flow as an AG-UI endpoint, and CopilotKit's React hooks and components consume that endpoint. The documented server is a Python process that serves the Crew or Flow over AG-UI with FastAPI and `ag-ui-crewai`, and the overview lists CrewAI as Supported under Agent Framework - Partnerships.",
    "facets": {
     "transport": "AG-UI endpoint served by a Python FastAPI process",
     "event_or_state_model": "AG-UI event endpoint for a Crew or Flow",
     "integration_role": "Partnership agent framework",
     "sdk_or_package": "ag-ui-crewai, consumed by CopilotKit React hooks"
    },
    "telemetry": null,
    "source_url": "https://docs.crewai.com/edge/en/guides/frontend/overview"
   },
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "CrewAI",
    "role": "Agent framework (baked-in instrumentation)",
    "status": "Supported",
    "status_display": "Supported · as of 2025-03-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2025-03-06",
    "col4_md": "The `2025-03-06` OpenTelemetry blog post states that some AI agent frameworks, such as CrewAI, provide built-in instrumentation that emits telemetry using OpenTelemetry semantic conventions.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://opentelemetry.io/blog/2025/ai-agent-observability/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "note": "AAIF proposal lists `CrewAI AMP` production hosting across `REST`/`JSON-RPC`/`gRPC` transports with `OIDC`, `OAuth2`, and `mTLS`."
 },
 {
  "id": "crosswalk",
  "org_id": "crosswalk",
  "name": "crosswalk",
  "url": "https://crosswalk.to/.well-known/poppy.json",
  "type": "origin",
  "implements": [
   "personal-agent-protocol"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "personal-agent-protocol",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "crosswalk",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "https://crosswalk.to/.well-known/poppy.json, seen 2026-10-29, is protocol_version 0.2 with organization.name crosswalk and organization.domain crosswalk.to. The 0.2 file lists scopes poppy:read and poppy:write.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json"
    },
    "source_url": "https://crosswalk.to/.well-known/poppy.json"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://crosswalk.to/.well-known/poppy.json",
  "note": "https://crosswalk.to/.well-known/poppy.json, seen 2026-10-29, is protocol_version 0.2 with organization.name crosswalk and organization.domain crosswalk.to. The 0.2 file lists scopes poppy:read and poppy:write."
 },
 {
  "id": "cube",
  "org_id": "cube",
  "name": "Cube",
  "url": "https://docs.cube.dev/docs/integrations/apache-ossie",
  "type": "origin",
  "implements": [
   "osi"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "osi",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cube",
    "role": "Data platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Cube converts a data model to Apache Ossie YAML and back. Docs checked 2026-10-29 say the conversion is in preview. Announced 2026-10-15.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.cube.dev/docs/integrations/apache-ossie"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.cube.dev/docs/integrations/apache-ossie",
  "note": "Cube converts a data model to Apache Ossie YAML and back. Docs checked 2026-10-29 say the conversion is in preview. Announced 2026-10-15."
 },
 {
  "id": "curity-cimd",
  "org_id": "curity",
  "name": "Curity Identity Server",
  "url": "https://curity.io",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Curity",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-02",
    "col4_md": "Admin UI ephemeral clients; one client ID reused across servers (2026-03-02).",
    "full_detail_md": "Curity Identity Server documents Client ID metadata documents in the Admin UI. The 2026-03-02 article points to the Ephemeral Clients tutorial for the configuration steps, so a client can reuse one client ID across authorization servers.",
    "facets": {
     "metadata_flag_or_profile": "Admin UI configuration of Client ID metadata documents, described as ephemeral clients",
     "auth_method_or_pkce": "Not named in the article; the point of the pattern is reusing one client ID across authorization servers",
     "uri_or_ssrf_rules": "Not specified in the article",
     "draft_or_spec_version": "Article published 2026-03-02; it does not name a CIMD draft revision number"
    },
    "telemetry": null,
    "source_url": "https://curity.io/resources/learn/oauth-client-id-metadata-document/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://curity.io/resources/learn/oauth-client-id-metadata-document/",
  "note": "Admin UI ephemeral clients; one client ID reused across servers (2026-03-02)."
 },
 {
  "id": "curl",
  "org_id": "curl",
  "name": "curl",
  "url": "https://curl.se/",
  "type": "sdk",
  "implements": [
   "http-message-signatures"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "curl",
    "role": "HTTP client signer (general RFC 9421)",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-09-02",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-03",
    "as_of": "2026-09-02",
    "col4_md": "Experimental RFC 9421 request signing in v8.22.0+ via `--httpsig-algo` (`ed25519` default and `hmac-sha256`).",
    "full_detail_md": "Added experimental general-purpose RFC 9421 HTTP Message Signatures support in curl 8.22.0 (released September 2, 2026) via `--httpsig-algo`, `--httpsig-key`, `--httpsig-keyid`, and `--httpsig-headers`, defaulting to covering method, authority, path, and query with `ed25519` (default) or `hmac-sha256`.",
    "facets": {
     "profile_or_spec_target": "RFC 9421 general-purpose client signing (experimental in curl 8.22.0+)",
     "signature_fields": "Covers method, authority, path, and query by default (`--httpsig-headers`, `--httpsig-keyid`)",
     "algorithms_or_keys": "`ed25519` (default) and `hmac-sha256` (`--httpsig-algo`, `--httpsig-key`)",
     "verification_posture": "HTTP client signer (outbound request signing in curl CLI and libcurl)"
    },
    "telemetry": null,
    "source_url": "https://daniel.haxx.se/blog/2026/07/27/http-message-signatures-with-curl/"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://daniel.haxx.se/blog/2026/07/27/http-message-signatures-with-curl/",
  "note": "Experimental RFC 9421 request signing in v8.22.0+ via `--httpsig-algo` (`ed25519` default and `hmac-sha256`)."
 },
 {
  "id": "cursor",
  "org_id": "cursor",
  "name": "Cursor",
  "url": "https://cursor.com",
  "type": "harness",
  "implements": [
   "agents-md",
   "anthropic-agent-skills-format",
   "cloudflare-markdown-for-agents",
   "mcp",
   "mcp-apps",
   "oauth-cimd"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Cursor",
    "role": "IDE host",
    "status": "Supported",
    "status_display": "Supported · as of 2025-06-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-06-04",
    "col4_md": "Supports one-click MCP server installation and OAuth authentication in Cursor `1.0`.",
    "full_detail_md": "Cursor `1.0` (`2025-06-04`) provides one-click MCP server installation via deep links and OAuth authentication for remote MCP servers.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1",
     "primitives": "tools, resources, prompts",
     "sdk_or_package": "Cursor 1.0+"
    },
    "telemetry": null,
    "source_url": "https://cursor.com/changelog/1-0"
   },
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Cursor",
    "role": "IDE and CLI coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-22",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-22",
    "col4_md": "Discovers `SKILL.md` in `.agents/skills/`, `.cursor/skills/`, `~/.claude/skills/`, and `~/.codex/skills/` across editor and CLI since Cursor `2.4`.",
    "full_detail_md": "Introduced in Cursor `2.4` (`2026-01-22`), Cursor discovers `SKILL.md` folders (with optional `scripts/`, `references/`, and `assets/`) from `.agents/skills/`, `.cursor/skills/`, `~/.agents/skills/`, `~/.cursor/skills/`, and compatibility paths (`.claude/skills/`, `.codex/skills/`, `~/.claude/skills/`, `~/.codex/skills/`) for automatic or `/` slash-command invocation, while noting that unsynced local user skills are not copied to cloud agents, remote SSH sessions, or self-hosted workers.",
    "facets": {
     "transport_or_packaging": "Local project and user directories (.agents/skills/, .cursor/skills/, plus Claude and Codex compatibility paths)",
     "manifest_or_entry": "SKILL.md in flat or nested category subdirectories plus optional scripts/, references/, and assets/",
     "execution_or_sandbox": "Editor and CLI agent tool execution; unsynced ~/.agents/skills/ are not copied to cloud agents or remote SSH",
     "verification_posture": "First-party Cursor 2.4 changelog (2026-01-22) and product documentation checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://cursor.com/changelog/2-4"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cursor",
    "role": "IDE / Coding agent",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Loads plain-Markdown `AGENTS.md` in root and subdirectories, combining parent files with subdirectory precedence.",
    "full_detail_md": "Supports plain-Markdown `AGENTS.md` files in the project root and nested subdirectories as a metadata-free alternative to `.cursor/rules` (`.mdc` files); nested `AGENTS.md` files are automatically applied when working in their subtree and combined with parent directory instructions so more specific instructions take precedence.",
    "facets": {
     "discovery_behavior": "Automatic prompt-level context loading from project root and nested subdirectories",
     "hierarchy_precedence": "Nested subdirectory AGENTS.md files combine with parent directories; more specific instructions take precedence",
     "fallback_files": ".cursor/rules/*.mdc; User Rules; Team Rules (deprecated .cursorrules)",
     "verification_posture": "Documented in Cursor Rules official documentation"
    },
    "telemetry": null,
    "source_url": "https://cursor.com/docs/rules"
   },
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Cursor",
    "role": "IDE",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-03",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-03",
    "col4_md": "Changelog 2.6 (2026-03-03) shows MCP Apps charts, diagrams, and whiteboards in Cursor.",
    "full_detail_md": "Cursor changelog 2.6, dated 2026-03-03, says MCP Apps support interactive user interfaces inside Cursor, including charts from Amplitude, diagrams from Figma, and whiteboards from tldraw. The changelog is a release note, not a live HTTP probe of an MCP endpoint and not a registry JSON record.",
    "facets": {
     "transport_or_channel": "MCP Apps render inside Cursor; the changelog does not name a separate wire transport",
     "ui_resource_or_primitive": "Interactive UI such as Amplitude charts, Figma diagrams, and tldraw whiteboards",
     "sandbox_or_security": "Changelog does not restate CSP or iframe sandbox flags",
     "sdk_or_version": "Cursor changelog 2.6 dated 2026-03-03"
    },
    "telemetry": null,
    "source_url": "https://cursor.com/changelog/2-6"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Cursor",
    "role": "OAuth client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `none` auth; `grant_types` are `authorization_code` and `refresh_token`.",
    "full_detail_md": "`https://cursor.com/oauth/mcp-client.json` returned HTTP 200 `application/json`, with `client_id` equal to that URL, `client_name` Cursor, and `token_endpoint_auth_method` `none`. `grant_types` are `authorization_code` and `refresh_token`, and `redirect_uris` include `https://www.cursor.com/agents/mcp/oauth/callback`, `https://www.cursor.com/bot/mcp/oauth/callback`, `https://grok.com/connectors-oauth-exchange-code/`, and loopback callbacks on port 8787. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "Published client metadata JSON; client_name Cursor; client_id equals https://cursor.com/oauth/mcp-client.json",
     "auth_method_or_pkce": "token_endpoint_auth_method none; grant_types authorization_code and refresh_token; no code_challenge_methods_supported field in this document",
     "uri_or_ssrf_rules": "redirect_uris include Cursor agent and bot callbacks, https://grok.com/connectors-oauth-exchange-code/, and http://127.0.0.1:8787/callback plus http://localhost:8787/callback",
     "draft_or_spec_version": "Live client metadata JSON checked 2026-10-30; the document does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_name": "Cursor",
     "token_endpoint_auth_method": "none"
    },
    "source_url": "https://cursor.com/oauth/mcp-client.json"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Cursor",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-02-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02-19",
    "col4_md": "Cursor `2.4.28` `WebFetch` sends `Accept: text/markdown,text/html;q=0.9,application/xhtml+xml;q=0.8,application/xml;q=0.7,image/webp;q=0.6,*/*;q=0.5`.",
    "full_detail_md": "Checkly recorded Cursor 2.4.28 WebFetch requesting Markdown with `Accept: text/markdown,text/html;q=0.9,application/xhtml+xml;q=0.8,application/xml;q=0.7,image/webp;q=0.6,*/*;q=0.5`, so the q factors rank Markdown above HTML.",
    "facets": {
     "negotiation_or_artifact": "WebFetch in Cursor 2.4.28 requests Markdown using q-weighted Accept",
     "response_headers": "Accept: text/markdown,text/html;q=0.9,application/xhtml+xml;q=0.8,application/xml;q=0.7,image/webp;q=0.6,*/*;q=0.5",
     "content_type_or_tokens": "text/markdown is first (implicit q=1) ahead of text/html;q=0.9",
     "verification_posture": "Checkly header capture published 2026-02-19"
    },
    "telemetry": null,
    "source_url": "https://www.checklyhq.com/blog/state-of-ai-agent-content-negotation/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://cursor.com/changelog/1-0",
  "note": "Supports one-click MCP server installation and OAuth authentication in Cursor `1.0`."
 },
 {
  "id": "cursor-com-llms-txt",
  "org_id": "cursor",
  "name": "Cursor Documentation",
  "url": "https://cursor.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cursor",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://cursor.com/llms.txt` as `text/plain` (`# Cursor Documentation`) with a `Link` header (`</llms.txt>; rel=\"describedby\"; type=\"text/plain\"; title=\"llms.txt\"`).",
    "full_detail_md": "Serves `https://cursor.com/llms.txt` as `text/plain; charset=utf-8` (28,202 bytes, fetched 2026-11-04) with an HTTP `Link: </llms.txt>; rel=\"describedby\"; type=\"text/plain\"; title=\"llms.txt\", </docs/sitemap.xml>; rel=\"sitemap\"; type=\"application/xml\"` response header. The file opens `# Cursor Documentation` and indexes `.md` documentation pages under `https://cursor.com/docs/`.",
    "facets": {
     "artifact_path": "https://cursor.com/llms.txt",
     "companion_files": ".md page twins under https://cursor.com/docs/*.md; HTTP Link rel=\"describedby\" header",
     "content_type_or_bytes": "text/plain; charset=utf-8 (28,202 bytes)",
     "generator_or_consumer_mode": "Origin documentation index with HTTP Link rel=\"describedby\" discovery"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# Cursor Documentation",
     "link": "</llms.txt>; rel=\"describedby\"; type=\"text/plain\"; title=\"llms.txt\""
    },
    "source_url": "https://cursor.com/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://cursor.com/llms.txt",
  "note": "Serves `https://cursor.com/llms.txt` as `text/plain` (`# Cursor Documentation`) with a `Link` header (`</llms.txt>; rel=\"describedby\"; type=\"text/plain\"; title=\"llms.txt\"`)."
 },
 {
  "id": "cursor-docs-markdown",
  "org_id": "cursor",
  "name": "Cursor (Docs)",
  "url": "https://cursor.com/docs",
  "type": "origin",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Cursor (Docs)",
    "role": "Developer documentation (cursor.com/docs)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`HTTP 200` `content-type: text/markdown; charset=utf-8`, `vary: Accept`, `link: </llms.txt>; rel=\"describedby\"`.",
    "full_detail_md": "Live probe of Cursor Docs returned `HTTP 200` with `content-type: text/markdown; charset=utf-8`, `vary: Accept`, and `link: </llms.txt>; rel=\"describedby\"`. The body opens `# Cursor Documentation`.",
    "facets": {
     "negotiation_or_artifact": "Live Markdown response at https://cursor.com/docs, linked to /llms.txt",
     "response_headers": "HTTP 200; vary: Accept; link: </llms.txt>; rel=\"describedby\"",
     "content_type_or_tokens": "text/markdown; charset=utf-8; body heading # Cursor Documentation",
     "verification_posture": "Live HTTP probe checked 2026-11-04"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "vary": "Accept"
    },
    "source_url": "https://cursor.com/docs"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://cursor.com/docs",
  "note": "`HTTP 200` `content-type: text/markdown; charset=utf-8`, `vary: Accept`, `link: </llms.txt>; rel=\"describedby\"`."
 },
 {
  "id": "cybersecai-aat-mcp",
  "org_id": "cybersecai-aat-mcp",
  "name": "CyberSecAI aat-mcp",
  "url": "https://raw.githubusercontent.com/razashariff/aat-mcp/main/README.md",
  "type": "sdk",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "CyberSecAI aat-mcp",
    "role": "Audit emitter",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-29",
    "col4_md": "PyPI `aat-mcp` `0.1.0`, uploaded 2026-09-29 by cybersecai. MCP middleware that records each tool invocation as a signed, hash-chained AAT record conformant to `draft-sharif-agent-audit-trail-06` (`principal` became mandatory in `-07`, after `aat-mcp` `0.1.0`'s stated `-06` target). Coverage named in the draft's implementation section: record format (Section 3), hash chaining (Section 6), and ES256 signatures, with offline independent verification.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/razashariff/aat-mcp/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/razashariff/aat-mcp/main/README.md",
  "note": "PyPI `aat-mcp` `0.1.0`, uploaded 2026-09-29 by cybersecai. MCP middleware that records each tool invocation as a signed, hash-chained AAT record conformant to `draft-sharif-agent-audit-trail-06` (`principal` became mandatory in `-07`, after `aat-mcp` `0.1.0`'s stated `-06` target). Coverage named in the draft's implementation section: record format (Section 3), hash chaining (Section 6), and ES256"
 },
 {
  "id": "cybersecai-aat-verify",
  "org_id": "cybersecai-aat-verify",
  "name": "CyberSecAI aat-verify",
  "url": "https://pypi.org/pypi/aat-verify/json",
  "type": "authority",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "CyberSecAI aat-verify",
    "role": "Verifier / Audit parser",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-15",
    "col4_md": "PyPI aat-verify 0.1.0, uploaded 2026-09-15 by cybersecai. Standalone reference verifier for draft-sharif-agent-audit-trail. The draft chains records with SHA-256 over RFC 8785 canonical JSON and requires agent identity, the authorizing principal, action classification, outcome, and trust level. ECDSA signatures are optional. aat-mcp's own text also says it can verify a chain offline against a public key.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/aat-verify/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/aat-verify/json",
  "note": "PyPI aat-verify 0.1.0, uploaded 2026-09-15 by cybersecai. Standalone reference verifier for draft-sharif-agent-audit-trail. The draft chains records with SHA-256 over RFC 8785 canonical JSON and requires agent identity, the authorizing principal, action classification, outcome, and trust level. ECDSA signatures are optional. aat-mcp's own text also says it can verify a chain offline against a publ"
 },
 {
  "id": "databricks-model-serving",
  "org_id": "databricks",
  "name": "Databricks Model Serving",
  "url": "https://docs.databricks.com/aws/en/machine-learning/model-serving/query-open-responses-models",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Databricks Model Serving",
    "role": "Inference API",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-02",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-02",
    "col4_md": "Stateless `/serving-endpoints/open-responses`; `previous_response_id` unsupported (updated October 2, 2026). Ankit Mathur (Databricks) is an initial TSC voting member.",
    "full_detail_md": "Databricks says the Open Responses API uses an input field instead of messages and returns a structured output array, with requests sent to /serving-endpoints/open-responses; conversations are stateless and previous_response_id is not supported, while stream true returns text/event-stream. The page was last updated on Oct 2, 2026, and The New Stack says Databricks Model Serving already implements the spec. Ankit Mathur (Databricks) is an initial TSC voting member.",
    "facets": {
     "endpoint_or_route": "/serving-endpoints/open-responses",
     "streaming_or_items": "stream true returns text/event-stream; otherwise a response object with an output array",
     "tool_or_state_model": "stateless; previous_response_id and server-side conversation storage are not supported; input field instead of messages",
     "sdk_or_version": "Documentation last updated Oct 2, 2026"
    },
    "telemetry": null,
    "source_url": "https://docs.databricks.com/aws/en/machine-learning/model-serving/query-open-responses-models"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.databricks.com/aws/en/machine-learning/model-serving/query-open-responses-models",
  "note": "Stateless `/serving-endpoints/open-responses`; `previous_response_id` unsupported (updated October 2, 2026). Ankit Mathur (Databricks) is an initial TSC voting member."
 },
 {
  "id": "datadiligence",
  "org_id": "spawning",
  "name": "Data Diligence",
  "url": "https://datadiligence.readthedocs.io/en/latest/api/datadiligence.rules.html",
  "type": "sdk",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Spawning (Data Diligence)",
    "role": "Opt-out library",
    "status": "Partial",
    "status_display": "Partial · as of 2023-07-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2023-07-11",
    "col4_md": "Rules reference for datadiligence 0.1.7.post1.dev1+gea09739. `TDMRepHeader` sets `HEADER_NAME` to `tdm-reservation`, and `is_allowed` checks whether the tdm-rep header allows access to the resource without a policy. `HttpEvaluator` accepts `respect_tdmrep=True`. `PostprocessEvaluator` loads `TDMRepHeader` by default. Spawning's 2023-07-11 comment says `datadiligence` supports the proposed TDMRep HTTP headers and does not directly support `tdmrep.json` yet; the Spawning API does.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://datadiligence.readthedocs.io/en/latest/api/datadiligence.rules.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://datadiligence.readthedocs.io/en/latest/api/datadiligence.rules.html",
  "note": "Rules reference for datadiligence 0.1.7.post1.dev1+gea09739. `TDMRepHeader` sets `HEADER_NAME` to `tdm-reservation`, and `is_allowed` checks whether the tdm-rep header allows access to the resource without a policy. `HttpEvaluator` accepts `respect_tdmrep=True`. `PostprocessEvaluator` loads `TDMRepHeader` by default. Spawning's 2023-07-11 comment says `datadiligence` supports the proposed TDMRep H"
 },
 {
  "id": "datadog-llm-observability",
  "org_id": "datadog",
  "name": "Datadog LLM Observability",
  "url": "https://docs.datadoghq.com/llm_observability/instrumentation/otel_instrumentation/",
  "type": "origin",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Datadog LLM Observability",
    "role": "Agent observability backend",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Datadog's OpenTelemetry LLM Observability documentation (`docs.datadoghq.com/llm_observability/instrumentation/otel_instrumentation/`, HTTP 200, `dateModified` 2026-11-04, canonical `/llm_observability/instrument/`) states that users can instrument LLM applications with OpenTelemetry using GenAI or OpenInference semantic conventions and send traces to Agent Observability without the Datadog SDK.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.datadoghq.com/llm_observability/instrumentation/otel_instrumentation/"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://docs.datadoghq.com/llm_observability/instrumentation/otel_instrumentation/",
  "note": "Datadog's OpenTelemetry LLM Observability documentation (`docs.datadoghq.com/llm_observability/instrumentation/otel_instrumentation/`, HTTP 200, `dateModified` 2026-11-04, canonical `/llm_observability/instrument/`) states that users can instrument LLM applications with OpenTelemetry using GenAI or OpenInference semantic conventions and send traces to Agent Observability without the Datadog SDK."
 },
 {
  "id": "datalayer-personal-agent-protocol-sdk",
  "org_id": "datalayer-personal-agent-protocol-sdk",
  "name": "Datalayer personal-agent-protocol SDK",
  "url": "https://pypi.org/pypi/personal-agent-protocol/json",
  "type": "sdk",
  "implements": [
   "personal-agent-protocol"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "personal-agent-protocol",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Datalayer personal-agent-protocol SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-27",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "PyPI personal-agent-protocol 0.27.0, uploaded 2026-10-27, owned by Datalayer. The summary says it is a Python SDK for Personal Agent Protocol draft 0.3 (2026-10) and Operations extension v1. The discovery file that draft uses is /.well-known/poppy.json with protocol_version and organization.name.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/personal-agent-protocol/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/personal-agent-protocol/json",
  "note": "PyPI personal-agent-protocol 0.27.0, uploaded 2026-10-27, owned by Datalayer. The summary says it is a Python SDK for Personal Agent Protocol draft 0.3 (2026-10) and Operations extension v1. The discovery file that draft uses is /.well-known/poppy.json with protocol_version and organization.name."
 },
 {
  "id": "dbt",
  "org_id": "dbt",
  "name": "dbt",
  "url": "https://docs.getdbt.com/docs/build/ossie-semantic-models",
  "type": "origin",
  "implements": [
   "osi"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "osi",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "dbt",
    "role": "Data platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-25",
    "col4_md": "dbt v1.12 defines semantic models and metrics in Apache Ossie YAML. Documents must use version 0.1.0 or 0.1.1. Docs page last updated 2026-09-25 and returned status 200 on 2026-10.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.getdbt.com/docs/build/ossie-semantic-models"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.getdbt.com/docs/build/ossie-semantic-models",
  "note": "dbt v1.12 defines semantic models and metrics in Apache Ossie YAML. Documents must use version 0.1.0 or 0.1.1. Docs page last updated 2026-09-25 and returned status 200 on 2026-10."
 },
 {
  "id": "defakto-security",
  "org_id": "defakto",
  "name": "Defakto Security",
  "url": "https://defakto.security",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Defakto Security",
    "role": "Workload credential issuer",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "draft-ietf-wimse-workload-creds-03 (dated 30 October 2026) records Defakto Security (prior SPIRL) with Workload Identity Certificate maturity production and Workload Identity Token maturity alpha. The coverage line lists the Workload Identity Certificate and WIT.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-ietf-wimse-workload-creds-03.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ietf.org/archive/id/draft-ietf-wimse-workload-creds-03.txt",
  "note": "draft-ietf-wimse-workload-creds-03 (dated 30 October 2026) records Defakto Security (prior SPIRL) with Workload Identity Certificate maturity production and Workload Identity Token maturity alpha. The coverage line lists the Workload Identity Certificate and WIT."
 },
 {
  "id": "deutsche-telekom-frag-magenta",
  "org_id": "deutsche-telekom-frag-magenta",
  "name": "Deutsche Telekom, Frag Magenta",
  "url": "https://newsroom.eclipse.org/news/announcements/eclipse-lmos-redefines-agentic-ai-industry%E2%80%99s-first-open-agent-definition",
  "type": "agent",
  "implements": [
   "lmos"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "lmos",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Deutsche Telekom, Frag Magenta",
    "role": "Agent runtime / Server",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-28",
    "col4_md": "Eclipse (2025-10-28 and 2025-11) says Frag Magenta OneBOT runs on the LMOS platform and has handled millions of customer service and sales interactions across countries. The project blog (2025-03-06) says the platform has been operational since 2023 through deployed ARC agents for contract, billing, and technical support. On the W3C WebAgents list the same day, Robert Winkler wrote that Deutsche Telekom's Agent/Tool Description Format and capability model, based on Web of Things, is already running at scale. Deutsche Telekom's own 2026-10-05 release counts about 2.6 million Frag Magenta calls in the first half of 2026 and does not name LMOS.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://newsroom.eclipse.org/news/announcements/eclipse-lmos-redefines-agentic-ai-industry%E2%80%99s-first-open-agent-definition"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://newsroom.eclipse.org/news/announcements/eclipse-lmos-redefines-agentic-ai-industry%E2%80%99s-first-open-agent-definition",
  "note": "Eclipse (2025-10-28 and 2025-11) says Frag Magenta OneBOT runs on the LMOS platform and has handled millions of customer service and sales interactions across countries. The project blog (2025-03-06) says the platform has been operational since 2023 through deployed ARC agents for contract, billing, and technical support. On the W3C WebAgents list the same day, Robert Winkler wrote that Deutsche T"
 },
 {
  "id": "developers-cloudflare-com-well-known-agent-skills-index-json",
  "org_id": "cloudflare",
  "name": "Cloudflare agent skills",
  "url": "https://developers.cloudflare.com/.well-known/agent-skills/index.json",
  "type": "origin",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Cloudflare",
    "role": "Well-known skill publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200 `application/json` at `/.well-known/agent-skills/index.json` (`0.2.0` schema) listing 19 `archive` skills including `agents-sdk`, `durable-objects`, and `wrangler`.",
    "full_detail_md": "Cloudflare serves HTTP 200 `application/json` at `/.well-known/agent-skills/index.json` conforming to `https://schemas.agentskills.io/discovery/0.2.0/schema.json`, indexing 19 skills (from `agents-sdk` and `basin` to `durable-objects` and `wrangler`), each distributed as an `archive` (`.tar.gz`) with a `sha256:` `digest`.",
    "facets": {
     "transport_or_packaging": "HTTPS well-known index (/.well-known/agent-skills/index.json) pointing to .tar.gz archives",
     "manifest_or_entry": "Discovery v0.2.0 schema (https://schemas.agentskills.io/discovery/0.2.0/schema.json) with 19 archive entries",
     "execution_or_sandbox": "Static .tar.gz skill archives verified by sha256 digest; discovery RFC v0.2.0 states clients SHALL NOT execute scripts by default",
     "verification_posture": "Live HTTP 200 probe checked 2026-10-30"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "skill_count": 19,
     "schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json"
    },
    "source_url": "https://developers.cloudflare.com/.well-known/agent-skills/index.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.cloudflare.com/.well-known/agent-skills/index.json",
  "note": "HTTP 200 `application/json` at `/.well-known/agent-skills/index.json` (`0.2.0` schema) listing 19 `archive` skills including `agents-sdk`, `durable-objects`, and `wrangler`."
 },
 {
  "id": "developers-openai-com-llms-txt",
  "org_id": "openai",
  "name": "OpenAI Developers",
  "url": "https://developers.openai.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "OpenAI (Developer Platform docs)",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `https://developers.openai.com/llms.txt` as `text/plain` (`# OpenAI Developers`), indexing API, Codex, Agentic Commerce, and Cookbook `llms.txt` files.",
    "full_detail_md": "Serves `https://developers.openai.com/llms.txt` as `text/plain; charset=utf-8` (15,522 bytes, fetched 2026-10-30). The file opens `# OpenAI Developers` as a master hub routing agents to dedicated product `llms.txt` indexes—including OpenAI API, Codex, Agentic Commerce, and Cookbook—alongside Markdown page twins and full-document exports.",
    "facets": {
     "artifact_path": "https://developers.openai.com/llms.txt",
     "companion_files": "Per-product llms.txt indexes (API, Codex, Agentic Commerce, Cookbook) and Markdown/full exports",
     "content_type_or_bytes": "text/plain; charset=utf-8 (15,522 bytes)",
     "generator_or_consumer_mode": "Master multi-product documentation index"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "marker": "# OpenAI Developers",
     "content_type": "text/plain; charset=utf-8"
    },
    "source_url": "https://developers.openai.com/llms.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.openai.com/llms.txt",
  "note": "Serves `https://developers.openai.com/llms.txt` as `text/plain` (`# OpenAI Developers`), indexing API, Codex, Agentic Commerce, and Cookbook `llms.txt` files."
 },
 {
  "id": "dfx-intel",
  "org_id": "dfx-intel",
  "name": "DFX Intel (dfxintel.com)",
  "url": "https://dfxintel.com/agents.txt",
  "type": "origin",
  "implements": [
   "agents-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "DFX Intel (dfxintel.com)",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring MCP servers and an A2A AgentCard",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "/agents.txt"
    },
    "source_url": "https://dfxintel.com/agents.txt"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://dfxintel.com/agents.txt",
  "note": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring MCP servers and an A2A AgentCard"
 },
 {
  "id": "dns-aid-looking-glass",
  "org_id": "dns-aid-looking-glass",
  "name": "DNS-AID Looking Glass (dns-aid.org)",
  "url": "https://www.dns-aid.org/looking-glass/",
  "type": "authority",
  "implements": [
   "dns-aid"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "dns-aid",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "DNS-AID Looking Glass (dns-aid.org)",
    "role": "Resolver / Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Interactive web resolver at `/looking-glass/`; the page resolves a zone the operator types and offers `ai.infoblox.com` as the known-good zone",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.dns-aid.org/looking-glass/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.dns-aid.org/looking-glass/",
  "note": "Interactive web resolver at `/looking-glass/`; the page resolves a zone the operator types and offers `ai.infoblox.com` as the known-good zone"
 },
 {
  "id": "dns-aid-reference-implementation",
  "org_id": "dns-aid-reference-implementation",
  "name": "dns-aid reference implementation (dns-aid/dns-aid-core, PyPI dns-aid 0.28.1)",
  "url": "https://raw.githubusercontent.com/dns-aid/dns-aid-core/main/README.md",
  "type": "sdk",
  "implements": [
   "dns-aid"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "dns-aid",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "dns-aid reference implementation (dns-aid/dns-aid-core, PyPI dns-aid 0.28.1)",
    "role": "Resolver / Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-09",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-09",
    "col4_md": "Supported (-02 draft) · v0.28.1 (2026-08-09). Python SDK, CLI `discover` command, and MCP server; README states that v0.28.1 is the reference implementation for predecessor draft-mozleywilliams-dnsop-dnsaid-02 (using -02 parameter names such as cap and bap rather than draft-mozleywilliams-dawn-dnsaid-00's proto and desc-ref). PyPI 0.28.1 uploaded 2026-08-09.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/dns-aid/dns-aid-core/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/dns-aid/dns-aid-core/main/README.md",
  "note": "Supported (-02 draft) · v0.28.1 (2026-08-09). Python SDK, CLI `discover` command, and MCP server; README states that v0.28.1 is the reference implementation for predecessor draft-mozleywilliams-dnsop-dnsaid-02 (using -02 parameter names such as cap and bap rather than draft-mozleywilliams-dawn-dnsaid-00's proto and desc-ref). PyPI 0.28.1 uploaded 2026-08-09."
 },
 {
  "id": "docs-aembit-io-okf-index-md",
  "org_id": "aembit",
  "name": "Aembit",
  "url": "https://docs.aembit.io/okf/index.md",
  "type": "origin",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Aembit",
    "role": "Docs publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`okf_version: \"0.1\"` at `https://docs.aembit.io/okf/index.md` (`text/markdown`, HTTP 200).",
    "full_detail_md": "Serves https://docs.aembit.io/okf/index.md as text/markdown; charset=utf-8 (content-length 2078, HTTP 200, response Date Wed, 04 Nov 2026 22:08:17 GMT) with bundle-root okf_version: \"0.1\", and the file calls itself an Open Knowledge Format bundle of the Aembit documentation that an agent navigates with filesystem tools. The docs page says to use the OKF bundle when the agent has a persistent workspace and file tools (Claude Code, Cursor, Copilot agents), and it lists the tarball docs.aembit.io/okf.tar.gz.",
    "facets": {
     "artifact_or_endpoint": "https://docs.aembit.io/okf/index.md and docs.aembit.io/okf.tar.gz",
     "content_type_or_schema": "text/markdown; charset=utf-8; YAML frontmatter okf_version 0.1",
     "discovery_mechanism": "Docs page points file-tool agents at the /okf/ bundle and tarball",
     "version_or_posture": "Live index HTTP 200 declaring okf_version 0.1; canonical main SPEC.md is Version 0.2"
    },
    "telemetry": {
     "artifact_kind": "okf_index_md",
     "http_status": 200,
     "marker": "okf_version: \"0.1\""
    },
    "source_url": "https://docs.aembit.io/llm-resources/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.aembit.io/llm-resources/",
  "note": "`okf_version: \"0.1\"` at `https://docs.aembit.io/okf/index.md` (`text/markdown`, HTTP 200)."
 },
 {
  "id": "docs-stripe-com-llms-txt",
  "org_id": "stripe",
  "name": "Stripe Documentation",
  "url": "https://docs.stripe.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Stripe (Documentation)",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `https://docs.stripe.com/llms.txt` as `text/markdown` (`# Stripe Documentation`), linking `.md` page twins and npm/PyPI package registries.",
    "full_detail_md": "Serves `https://docs.stripe.com/llms.txt` as `text/markdown; charset=utf-8` (252,169 bytes, fetched 2026-10-30). The file opens `# Stripe Documentation` with agent guidance to verify current SDK versions on npm (`https://www.npmjs.com/package/stripe`) and PyPI (`https://pypi.org/project/stripe/`), use general sandboxes, and follow `.md` documentation links across payments, billing, and Connect.",
    "facets": {
     "artifact_path": "https://docs.stripe.com/llms.txt",
     "companion_files": ".md page twins across docs.stripe.com; npm and PyPI package references",
     "content_type_or_bytes": "text/markdown; charset=utf-8 (252,169 bytes)",
     "generator_or_consumer_mode": "Origin documentation index with SDK version-pinning instructions"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "marker": "# Stripe Documentation",
     "content_type": "text/markdown; charset=utf-8"
    },
    "source_url": "https://docs.stripe.com/llms.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.stripe.com/llms.txt",
  "note": "Serves `https://docs.stripe.com/llms.txt` as `text/markdown` (`# Stripe Documentation`), linking `.md` page twins and npm/PyPI package registries."
 },
 {
  "id": "docs-stripe-com-well-known-skills-index-json",
  "org_id": "stripe",
  "name": "Stripe skills",
  "url": "https://docs.stripe.com/.well-known/skills/index.json",
  "type": "origin",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Well-known skill publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200 `application/json` at legacy `/.well-known/skills/index.json` listing 10 skills (including `connect-recommend`) using `v0.1.0` `files` arrays starting with `SKILL.md` (incompatible with `v0.2.0`; clients MUST check `$schema`).",
    "full_detail_md": "Stripe serves HTTP 200 `application/json` at the pre-v0.2.0 path `https://docs.stripe.com/.well-known/skills/index.json` (`x-content-timestamp: 2026-10-30T19:35:23Z`), listing 10 payment and Connect skills (such as `connect-recommend` and `upgrade-stripe`) where each entry enumerates a `files` array starting with `SKILL.md` and reference Markdown files such as `references/account-types.md`.",
    "facets": {
     "transport_or_packaging": "HTTPS well-known index at pre-v0.2.0 legacy path /.well-known/skills/index.json",
     "manifest_or_entry": "10 skill objects with name, description, and files arrays starting with SKILL.md",
     "execution_or_sandbox": "Instruction and reference Markdown files (SKILL.md and references/*.md)",
     "verification_posture": "Live HTTP 200 probe checked 2026-10-30 (x-content-timestamp 2026-10-30T19:35:23Z)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "skill_count": 10
    },
    "source_url": "https://docs.stripe.com/.well-known/skills/index.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.stripe.com/.well-known/skills/index.json",
  "note": "HTTP 200 `application/json` at legacy `/.well-known/skills/index.json` listing 10 skills (including `connect-recommend`) using `v0.1.0` `files` arrays starting with `SKILL.md` (incompatible with `v0.2.0`; clients MUST check `$schema`)."
 },
 {
  "id": "dri-es",
  "org_id": "dries",
  "name": "dri.es",
  "url": "https://dri.es/",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment",
   "api-catalog-rfc9727"
  ],
  "archetypes": [
   "crawler_policy",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "dri.es",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The home-page response carries the header `content-usage: ai=y` beside `content-signal: ai-train=yes, search=yes, ai-input=yes`. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/html; charset=utf-8",
     "attachment": "http-header",
     "content_usage": "content-usage: ai=y"
    },
    "source_url": "https://dri.es/"
   },
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "dri.es",
    "role": "Personal site search API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Profiled `application/linkset+json` for `https://dri.es/api` and `https://dri.es/mcp`, without an `item` array.",
    "full_detail_md": "On 2026-11-04, `https://dri.es/.well-known/api-catalog` returned HTTP 200 (`Content-Type: application/linkset+json` with profile `https://www.rfc-editor.org/info/rfc9727`, `Content-Length: 561`, Drupal 11) with no `item` array and no `Link` `rel=\"api-catalog\"` header. One anchor is `https://dri.es/api` (`service-desc` `https://dri.es/openapi.json`) and the other is `https://dri.es/mcp` (`service-desc` `https://dri.es/.well-known/ai-catalog.json`).",
    "facets": {
     "well_known_endpoint": "https://dri.es/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_relations": "service-desc for https://dri.es/api (openapi.json) and https://dri.es/mcp (ai-catalog.json); no item array",
     "http_or_link_header": "HTTP 200; no Link rel=api-catalog response header"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_header_rel_api_catalog": false,
     "has_item_array": false
    },
    "source_url": "https://dri.es/.well-known/api-catalog"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://dri.es/",
  "note": "The home-page response carries the header `content-usage: ai=y` beside `content-signal: ai-train=yes, search=yes, ai-input=yes`. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored."
 },
 {
  "id": "drone-research-agent-dronecraft-co-and-bookagent-cloud",
  "org_id": "drone-research-agent-dronecraft-co-and-bookagent-cloud",
  "name": "drone-research-agent.dronecraft.co and bookagent.cloud",
  "url": "https://transparency.ans.godaddy.com/tile/entries/000",
  "type": "agent",
  "implements": [
   "ans"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "ans",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "drone-research-agent.dronecraft.co and bookagent.cloud",
    "role": "Bot / Agent signer",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "On 2026-10-29 both hosts still published an `_ans` TXT record and a DNSSEC-validated TLSA record, on both resolvers used in the check.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://transparency.ans.godaddy.com/tile/entries/000"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://transparency.ans.godaddy.com/tile/entries/000",
  "note": "On 2026-10-29 both hosts still published an `_ans` TXT record and a DNSSEC-validated TLSA record, on both resolvers used in the check."
 },
 {
  "id": "duckassistbot",
  "org_id": "duckduckgo",
  "name": "DuckAssistBot",
  "url": "https://duckduckgo.com/duckduckgo-help-pages/results/duckassistbot",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "DuckDuckGo",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`DuckAssistBot` (`DuckAssistBot/1.2`) crawls in real time for source-cited AI answers, never trains models, and honors `robots.txt`.",
    "full_detail_md": "`DuckAssistBot` crawls pages in real time for AI-assisted answers that cite sources, and that data is not used to train AI models. Publishers opt out by disallowing the `DuckAssistBot` user agent in robots.txt. The user agent appears as `DuckAssistBot/1.2`.",
    "facets": {
     "user_agent_token": [
      "DuckAssistBot",
      "DuckAssistBot/1.2"
     ],
     "operator_purpose": "Real-time crawling for source-cited AI-assisted answers (not used to train AI models)",
     "ip_verification_url": "https://duckduckgo.com/duckduckgo-help-pages/results/duckassistbot",
     "robots_directives_honored": "Honors robots.txt Disallow rules for DuckAssistBot"
    },
    "telemetry": null,
    "source_url": "https://duckduckgo.com/duckduckgo-help-pages/results/duckassistbot"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://duckduckgo.com/duckduckgo-help-pages/results/duckassistbot",
  "note": "`DuckAssistBot` (`DuckAssistBot/1.2`) crawls in real time for source-cited AI answers, never trains models, and honors `robots.txt`."
 },
 {
  "id": "dune",
  "org_id": "dune",
  "name": "Dune",
  "url": "https://dune.com",
  "type": "origin",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Dune",
    "role": "Seller",
    "status": "Listed",
    "status_display": "Listed · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Catalog active: `tempo` intent `session`; POST `/api/v1/sql/execute` at `https://api.dune.com`.",
    "full_detail_md": "The catalog lists Dune as active, with method tempo, intent session, and asset 0x20c000000000000000000000b9537d11c60e8b50. POST /api/v1/sql/execute executes a SQL query, and serviceUrl is https://api.dune.com.",
    "facets": {
     "settlement_rail": "tempo session on asset 0x20c000000000000000000000b9537d11c60e8b50",
     "challenge_or_scheme": "Catalog status active; intent session rather than a one-time charge",
     "headers_or_methods": "Payment method tempo, intent session",
     "sdk_or_endpoint": "POST /api/v1/sql/execute at serviceUrl https://api.dune.com"
    },
    "telemetry": null,
    "source_url": "https://mpp.dev/api/services"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.dev/api/services",
  "note": "Catalog active: `tempo` intent `session`; POST `/api/v1/sql/execute` at `https://api.dune.com`."
 },
 {
  "id": "eclipse-ai-registry",
  "org_id": "eclipse-foundation",
  "name": "Eclipse AI Registry",
  "url": "https://github.com/modelcontextprotocol/registry/blob/main/docs/community-projects.md",
  "type": "authority",
  "implements": [
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Eclipse AI Registry",
    "role": "Downstream aggregator",
    "status": "Partial",
    "status_display": "Partial · checked 2026-11-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-11",
    "as_of": null,
    "col4_md": "Vendor-neutral registry hosted at the Eclipse Foundation, where organizations publish which MCP servers, Agent Skills, plugins and A2A agents they approve. A downstream aggregator of the official MCP Registry: it checks MCP servers against the official registry and retrieves their metadata from it.",
    "full_detail_md": "The official community-projects list describes Eclipse AI Registry as a vendor-neutral registry hosted at the Eclipse Foundation. Organizations publish which MCP servers, Agent Skills, plugins and A2A agents they approve. It is a downstream aggregator of the official MCP Registry: it checks MCP servers against the official registry and retrieves their metadata from it. The same page says inclusion does not imply endorsement.",
    "facets": {
     "registry_or_namespace": "Eclipse AI Registry at the Eclipse Foundation",
     "api_or_schema_version": "Downstream aggregator of the official MCP Registry",
     "transport_or_package_types": "Organizations publish approved MCP servers, Agent Skills, plugins, and A2A agents",
     "verification_posture": "Named in the official community-projects list (checked 2026-11-11)"
    },
    "telemetry": null,
    "source_url": "https://github.com/modelcontextprotocol/registry/blob/main/docs/community-projects.md"
   }
  ],
  "observed": "2026-11-11",
  "date_basis": "recorded",
  "source": "https://github.com/modelcontextprotocol/registry/blob/main/docs/community-projects.md",
  "note": "Vendor-neutral registry hosted at the Eclipse Foundation, where organizations publish which MCP servers, Agent Skills, plugins and A2A agents they approve. A downstream aggregator of the official MCP Registry: it checks MCP servers against the official registry and retrieves their metadata from it."
 },
 {
  "id": "eclipse-lmos-kotlin-sdk",
  "org_id": "eclipse-lmos-kotlin-sdk",
  "name": "Eclipse LMOS Kotlin SDK",
  "url": "https://github.com/eclipse-lmos/lmos-kotlin-sdk",
  "type": "sdk",
  "implements": [
   "lmos"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "lmos",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Eclipse LMOS Kotlin SDK",
    "role": "Client SDK / CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "The lmos-kotlin-sdk README says the SDK connects to a Web of Things-enabled agent by pointing at its well-known Thing Description. The published client coordinate on that page is lmos-kotlin-sdk-client:0.1.0-SNAPSHOT. Repository eclipse-lmos/lmos-kotlin-sdk, checked 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/eclipse-lmos/lmos-kotlin-sdk"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/eclipse-lmos/lmos-kotlin-sdk",
  "note": "The lmos-kotlin-sdk README says the SDK connects to a Web of Things-enabled agent by pointing at its well-known Thing Description. The published client coordinate on that page is lmos-kotlin-sdk-client:0.1.0-SNAPSHOT. Repository eclipse-lmos/lmos-kotlin-sdk, checked 2026-10-29."
 },
 {
  "id": "edge",
  "org_id": "microsoft",
  "name": "Microsoft Edge",
  "url": "https://developer.microsoft.com/en-us/microsoft-edge/origin-trials/trials/0b76fe60-b266-458e-a285-04e375c0c31a",
  "type": "harness",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Microsoft Edge",
    "role": "Browser engine",
    "status": "Origin trial",
    "status_display": "Origin trial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-10-30",
    "col4_md": "Origin trial in Edge 150; expires March 30, 2027.",
    "full_detail_md": "The implementation-status page fetched 2026-11-04 says an origin trial is live in Edge 150 and says to refer to Chrome for platform support. The Edge origin-trial page lists trial expiration March 30, 2027 and describes an origin trial for WebMCP so websites can register tools for agents, and the 2026-09-21 Edge post says the WebMCP spec in Microsoft Edge is ready for testing, with samples and a browser extension to run and debug WebMCP tools.",
    "facets": {
     "engine_or_runtime": "Microsoft Edge",
     "api_surface_or_flag": "WebMCP origin trial; platform support refers to the Chrome implementation status",
     "position_or_status": "Origin trial live in Edge 150",
     "package_or_version": "Edge 150; trial expiration March 30, 2027"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/webmachinelearning/webmcp/main/implementation-status.md",
  "note": "Origin trial in Edge 150; expires March 30, 2027."
 },
 {
  "id": "elsevier-com",
  "org_id": "elsevier",
  "name": "Elsevier",
  "url": "https://www.elsevier.com/.well-known/tdmrep.json",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Elsevier",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Well-known `tdmrep.json` (HTTP 200, `application/json;charset=utf-8`, checked 2026-10-30) sets `location` `/`, `tdm-reservation` 1, and `tdm-policy` `https://www.elsevier.com/tdm/tdmrep-policy.json`. The adopters list also records http headers + html metadata, with a policy, plus Crossref metadata, PDF and EPUB metadata.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json;charset=utf-8",
     "attachment": "well-known",
     "location": "/",
     "tdm_reservation": 1,
     "tdm_policy": "https://www.elsevier.com/tdm/tdmrep-policy.json"
    },
    "source_url": "https://www.elsevier.com/.well-known/tdmrep.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.elsevier.com/.well-known/tdmrep.json",
  "note": "Well-known `tdmrep.json` (HTTP 200, `application/json;charset=utf-8`, checked 2026-10-30) sets `location` `/`, `tdm-reservation` 1, and `tdm-policy` `https://www.elsevier.com/tdm/tdmrep-policy.json`. The adopters list also records http headers + html metadata, with a policy, plus Crossref metadata, PDF and EPUB metadata."
 },
 {
  "id": "emacs-agent-shell",
  "org_id": "emacs",
  "name": "agent-shell",
  "url": "https://xenodium.com/introducing-agent-shell",
  "type": "harness",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Emacs agent-shell",
    "role": "Community Emacs client package",
    "status": "Development",
    "status_display": "Development · as of 2025-09-25",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-25",
    "col4_md": "Initial native Emacs shell on `comint-mode` built on the `acp.el` Emacs Lisp ACP client.",
    "full_detail_md": "Introduced on 25 September 2025 as an initial version, `agent-shell` is a community Emacs shell powered by `comint-mode` and built on `acp.el` (an Emacs Lisp implementation of ACP) with configuration examples for Gemini CLI and Claude Code.",
    "facets": {
     "role_in_acp": "Editor package client",
     "integration_mode": "Community Emacs package (agent-shell on comint-mode + acp.el client)",
     "transport": "JSON-RPC 2.0 over stdio",
     "verification_posture": "Author announcement post (initial version, 2025-09-25)",
     "sdk_or_package": "agent-shell / acp.el"
    },
    "telemetry": null,
    "source_url": "https://xenodium.com/introducing-agent-shell"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://xenodium.com/introducing-agent-shell",
  "note": "Initial native Emacs shell on `comint-mode` built on the `acp.el` Emacs Lisp ACP client."
 },
 {
  "id": "envoy",
  "org_id": "envoy",
  "name": "Envoy",
  "url": "https://www.envoyproxy.io",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Envoy",
    "role": "Relying proxy",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "SPIRE SDS installs and rotates TLS certificates and trust bundles inside Envoy.",
    "full_detail_md": "SPIRE provides an implementation of the Envoy Secret Discovery Service (SDS) for use with Envoy Proxy. SDS can be used to transparently install and rotate TLS certificates and trust bundles in Envoy. The SPIFFE overview also lists Envoy under open-source software that works with SPIFFE, beside Ghostunnel. The overview works-with row marks Envoy for X.509 SVID, JWT SVID, and SPIFFE Authentication, and not for Workload API.",
    "facets": {
     "svid_or_bundle_format": "SPIRE SDS installs and rotates TLS certificates and trust bundles. The works-with row also marks X.509 SVID and JWT SVID.",
     "api_or_federation_surface": "SPIRE's implementation of the Envoy Secret Discovery Service (SDS).",
     "attestation_or_trust_domain": "Works-with mark for federated SPIFFE authentication based on trust domain name. No Workload API mark.",
     "verification_posture": "SDS integration is documented in the SPIRE README. The three works-with marks are a SPIFFE ecosystem listing. Graded partial."
    },
    "telemetry": null,
    "source_url": "https://github.com/spiffe/spire/blob/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/spiffe/spire/blob/main/README.md",
  "note": "SPIRE SDS installs and rotates TLS certificates and trust bundles inside Envoy."
 },
 {
  "id": "erc-8004-identity-reputation-registries",
  "org_id": "erc-8004",
  "name": "ERC-8004 Identity and Reputation Registries",
  "url": "https://github.com/erc-8004/erc-8004-contracts",
  "type": "authority",
  "implements": [
   "erc-8004"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "ERC-8004 Identity and Reputation Registries",
    "role": "Registry / Smart contract",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Ethereum mainnet IdentityRegistry `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432` and ReputationRegistry `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63`.",
    "full_detail_md": "The contracts README repeats IdentityRegistry `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432` and ReputationRegistry `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63` from Ethereum Mainnet through 0G Mainnet, and 8004.org (2026-01-29) says those singleton registries, with verified identical bytecode, are officially live on Ethereum mainnet. The Validation Registry remains under active update and is not yet available, so this row covers Identity and Reputation only.",
    "facets": {
     "registry_or_contract": "IdentityRegistry 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 and ReputationRegistry 0x8004BAa17C55a88189AE136b182e5fdA19dE9b63",
     "chains_or_networks": "Shared mainnet address pair from Ethereum Mainnet through 0G Mainnet; testnet pair 0x8004A818BFB912233c491871b3d84c89A494BD9e and 0x8004B663056A597Dffe9eCcC1965A193B7388713 from Ethereum Sepolia through 0G Galileo Testnet",
     "standards_profile": "ERC-721 URIStorage Identity Registry plus Reputation Registry; Validation Registry still under active update and not yet available",
     "sdk_or_deployment": "Per-chain singleton contracts with verified identical bytecode and one canonical deployment per chain"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/erc-8004/erc-8004-contracts/master/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/erc-8004/erc-8004-contracts/master/README.md",
  "note": "Ethereum mainnet IdentityRegistry `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432` and ReputationRegistry `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63`."
 },
 {
  "id": "etsy",
  "org_id": "etsy",
  "name": "Etsy",
  "url": "https://www.etsy.com",
  "type": "origin",
  "implements": [
   "agentic-commerce-protocol",
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Etsy",
    "role": "Marketplace",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-24",
    "col4_md": "Launched in-ChatGPT Instant Checkout for U.S. Etsy items on 2025-09-29; following OpenAI's 2026-03-24 shift, Etsy catalogs remain integrated while purchases complete on merchant-owned websites or apps.",
    "full_detail_md": "Etsy announced on 2025-09-29 (Sep 29, 2025) that U.S. ChatGPT users could discover, browse, and purchase Etsy items directly in ChatGPT via Instant Checkout. Following OpenAI's 2026-03-24 shift to merchant checkout experiences, ChatGPT's merchants page states that Etsy catalogs are integrated while purchases are completed on merchant-owned websites or apps.",
    "facets": {
     "commerce_role_or_surface": "Etsy marketplace catalog inside ChatGPT",
     "payment_or_token_rail": "Purchases completed on merchant-owned websites or apps",
     "api_or_spec_version": "Agentic Commerce Protocol, announced with ChatGPT shopping",
     "availability_or_eligibility_posture": "U.S. ChatGPT users; Shopify or Etsy catalogs already integrated"
    },
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20251220210109/https://www.etsy.com/news/meeting-buyers-where-they-are-etsy-partners-with-openai-to-enable-ai-powered-shopping"
   },
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Etsy",
    "role": "Retailer (co-developer)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-02-11",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02-11",
    "col4_md": "Co-developer; 2026-02-11 UCP checkout for US shoppers in AI Mode.",
    "full_detail_md": "The launch post (datePublished 2026-01-11) names Etsy as a co-developer, and on datePublished 2026-02-11 UCP-powered checkout was rolling out for US shoppers to buy from Etsy and Wayfair in AI Mode in Search and the Gemini app. Shopify engineering says UCP is supported by Etsy, Target, Walmart, Wayfair, and millions of Shopify merchants.",
    "facets": {
     "commerce_surface": "Etsy checkout in AI Mode in Search and the Gemini app for US shoppers",
     "payment_handlers_or_rail": "UCP-powered checkout rolling out 2026-02-11",
     "transport_bindings": "Google AI surfaces; no probed Etsy /.well-known/ucp body in this row",
     "spec_version": "Co-developer in the 2026-01-11 launch; rollout article datePublished 2026-02-11"
    },
    "telemetry": null,
    "source_url": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://web.archive.org/web/20251220210109/https://www.etsy.com/news/meeting-buyers-where-they-are-etsy-partners-with-openai-to-enable-ai-powered-shopping",
  "note": "Launched in-ChatGPT Instant Checkout for U.S. Etsy items on 2025-09-29; following OpenAI's 2026-03-24 shift, Etsy catalogs remain integrated while purchases complete on merchant-owned websites or apps."
 },
 {
  "id": "eventcatalog",
  "org_id": "eventcatalog",
  "name": "EventCatalog",
  "url": "https://www.eventcatalog.dev/blog/api-catalog",
  "type": "sdk",
  "implements": [
   "api-catalog-rfc9727"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "EventCatalog",
    "role": "Architecture catalog generator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-05-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05-25",
    "col4_md": "Publishes `/.well-known/api-catalog` as profiled `application/linkset+json` for services, domains, and MCP.",
    "full_detail_md": "EventCatalog (David Boyne, 2026-05-25) publishes a Linkset at `GET /.well-known/api-catalog` with `Content-Type: application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"`. The first version includes services and domains that have OpenAPI, AsyncAPI, or GraphQL specifications, and includes the MCP endpoint when the EventCatalog MCP server is enabled.",
    "facets": {
     "well_known_endpoint": "GET /.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_relations": "service-desc and service-doc for services and domains; MCP endpoint when the MCP server is enabled",
     "http_or_link_header": "Documented GET /.well-known/api-catalog; Content-Type application/linkset+json with RFC 9727 profile"
    },
    "telemetry": null,
    "source_url": "https://www.eventcatalog.dev/blog/api-catalog"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.eventcatalog.dev/blog/api-catalog",
  "note": "Publishes `/.well-known/api-catalog` as profiled `application/linkset+json` for services, domains, and MCP."
 },
 {
  "id": "everruns",
  "org_id": "everruns",
  "name": "Everruns",
  "url": "https://everruns.com/docs/changelog/2026-10-11-poppy-framework-personal-agents/",
  "type": "sdk",
  "implements": [
   "personal-agent-protocol"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "personal-agent-protocol",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Everruns",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-11",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-11",
    "col4_md": "Everruns changelog 2026-10-11: a Framework app can be a person's own agent over Poppy. The agent identifies itself to the company. The company reads /.well-known/poppy.json (protocol_version, organization.name, organization.domain). Until the person signs in, the company receives an ID that contains no personal information.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://everruns.com/docs/changelog/2026-10-11-poppy-framework-personal-agents/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://everruns.com/docs/changelog/2026-10-11-poppy-framework-personal-agents/",
  "note": "Everruns changelog 2026-10-11: a Framework app can be a person's own agent over Poppy. The agent identifies itself to the company. The company reads /.well-known/poppy.json (protocol_version, organization.name, organization.domain). Until the person signs in, the company receives an ID that contains no personal information."
 },
 {
  "id": "exa",
  "org_id": "exa",
  "name": "Exa (Exa MCP)",
  "url": "https://mcp.exa.ai/mcp/server-card",
  "type": "authority",
  "implements": [
   "mcp-server-cards"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-server-cards",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Exa (Exa MCP)",
    "role": "Server Card publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GET https://mcp.exa.ai/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://mcp.exa.ai/mcp, card name ai.exa/exa. Exa's docs give the hosted server as https://mcp.exa.ai/mcp.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://mcp.exa.ai/mcp/server-card"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://mcp.exa.ai/mcp/server-card",
  "note": "GET https://mcp.exa.ai/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://mcp.exa.ai/mcp, card name ai.exa/exa. Exa's docs give the hosted server as https://mcp.exa.ai/mcp."
 },
 {
  "id": "exa-exasearchbot",
  "org_id": "exa",
  "name": "ExaSearchBot",
  "url": "https://crawler.exa.ai",
  "type": "origin",
  "implements": [
   "http-message-signatures",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Exa (ExaSearchBot)",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Publishes `Ed25519` JWK and directory-response signature headers; documents signing all `ExaSearchBot` requests under RFC 9421.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` at Exa's key directory, publishing one `Ed25519` JWK and directory-response `binding0` signature headers (`tag=\"http-message-signatures-directory\"`, signature validation not established by the recorded HTTP observation), and documents signing every `ExaSearchBot` request under RFC 9421.",
    "facets": {
     "signature_or_key_format": "Publishes 1 OKP Ed25519 JWK (`kid: sDCpsJpgItYcmF_KhZozOUGIGL6a49yxE3f0yQR5SIA`) and directory-response signature headers; signature validation not established by the recorded HTTP observation",
     "directory_or_header": "HTTP 200 `application/http-message-signatures-directory+json` (`binding0` response signature)",
     "signing_algorithm": "Ed25519 / RFC 9421 (`tag=\"http-message-signatures-directory\"`)",
     "verification_role": "Bot / Agent signer (signs all outbound ExaSearchBot crawler requests)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 1,
     "kid": "sDCpsJpgItYcmF_KhZozOUGIGL6a49yxE3f0yQR5SIA",
     "signature_label": "binding0",
     "alg": "ed25519"
    },
    "source_url": "https://crawler.exa.ai/.well-known/http-message-signatures-directory"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Exa (ExaSearchBot)",
    "role": "Bot / Agent signer (Web Bot Auth profile)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Web Bot Auth profile: publishes `Ed25519` JWK and signs outbound `ExaSearchBot` requests under RFC 9421.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` at the ExaSearchBot key directory endpoint, publishing one `OKP` `Ed25519` JWK (`\"kid\":\"sDCpsJpgItYcmF_KhZozOUGIGL6a49yxE3f0yQR5SIA\"`) and directory-response signature headers (`binding0`, `tag=\"http-message-signatures-directory\"`; runtime signature validation not established by the HTTP probe), and documents signing every outbound `ExaSearchBot` request using RFC 9421 under the Web Bot Auth scheme.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth profile of RFC 9421 (`tag=\"http-message-signatures-directory\"`)",
     "signature_fields": "HTTP 200 `application/http-message-signatures-directory+json` (`binding0` response signature)",
     "algorithms_or_keys": "Publishes 1 OKP `Ed25519` JWK (`kid: sDCpsJpgItYcmF_KhZozOUGIGL6a49yxE3f0yQR5SIA`) and directory-response signature headers",
     "verification_posture": "Bot / Agent signer (signs outbound ExaSearchBot crawler requests under Web Bot Auth; directory signature validation not established by HTTP observation)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 1,
     "kid": "sDCpsJpgItYcmF_KhZozOUGIGL6a49yxE3f0yQR5SIA",
     "signature_label": "binding0",
     "alg": "ed25519"
    },
    "source_url": "https://crawler.exa.ai/.well-known/http-message-signatures-directory"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://crawler.exa.ai/.well-known/http-message-signatures-directory",
  "note": "Publishes `Ed25519` JWK and directory-response signature headers; documents signing all `ExaSearchBot` requests under RFC 9421."
 },
 {
  "id": "excalidraw",
  "org_id": "excalidraw",
  "name": "Excalidraw MCP",
  "url": "https://mcp.excalidraw.com/mcp",
  "type": "origin",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Excalidraw",
    "role": "MCP App server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Remote `https://mcp.excalidraw.com`; GET returned HTTP 200 and JSON-RPC `-32000`.",
    "full_detail_md": "The README recommends the remote server https://mcp.excalidraw.com and says it works with any client that supports MCP Apps, including Claude, ChatGPT, VS Code, and Goose. A GET of https://mcp.excalidraw.com/mcp returned HTTP 200 with JSON-RPC error -32000 and message Method not allowed, which is an endpoint probe and not a rendered ui:// view or a registry JSON record.",
    "facets": {
     "transport_or_channel": "Remote MCP URL https://mcp.excalidraw.com/mcp; GET body is JSON-RPC error -32000 Method not allowed",
     "ui_resource_or_primitive": "README says the server works with MCP Apps clients; the GET body is not an HTML ui:// resource",
     "sandbox_or_security": "No CSP or sandbox policy in the GET body; host sandboxing is left to the MCP Apps client",
     "sdk_or_version": "Public remote server named in the README; HTTP probe checked 2026-10-30"
    },
    "telemetry": {
     "http_status": 200,
     "jsonrpc_error_code": -32000,
     "jsonrpc_error_message": "Method not allowed."
    },
    "source_url": "https://github.com/excalidraw/excalidraw-mcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/excalidraw/excalidraw-mcp",
  "note": "Remote `https://mcp.excalidraw.com`; GET returned HTTP 200 and JSON-RPC `-32000`."
 },
 {
  "id": "expedia",
  "org_id": "expedia",
  "name": "Expedia",
  "url": "https://www.expedia.com",
  "type": "origin",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Expedia",
    "role": "ChatGPT app",
    "status": "Listed",
    "status_display": "Listed · as of 2025-10-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-06",
    "col4_md": "Named by TechCrunch and The Verge among the interactive apps inside ChatGPT at launch.",
    "full_detail_md": "TechCrunch names Expedia among the companies whose interactive applications ship inside ChatGPT, in the list with Booking.com, Spotify, Figma, Coursera, Zillow, and Canva. The Verge includes Expedia in the apps available inside ChatGPT starting that day.",
    "facets": {
     "transport_or_manifest": "No manifest file cited; named only in launch coverage",
     "ui_or_widget_surface": "Interactive application inside ChatGPT",
     "auth_or_permissions": "No permission model named in the cited launch coverage",
     "sdk_or_version": "Apps SDK preview period (launch coverage dated 2025-10-06)"
    },
    "telemetry": null,
    "source_url": "https://techcrunch.com/2025/10/06/openai-launches-apps-inside-of-chatgpt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://techcrunch.com/2025/10/06/openai-launches-apps-inside-of-chatgpt/",
  "note": "Named by TechCrunch and The Verge among the interactive apps inside ChatGPT at launch."
 },
 {
  "id": "ext-apps-examples",
  "org_id": "modelcontextprotocol",
  "name": "ext-apps examples",
  "url": "https://github.com/modelcontextprotocol/ext-apps",
  "type": "sdk",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "ext-apps examples",
    "role": "Example MCP App servers",
    "status": "Development",
    "status_display": "Development · as of 2026-10-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "Main examples include `examples/map-server`; release `v2.0.4` notes `pdf-server`.",
    "full_detail_md": "The ext-apps repository on main includes example projects such as examples/map-server, and release v2.0.4 published 2026-10-27 mentions example work on pdf-server and says there are no changes to the library API. These are repository examples, so the row stays Development rather than Supported, and the same README says the wire protocol is unchanged between ext-apps 1.x and 2.x while listing specification 2026-01-26 as Stable and draft as Development.",
    "facets": {
     "transport_or_channel": "Repository examples, not a probed public MCP endpoint",
     "ui_resource_or_primitive": "examples/map-server on main; v2.0.4 release notes mention pdf-server example work",
     "sandbox_or_security": "Example views follow the MCP Apps iframe model; this row does not probe a live sandbox",
     "sdk_or_version": "Main-branch examples plus release v2.0.4 (2026-10-27); wire protocol unchanged between 1.x and 2.x; draft spec remains Development"
    },
    "telemetry": null,
    "source_url": "https://github.com/modelcontextprotocol/ext-apps"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/modelcontextprotocol/ext-apps",
  "note": "Main examples include `examples/map-server`; release `v2.0.4` notes `pdf-server`."
 },
 {
  "id": "ext-apps-sdk",
  "org_id": "modelcontextprotocol",
  "name": "@modelcontextprotocol/ext-apps",
  "url": "https://github.com/modelcontextprotocol/ext-apps",
  "type": "sdk",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "@modelcontextprotocol/ext-apps",
    "role": "Official SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-27",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "npm `latest` is `2.0.4`; published `2.1.0` is not that tag. package.json on main is version 2.1.0.",
    "full_detail_md": "npm dist-tag latest is 2.0.4 and dist-tag release-2.0 is 2.0.3, while version 2.1.0 was published later on 2026-10-27 and is not the latest tag, so the Supported grade follows the latest tag and the v2.0.4 release rather than 2.1.0 or the main-branch draft. Release v2.0.4 says there are no library API changes, release 2.0.0 says the MCP Apps wire protocol is unchanged, and the README says views render inline in Claude, ChatGPT, and any other compliant client and ships create-mcp-app, migrate-oai-app, add-app-to-server, and convert-web-app, while main lists 2026-01-26 as Stable and draft as Development. package.json on main declares version 2.1.0.",
    "facets": {
     "transport_or_channel": "App class and PostMessageTransport in @modelcontextprotocol/ext-apps; wire protocol unchanged from 1.x to 2.x",
     "ui_resource_or_primitive": "Views that render inline in Claude, ChatGPT, and other compliant chat clients",
     "sandbox_or_security": "SDK hosts the MCP Apps sandbox model; this row does not treat the main draft spec as the supported snapshot",
     "sdk_or_version": "npm latest 2.0.4 (2026-10-27) is the Supported tag; 2.1.0 is published the same day and is not latest; package.json on main is version 2.1.0; release-2.0 tag is 2.0.3"
    },
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@modelcontextprotocol/ext-apps"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@modelcontextprotocol/ext-apps",
  "note": "npm `latest` is `2.0.4`; published `2.1.0` is not that tag. package.json on main is version 2.1.0."
 },
 {
  "id": "factory-droid",
  "org_id": "factory",
  "name": "Droid",
  "url": "https://docs.factory.com/harness/agents-md",
  "type": "harness",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Factory (Droid)",
    "role": "Coding agent / CLI",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Searches CWD-to-Git-root and dynamic Read paths for `AGENTS.md`, refining root rules with nested files.",
    "full_detail_md": "Loads `AGENTS.md` at session startup (80,000-character initial cap) by searching from the current working directory up to the Git root—checking each directory plus `.factory/`, `.agents/`, `.agent/`, and personal `~/.factory/`, `~/.agents/`, `~/.agent/`—and dynamically discovers nested subdirectory `AGENTS.md` files on file Read paths (40,000-character cap) where nested files refine root rules and user prompts take top priority.",
    "facets": {
     "discovery_behavior": "Startup scan from CWD up to Git root (80,000-char cap) plus dynamic Read-path discovery in subdirectories (40,000-char cap)",
     "hierarchy_precedence": "Current user request > nested subdirectory AGENTS.md > root project AGENTS.md > personal (~/.factory, ~/.agents, ~/.agent) defaults",
     "fallback_files": "agents.md; Agents.md; CLAUDE.md; Claude.md; .factory/; .agents/; .agent/",
     "verification_posture": "Documented in Factory Droid harness documentation"
    },
    "telemetry": null,
    "source_url": "https://docs.factory.com/harness/agents-md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.factory.com/harness/agents-md",
  "note": "Searches CWD-to-Git-root and dynamic Read paths for `AGENTS.md`, refining root rules with nested files."
 },
 {
  "id": "fastmcp-cimd",
  "org_id": "fastmcp",
  "name": "FastMCP",
  "url": "https://gofastmcp.com/clients/auth/cimd",
  "type": "sdk",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "FastMCP",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "The HTTPS metadata URL becomes `client_id`; the server fetches that document.",
    "full_detail_md": "FastMCP's client CIMD guide says the client hosts a JSON document at an HTTPS URL and that URL becomes `client_id`. When the client connects, the server fetches the metadata document and can verify identity through domain ownership.",
    "facets": {
     "metadata_flag_or_profile": "Client-hosted JSON document; the document URL is the client_id",
     "auth_method_or_pkce": "Identity is checked through domain ownership of the hosted document; the guide does not name a token_endpoint_auth_method",
     "uri_or_ssrf_rules": "The metadata document is an HTTPS URL the client controls, and the server fetches it on connect",
     "draft_or_spec_version": "Undated FastMCP client guide at gofastmcp.com, not a floating main-branch source file"
    },
    "telemetry": null,
    "source_url": "https://gofastmcp.com/clients/auth/cimd"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://gofastmcp.com/clients/auth/cimd",
  "note": "The HTTPS metadata URL becomes `client_id`; the server fetches that document."
 },
 {
  "id": "fenty-beauty",
  "org_id": "fenty-beauty",
  "name": "Fenty Beauty",
  "url": "https://fentybeauty.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Fenty Beauty",
    "role": "Seller (Shopify merchant)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`.",
    "full_detail_md": "The live profile declares protocol version 2026-08-25 (the ucp.version field, not a publication date) on fentybeautyshop.myshopify.com, where dev.ucp.shopping binds transports mcp and embedded and no dev.ucp.common service is published. Payment handlers are com.google.pay at handler spec 2026-01-11, dev.shopify.card at handler spec 2026-01-15, and dev.shopify.shop_pay at handler spec 2026-04-08, and capabilities include dev.ucp.shopping.checkout plus dev.ucp.common.identity_linking.",
    "facets": {
     "commerce_surface": "Shopify storefront fentybeautyshop.myshopify.com",
     "payment_handlers_or_rail": "com.google.pay (handler spec 2026-01-11), dev.shopify.card (handler spec 2026-01-15), dev.shopify.shop_pay (handler spec 2026-04-08)",
     "transport_bindings": "dev.ucp.shopping over mcp and embedded; no dev.ucp.common service",
     "spec_version": "ucp.version 2026-08-25 (protocol version, not a publication date); supported_versions also lists 2026-04-08 and 2026-01-23"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8",
     "ucp_version": "2026-08-25",
     "transports": [
      "mcp",
      "embedded"
     ],
     "payment_handlers": [
      "com.google.pay",
      "dev.shopify.card",
      "dev.shopify.shop_pay"
     ],
     "merchant_host": "fentybeautyshop.myshopify.com",
     "publishes_dev_ucp_common_service": false
    },
    "source_url": "https://fentybeauty.com/.well-known/ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://fentybeauty.com/.well-known/ucp",
  "note": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`."
 },
 {
  "id": "figma",
  "org_id": "figma",
  "name": "Figma",
  "url": "https://www.figma.com",
  "type": "sdk",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Figma",
    "role": "Plugin package",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Main-branch `figma` `2.0.20` with `skills/` and connector `.app.json`.",
    "full_detail_md": "Figma is a DevDay launch app and the openai/plugins main-branch package `figma` at version `2.0.20`, describing workflows for design implementation, Code Connect templates, and design system rule generation, with `./skills/` and `.app.json`. The connector id is `connector_68df038e0ba48191908c8434991bbac2`, interface capabilities are Interactive, Read, and Write, and those cited files are the floating main branch, so this row is Partial rather than Supported.",
    "facets": {
     "transport_or_manifest": "openai/plugins main: plugin.json version 2.0.20, skills ./skills/, .app.json",
     "ui_or_widget_surface": "Interactive capability; design-to-code workflows inside the host",
     "auth_or_permissions": "No separate auth handshake in the cited manifest; capabilities are Interactive, Read, and Write",
     "sdk_or_version": "plugin.json version 2.0.20 on main; also a DevDay launch app"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/openai/plugins/main/plugins/figma/.codex-plugin/plugin.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/openai/plugins/main/plugins/figma/.codex-plugin/plugin.json",
  "note": "Main-branch `figma` `2.0.20` with `skills/` and connector `.app.json`."
 },
 {
  "id": "figma-mcp-as",
  "org_id": "figma",
  "name": "Figma MCP",
  "url": "https://mcp.figma.com",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Figma",
    "role": "MCP authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`https://mcp.figma.com/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://api.figma.com`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. The document also publishes a `registration_endpoint`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "issuer": "https://api.figma.com",
     "grant_profile": "urn:ietf:params:oauth:grant-profile:id-jag"
    },
    "source_url": "https://mcp.figma.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mcp.figma.com/.well-known/oauth-authorization-server",
  "note": "`https://mcp.figma.com/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://api.figma.com`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. The document also publishes a `registration_endpoint`."
 },
 {
  "id": "firecrawl",
  "org_id": "firecrawl",
  "name": "Firecrawl",
  "url": "https://www.firecrawl.dev/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Firecrawl",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://www.firecrawl.dev/auth.md allows one registration method: identity_assertion with assertion_type urn:ietf:params:oauth:token-type:id-jag and requested_credential_type api_key. The credential is a Firecrawl API key used as a bearer token. Authorization-server metadata sets agent_auth.skill to that file, register_uri https://www.firecrawl.dev/agent/auth, and revocation_uri https://www.firecrawl.dev/agent/auth/revoke.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.firecrawl.dev/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.firecrawl.dev/auth.md",
  "note": "https://www.firecrawl.dev/auth.md allows one registration method: identity_assertion with assertion_type urn:ietf:params:oauth:token-type:id-jag and requested_credential_type api_key. The credential is a Firecrawl API key used as a bearer token. Authorization-server metadata sets agent_auth.skill to that file, register_uri https://www.firecrawl.dev/agent/auth, and revocation_uri https://www.firecr"
 },
 {
  "id": "flutter-genui",
  "org_id": "flutter",
  "name": "Flutter GenUI SDK",
  "url": "https://flutter.dev/blog/new-updates-to-a2ui-and-flutters-genui-package",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Flutter GenUI SDK",
    "role": "Client renderer",
    "status": "Supported",
    "status_display": "Supported · as of 2026-05-14",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05-14",
    "col4_md": "Roadmap marks Flutter GenUI Stable; the May 14, 2026 post adopts `v0.9`.",
    "full_detail_md": "The roadmap marks Flutter (GenUI SDK) Stable and says it works on mobile, web, and desktop. The May 14, 2026 Flutter post says genui uses A2UI to connect with an agent, provide a catalog of widgets, and present those widgets, driven by adoption of v0.9, and the ecosystem page says the GenUI SDK uses A2UI between server-side agents and Flutter applications.",
    "facets": {
     "transport_or_binding": "A2UI between server-side agents and Flutter applications",
     "component_or_catalog": "Widget catalog handed to the agent",
     "spec_version": "Roadmap Stable; Flutter post 2026-05-14 adopts v0.9",
     "sdk_or_renderer": "Flutter GenUI SDK for mobile, web, and desktop"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/roadmap/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2ui.org/roadmap/",
  "note": "Roadmap marks Flutter GenUI Stable; the May 14, 2026 post adopts `v0.9`."
 },
 {
  "id": "fly-io",
  "org_id": "fly-io",
  "name": "Fly.io",
  "url": "https://fly.io/.well-known/ard.json",
  "type": "origin",
  "implements": [
   "api-catalog-rfc9727",
   "ard"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Fly.io",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"1.0\"`) with 4 entries, first `urn:air:fly.io:mcp:sprites` type `application/mcp-server-card+json` at https://fly.io/.well-known/mcp/server-card.json",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://fly.io/.well-known/ard.json"
   },
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Fly.io",
    "role": "Compute platform API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Three `item` APIs in profiled `application/linkset+json`; no catalog `Link` response header.",
    "full_detail_md": "On 2026-11-04, `https://fly.io/.well-known/api-catalog` returned HTTP 200 (`content-length: 857`, `server: Fly/366e4bf88 (2026-10-27)`) as `application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"; charset=utf-8`, with no `Link` response header. The `item` array lists `https://api.machines.dev/v1`, `https://api.sprites.dev/v1`, and `https://sprites.dev/mcp`, and the first two also carry `service-desc`, `service-doc`, and `status`.",
    "facets": {
     "well_known_endpoint": "https://fly.io/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"; charset=utf-8",
     "link_relations": "item (api.machines.dev/v1, api.sprites.dev/v1, sprites.dev/mcp); service-desc; service-doc; status",
     "http_or_link_header": "HTTP 200; no Link rel=api-catalog response header"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"; charset=utf-8",
     "link_header_rel_api_catalog": false,
     "has_item_array": true
    },
    "source_url": "https://fly.io/.well-known/api-catalog"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://fly.io/.well-known/ard.json",
  "note": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"1.0\"`) with 4 entries, first `urn:air:fly.io:mcp:sprites` type `application/mcp-server-card+json` at https://fly.io/.well-known/mcp/server-card.json"
 },
 {
  "id": "follow-it",
  "org_id": "follow-it",
  "name": "follow.it",
  "url": "https://follow.it",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "follow.it",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "robots.txt is marked `# START nuxt-robots (indexable)`. The `User-agent: *` group serves `Content-Usage: bots=y, train-ai=n` and `Content-Signal: ai-train=no, search=yes`. `bots` is not a vocab-08 Table 1 label (`train-ai`, `ai-use`, `search`), and any unknown labels MUST be ignored. The label that remains, `train-ai`, is the Table 1 label for AI Training.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "attachment": "robots.txt",
     "content_usage": "Content-Usage: bots=y, train-ai=n",
     "generator_mark": "# START nuxt-robots (indexable)"
    },
    "source_url": "https://follow.it/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://follow.it/robots.txt",
  "note": "robots.txt is marked `# START nuxt-robots (indexable)`. The `User-agent: *` group serves `Content-Usage: bots=y, train-ai=n` and `Content-Signal: ai-train=no, search=yes`. `bots` is not a vocab-08 Table 1 label (`train-ai`, `ai-use`, `search`), and any unknown labels MUST be ignored. The label that remains, `train-ai`, is the Table 1 label for AI Training."
 },
 {
  "id": "forter",
  "org_id": "forter",
  "name": "Forter",
  "url": "https://thepaypers.com/fraud-and-fincrime/news/skyfire-and-forter-partner-to-verify-ai-agents-at-checkout",
  "type": "authority",
  "implements": [
   "kyapay-token"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Forter",
    "role": "Checkout fraud verifier",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Ingests Skyfire KYA JWT identity & consumer trust claims into checkout fraud decisioning (piloted with US online retailer Jomashop)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://thepaypers.com/fraud-and-fincrime/news/skyfire-and-forter-partner-to-verify-ai-agents-at-checkout"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://thepaypers.com/fraud-and-fincrime/news/skyfire-and-forter-partner-to-verify-ai-agents-at-checkout",
  "note": "Ingests Skyfire KYA JWT identity & consumer trust claims into checkout fraud decisioning (piloted with US online retailer Jomashop)"
 },
 {
  "id": "gazzetta-del-sud",
  "org_id": "gazzetta-del-sud",
  "name": "Gazzetta del Sud",
  "url": "https://gazzettadelsud.it",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Gazzetta del Sud",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "robots.txt serves `Content-Usage: ai=n` in the `User-Agent: *` group, with the comment `# Source: https://robotstxt.com/ai`. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "attachment": "robots.txt",
     "content_usage": "Content-Usage: ai=n"
    },
    "source_url": "https://gazzettadelsud.it/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://gazzettadelsud.it/robots.txt",
  "note": "robots.txt serves `Content-Usage: ai=n` in the `User-Agent: *` group, with the comment `# Source: https://robotstxt.com/ai`. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored."
 },
 {
  "id": "gcp-workload-identity-federation",
  "org_id": "google",
  "name": "GCP Workload Identity Federation",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "GCP Workload Identity Federation",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Commercial works-with listing: X.509 SVID and JWT SVID authentication.",
    "full_detail_md": "The SPIFFE overview lists GCP Workload Identity Federation under commercial software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID and JWT SVID.",
    "facets": {
     "svid_or_bundle_format": "Marks for X.509 SVID-based authentication and JWT SVID-based authentication.",
     "api_or_federation_surface": "SPIFFE Authentication and the Workload API are not marked.",
     "attestation_or_trust_domain": "No trust-domain federation mark. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Commercial works-with listing: X.509 SVID and JWT SVID authentication."
 },
 {
  "id": "gemini-cli",
  "org_id": "google",
  "name": "Gemini CLI",
  "url": "https://github.com/google-gemini/gemini-cli",
  "type": "harness",
  "implements": [
   "agent-client-protocol",
   "agents-md",
   "anthropic-agent-skills-format",
   "cloudflare-markdown-for-agents",
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Gemini CLI",
    "role": "CLI coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2025-06-25",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-06-25",
    "col4_md": "Open-source (`Apache 2.0`) terminal agent with built-in Model Context Protocol client support and bundled extensions.",
    "full_detail_md": "Google's open-source (`Apache 2.0`) Gemini CLI agent (`2025-06-25`) includes built-in MCP client support and bundled extensions to connect external context and tools in interactive and scripted terminal workflows.",
    "facets": {
     "transport": "stdio, Streamable HTTP",
     "auth_or_oauth": "Environment credentials and OAuth",
     "primitives": "tools, prompts, resources",
     "sdk_or_package": "@google/gemini-cli (Apache 2.0)"
    },
    "telemetry": null,
    "source_url": "https://blog.google/innovation-and-ai/technology/developers-tools/introducing-gemini-cli-open-source-ai-agent/"
   },
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Google Gemini CLI",
    "role": "Native CLI coding agent (reference implementation)",
    "status": "Supported",
    "status_display": "Supported · as of 2025-08-27",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-08-27",
    "col4_md": "Native `gemini --acp` mode speaking `JSON-RPC 2.0` over `stdio`; initial ACP reference implementation with Zed.",
    "full_detail_md": "Google's Gemini CLI provides a native ACP operational mode started with `gemini --acp` over `stdio` (`JSON-RPC 2.0`), partnered with Zed on 2025-08-27 as the initial ACP reference implementation and distributed through the official ACP Registry.",
    "facets": {
     "role_in_acp": "Agent server (initial reference implementation)",
     "integration_mode": "Native CLI mode (gemini --acp)",
     "transport": "JSON-RPC 2.0 over stdio",
     "verification_posture": "First-party CLI documentation & official ACP Registry listing",
     "sdk_or_package": "gemini --acp (Gemini CLI)"
    },
    "telemetry": null,
    "source_url": "https://geminicli.com/docs/cli/acp-mode/"
   },
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Gemini CLI",
    "role": "Agent CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-27",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-27",
    "col4_md": "Discovers `SKILL.md` in `.agents/skills/` and `.gemini/skills/`, calling `activate_skill` with user consent before injecting instructions.",
    "full_detail_md": "Introduced in preview in `v0.23.0` (`2026-01-07`) and enabled by default in `v0.25.0`/`v0.26.0` (`2026-01-27`), Gemini CLI scans workspace and user skills in `.agents/skills/`, `.gemini/skills/`, `~/.agents/skills/`, and `~/.gemini/skills/` (giving `.agents/skills/` higher precedence), injects `name` and `description` at session startup, and calls `activate_skill` with an interactive user confirmation prompt before adding the `SKILL.md` body and directory path to the session.",
    "facets": {
     "transport_or_packaging": "Workspace and user directories (.agents/skills/, .gemini/skills/, ~/.agents/skills/, ~/.gemini/skills/) and extensions",
     "manifest_or_entry": "SKILL.md directory with name and description frontmatter",
     "execution_or_sandbox": "activate_skill tool with interactive UI consent prompt granting directory read permission; seatbelt policy engine",
     "verification_posture": "First-party Gemini CLI documentation and release notes (2026-01-07 to 2026-01-27, checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://geminicli.com/docs/cli/skills/"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Google Gemini CLI",
    "role": "Coding agent / CLI",
    "status": "Partial",
    "status_display": "Partial · as of 2026-06-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-30",
    "col4_md": "Uses `GEMINI.md` by default; `agents.md` FAQ documents configuring `AGENTS.md` via `.gemini/settings.json`.",
    "full_detail_md": "Loads `GEMINI.md` by default (per Galster et al., Table 1) and can be configured to read `AGENTS.md` by setting `{ \"context\": { \"fileName\": \"AGENTS.md\" }, }` in `.gemini/settings.json` as documented in the `agents.md` FAQ.",
    "facets": {
     "discovery_behavior": "Reads GEMINI.md by default; reads AGENTS.md when context.fileName is set in .gemini/settings.json",
     "hierarchy_precedence": "Configured via .gemini/settings.json",
     "fallback_files": "GEMINI.md; .gemini/settings.json",
     "verification_posture": "Documented in the `agents.md` FAQ and Galster et al. (arXiv:2602.14690v5, Table 1)"
    },
    "telemetry": null,
    "source_url": "https://agents.md/"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Gemini CLI",
    "role": "Coding agent",
    "status": "Development",
    "status_display": "Development · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Floating `main` branch sends `text/markdown, text/plain;q=0.9, application/json;q=0.9, text/html;q=0.8` ahead of `*/*;q=0.5`; released `0.28.2` sent `Accept: */*`.",
    "full_detail_md": "In web-fetch.ts on floating main, sends `text/markdown, text/plain;q=0.9, application/json;q=0.9, text/html;q=0.8, application/pdf;q=0.7, video/*;q=0.7, */*;q=0.5` (upgraded since Checkly's 2026-02-19 study of released `0.28.2`, which sent `Accept: */*`).",
    "facets": {
     "negotiation_or_artifact": "web-fetch.ts on main sends a q-weighted Accept that starts with text/markdown",
     "response_headers": "Accept: text/markdown, text/plain;q=0.9, application/json;q=0.9, text/html;q=0.8, application/pdf;q=0.7, video/*;q=0.7, */*;q=0.5",
     "content_type_or_tokens": "text/markdown first; Checkly's 0.28.2 build sent Accept: */* and did not request Markdown",
     "verification_posture": "Observed on floating `main` branch (`packages/core/src/tools/web-fetch.ts`, checked 2026-11-04); Checkly's 2026-02-19 test of released `v0.28.2` recorded `Accept: */*` (`negotiates_markdown: false`)."
    },
    "telemetry": {
     "http_status": 200,
     "accept_header": "text/markdown, text/plain;q=0.9, application/json;q=0.9, text/html;q=0.8, application/pdf;q=0.7, video/*;q=0.7, */*;q=0.5"
    },
    "source_url": "https://raw.githubusercontent.com/google-gemini/gemini-cli/main/packages/core/src/tools/web-fetch.ts"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.google/innovation-and-ai/technology/developers-tools/introducing-gemini-cli-open-source-ai-agent/",
  "note": "Open-source (`Apache 2.0`) terminal agent with built-in Model Context Protocol client support and bundled extensions."
 },
 {
  "id": "gemini-enterprise",
  "org_id": "google",
  "name": "Gemini Enterprise",
  "url": "https://docs.cloud.google.com/gemini/enterprise/docs/release-notes",
  "type": "harness",
  "implements": [
   "a2a",
   "a2ui",
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Google (Gemini Enterprise)",
    "role": "Client orchestrator",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-08-17",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-17",
    "col4_md": "August 2026 release note announces general availability for registering external `A2A` and `A2UI` (`v0.9`, `v0.8`) agents.",
    "full_detail_md": "Google Cloud's Gemini Enterprise release notes (17 August 2026 entry) announce general availability (graduating from Public Preview) for administrators to register and manage external agents using the Agent2Agent (`A2A`) Protocol for communication alongside Agent to UI (`A2UI`) `v0.8` and `v0.9` interface catalogs.",
    "facets": {
     "transport_bindings": "A2A client registration and orchestration (paired with A2UI v0.8 and v0.9 UI catalogs)",
     "discovery_artifact": "Admin-registered A2A agent in Gemini Enterprise",
     "protocol_version": "Not specified in release note entry (2026-08-17)",
     "auth_schemes": "Google Cloud console administrator configuration",
     "verification_posture": "Vendor release-notes GA announcement (2026-08-17)"
    },
    "telemetry": null,
    "source_url": "https://docs.cloud.google.com/gemini/enterprise/docs/release-notes"
   },
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Gemini Enterprise",
    "role": "Host renderer",
    "status": "Partial",
    "status_display": "Partial · as of 2026-05-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05-30",
    "col4_md": "Shell and renderer for `a2aAgentDefinition` agents; `adkAgentDefinition` agents do not render A2UI.",
    "full_detail_md": "The Cloud guide byline is May 30, 2026, while its JSON-LD datePublished is 2026-05-29, and the byline article says Gemini Enterprise is the shell, the renderer, and the transport client so you only build the agent. The ecosystem page says A2UI rendering currently requires self-serve agents registered on the A2A path (a2aAgentDefinition), and that managed agents on Vertex AI Agent Engine registered with adkAgentDefinition do not currently support A2UI rendering.",
    "facets": {
     "transport_or_binding": "A2A path via a2aAgentDefinition; Gemini Enterprise is the transport client",
     "component_or_catalog": "Built-in A2UI renderer in the Gemini Enterprise shell",
     "spec_version": "Blog byline 2026-05-30; JSON-LD datePublished 2026-05-29 is not the byline date",
     "sdk_or_renderer": "Host renderer; adkAgentDefinition managed agents do not render A2UI"
    },
    "telemetry": null,
    "source_url": "https://cloud.google.com/blog/topics/developers-practitioners/guide-to-gemini-enterprise-and-a2ui-integration/"
   },
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Gemini Enterprise",
    "role": "AI host",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-20",
    "col4_md": "October 20, 2026 post: Gemini Enterprise renders the UI in a sandboxed iframe.",
    "full_detail_md": "Dave Wang's Google Cloud post of October 20, 2026 says this MCP extension pairs a tool with a live UI, and in Gemini Enterprise that UI renders in the chat flow inside a sandboxed iframe and can expand to fullscreen or a side panel. The post points at the MCP Apps specification SEP-1865 and does not grade a registry JSON record.",
    "facets": {
     "transport_or_channel": "Tool paired with a live UI rendered in the Gemini Enterprise chat flow",
     "ui_resource_or_primitive": "Sandboxed iframe that can expand to fullscreen or a side panel",
     "sandbox_or_security": "UI renders inside a sandboxed iframe",
     "sdk_or_version": "Google Cloud post by Dave Wang, October 20, 2026, pointing at SEP-1865"
    },
    "telemetry": null,
    "source_url": "https://cloud.google.com/blog/topics/developers-practitioners/devs-guide-to-mcp-apps-in-gemini"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.cloud.google.com/gemini/enterprise/docs/release-notes",
  "note": "August 2026 release note announces general availability for registering external `A2A` and `A2UI` (`v0.9`, `v0.8`) agents."
 },
 {
  "id": "genai-provider-matrix",
  "org_id": "opentelemetry",
  "name": "semantic-conventions-genai reference matrix",
  "url": "https://github.com/open-telemetry/semantic-conventions-genai/blob/main/reference/README.md",
  "type": "authority",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "semantic-conventions-genai reference matrix",
    "role": "Provider-by-operation coverage",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "The semantic-conventions-genai reference matrix names providers `aws-bedrock`, `azure-ai-inference`, `azure-openai`, `groq`, `litellm`, `mistralai`, and `openai`. The Embeddings row names `aws-bedrock`, `azure-ai-inference`, `azure-openai`, and `cohere`. Fetch Response names `openai`. A Memory row is present with an empty provider cell.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/open-telemetry/semantic-conventions-genai/blob/main/reference/README.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/open-telemetry/semantic-conventions-genai/blob/main/reference/README.md",
  "note": "The semantic-conventions-genai reference matrix names providers `aws-bedrock`, `azure-ai-inference`, `azure-openai`, `groq`, `litellm`, `mistralai`, and `openai`. The Embeddings row names `aws-bedrock`, `azure-ai-inference`, `azure-openai`, and `cohere`. Fetch Response names `openai`. A Memory row is present with an empty provider cell."
 },
 {
  "id": "general-informatics",
  "org_id": "general-informatics",
  "name": "General Informatics (www.general-informatics.com)",
  "url": "https://www.general-informatics.com/agents.txt",
  "type": "origin",
  "implements": [
   "agents-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "General Informatics (www.general-informatics.com)",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring a Skills file, WebMCP, and an MCP page",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "/agents.txt"
    },
    "source_url": "https://www.general-informatics.com/agents.txt"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://www.general-informatics.com/agents.txt",
  "note": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring a Skills file, WebMCP, and an MCP page"
 },
 {
  "id": "getalby-cli",
  "org_id": "alby",
  "name": "Alby",
  "url": "https://github.com/getAlby/cli",
  "type": "sdk",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Alby (getAlby/cli)",
    "role": "Wallet CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-07",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-07",
    "col4_md": "`v0.4.0` (2026-04-07) fetches L402, X402, and MPP resources.",
    "full_detail_md": "getAlby/cli release v0.4.0, published 2026-04-07, adds a unified command to fetch an L402, X402, and MPP resource.",
    "facets": {
     "settlement_rail": "Unified client fetch across L402, X402, and MPP",
     "token_or_macaroon": "L402 resource fetch; the release note does not redefine the macaroon",
     "headers_or_challenge": "L402 challenge handled by the unified fetch command added in v0.4.0",
     "sdk_or_endpoint": "getAlby/cli tag v0.4.0, published 2026-04-07"
    },
    "telemetry": null,
    "source_url": "https://api.github.com/repos/getAlby/cli/releases/tags/v0.4.0"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/repos/getAlby/cli/releases/tags/v0.4.0",
  "note": "`v0.4.0` (2026-04-07) fetches L402, X402, and MPP resources."
 },
 {
  "id": "ghostunnel",
  "org_id": "ghostunnel",
  "name": "Ghostunnel",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Ghostunnel",
    "role": "Relying proxy",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication.",
    "full_detail_md": "The SPIFFE overview lists Ghostunnel under open-source software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID, JWT SVID, and SPIFFE Authentication, and is not marked for Workload API.",
    "facets": {
     "svid_or_bundle_format": "Marks for X.509 SVID-based authentication and JWT SVID-based authentication.",
     "api_or_federation_surface": "SPIFFE Authentication is marked (federated authentication by trust domain name). Workload API is not marked.",
     "attestation_or_trust_domain": "Trust-domain federation is the marked SPIFFE Authentication column. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication."
 },
 {
  "id": "gitbook",
  "org_id": "gitbook",
  "name": "GitBook",
  "url": "https://docs.gitbook.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "GitBook",
    "role": "Documentation engine",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Automatically serves `llms.txt` and `.md` pages for published documentation sites, including `https://docs.gitbook.com/llms.txt` (`# GitBook Documentation`, `text/markdown`).",
    "full_detail_md": "Serves `https://docs.gitbook.com/llms.txt` (`HTTP 200`, `text/markdown; charset=utf-8`, 132,318 bytes, fetched 2026-11-04) opening `# GitBook Documentation` and indexing `.md` guides including `/docs/getting-started/llm-ready-docs.md`. Listed on `llmstxt.org` as a documentation platform that automatically serves an `llms.txt` file for published docs sites.",
    "facets": {
     "artifact_path": "https://docs.gitbook.com/llms.txt",
     "companion_files": ".md page twins (e.g., https://gitbook.com/docs/getting-started/llm-ready-docs.md)",
     "content_type_or_bytes": "text/markdown; charset=utf-8 (132,318 bytes)",
     "generator_or_consumer_mode": "Hosted documentation platform serving /llms.txt for published sites"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "h1_title": "# GitBook Documentation"
    },
    "source_url": "https://docs.gitbook.com/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://docs.gitbook.com/llms.txt",
  "note": "Automatically serves `llms.txt` and `.md` pages for published documentation sites, including `https://docs.gitbook.com/llms.txt` (`# GitBook Documentation`, `text/markdown`)."
 },
 {
  "id": "github",
  "org_id": "github",
  "name": "GitHub",
  "url": "https://github.com/.well-known/ai-catalog.json",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file",
   "ai-crawler-tokens-robots",
   "mcp-server-cards"
  ],
  "archetypes": [
   "crawler_policy",
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "GitHub",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Level 1 catalog on github.com (`specVersion` 1.0) with one entry, `urn:air:github.com:mcp:github-mcp-server`, pointing at `https://api.githubcopilot.com/mcp/server-card`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/.well-known/ai-catalog.json"
   },
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "GitHub",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Groups `GPTBot`, `OAI-SearchBot`, `ClaudeBot`, `anthropic-ai`, and `PerplexityBot` under `Crawl-delay: 1` with `Disallow: /copilot/` and `Disallow: /gist/`.",
    "full_detail_md": "Places `User-agent: GPTBot`, `User-agent: OAI-SearchBot`, `User-agent: ClaudeBot`, `User-agent: anthropic-ai`, and `User-agent: PerplexityBot` in a shared rule group with `Crawl-delay: 1` and path exclusions including `Disallow: /copilot/`, `Disallow: /gist/`, and `Disallow: /*/archive/`.",
    "facets": {
     "scope_host": "https://github.com/robots.txt",
     "policy_role": "Publisher robots.txt policy declaration",
     "published_rules": [
      {
       "tokens": [
        "GPTBot",
        "OAI-SearchBot",
        "ClaudeBot",
        "anthropic-ai",
        "PerplexityBot"
       ],
       "directives": [
        "Crawl-delay: 1",
        "Disallow: /copilot/",
        "Disallow: /gist/",
        "Disallow: /*/archive/"
       ]
      }
     ],
     "content_signals": null
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "robots_txt",
     "marker": "User-agent: GPTBot"
    },
    "source_url": "https://github.com/robots.txt"
   },
   {
    "protocol_id": "mcp-server-cards",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GitHub (GitHub MCP Server)",
    "role": "Server Card publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-09-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-02",
    "col4_md": "GET https://api.githubcopilot.com/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://api.githubcopilot.com/mcp/, card name io.github.github/github-mcp-server. https://github.com/.well-known/ai-catalog.json (status 200, application/ai-catalog+json) links to this card. github/github-mcp-server pull request #2768, merged 2026-09-02, adds the card handler.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.githubcopilot.com/mcp/server-card"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/.well-known/ai-catalog.json",
  "note": "Level 1 catalog on github.com (`specVersion` 1.0) with one entry, `urn:air:github.com:mcp:github-mcp-server`, pointing at `https://api.githubcopilot.com/mcp/server-card`."
 },
 {
  "id": "github-agent-finder",
  "org_id": "github-agent-finder",
  "name": "GitHub agent finder (GitHub Copilot)",
  "url": "https://commandline.microsoft.com/agentic-resource-discovery-specification-ard/",
  "type": "agent",
  "implements": [
   "ard"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "GitHub agent finder (GitHub Copilot)",
    "role": "Agent runtime",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Searches GitHub's curated catalog of public AI resources or a private registry and injects the resources the prompt needs into the Copilot context window",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://commandline.microsoft.com/agentic-resource-discovery-specification-ard/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://commandline.microsoft.com/agentic-resource-discovery-specification-ard/",
  "note": "Searches GitHub's curated catalog of public AI resources or a private registry and injects the resources the prompt needs into the Copilot context window"
 },
 {
  "id": "github-com-anthropics-skills",
  "org_id": "anthropic",
  "name": "anthropics/skills",
  "url": "https://github.com/anthropics/skills",
  "type": "sdk",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "anthropics/skills",
    "role": "Reference & document skill repository",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Claude reference repo and plugin marketplace bundling Apache 2.0 examples and source-available `skills/docx`, `skills/pdf`, `skills/pptx`, and `skills/xlsx`.",
    "full_detail_md": "Anthropic's public `anthropics/skills` repository hosts Apache 2.0 example skill folders (each with a `SKILL.md` file), the `./spec` and `./template` directories, and source-available document skills (`skills/docx`, `skills/pdf`, `skills/pptx`, and `skills/xlsx`), and can be registered in Claude Code via `/plugin marketplace add anthropics/skills`.",
    "facets": {
     "transport_or_packaging": "Git repository and Claude Code plugin marketplace (anthropics/skills)",
     "manifest_or_entry": "Per-skill folder with SKILL.md (YAML name and description frontmatter)",
     "execution_or_sandbox": "Prompt instructions and bundled helper scripts; source-available document skills power Claude document tools",
     "verification_posture": "First-party GitHub repository snapshot checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://github.com/anthropics/skills"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/anthropics/skills",
  "note": "Claude reference repo and plugin marketplace bundling Apache 2.0 examples and source-available `skills/docx`, `skills/pdf`, `skills/pptx`, and `skills/xlsx`."
 },
 {
  "id": "github-com-apache-airflow-agents-md",
  "org_id": "apache",
  "name": "Apache Airflow",
  "url": "https://raw.githubusercontent.com/apache/airflow/HEAD/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "apache/airflow",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves root `AGENTS.md` (`# AGENTS instructions`, `text/plain`) covering `Dag` naming, Breeze commands, and architecture boundaries.",
    "full_detail_md": "Serves root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 23,160 bytes, checked 2026-10-30) opening `# AGENTS instructions` under an Apache-2.0 SPDX license header. Defines prose naming rules (`Write Dag (title case) in all prose`), Breeze test and environment setup commands, monorepo structure, architecture boundaries, security model, coding/testing standards, and commit/PR boundaries.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/apache/airflow/HEAD/AGENTS.md",
     "repo_scope": "Apache Airflow monorepo root (23,160 bytes; Apache-2.0 SPDX header)",
     "heading_structure": "# AGENTS instructions; ## Naming; ## Environment Setup; ## Commands; ## Repository Structure; ## Architecture Boundaries; ## Security Model; ## Coding Standards; ## Testing Standards",
     "precedence_or_nested_files": "Root monorepo specification governing Airflow core, task SDK, shared libraries, and providers"
    },
    "telemetry": {
     "artifact_kind": "agents_md",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# AGENTS instructions"
    },
    "source_url": "https://raw.githubusercontent.com/apache/airflow/HEAD/AGENTS.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/apache/airflow/HEAD/AGENTS.md",
  "note": "Serves root `AGENTS.md` (`# AGENTS instructions`, `text/plain`) covering `Dag` naming, Breeze commands, and architecture boundaries."
 },
 {
  "id": "github-com-astral-sh-uv-agents-md",
  "org_id": "astral-sh",
  "name": "uv",
  "url": "https://raw.githubusercontent.com/astral-sh/uv/HEAD/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "astral-sh/uv",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves heading-free root `AGENTS.md` (`text/plain`), opening with bulleted rules referencing `CONTRIBUTING.md` and `insta` snapshots.",
    "full_detail_md": "Serves a heading-free root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 3,746 bytes, checked 2026-10-30) consisting of flat Markdown bullet directives that point agents to `CONTRIBUTING.md` for running tools, require `insta` and `uv_snapshot!` integration test snapshots, mandate `cargo xwin clippy` for Windows cross-checks, and forbid `panic!`, `unreachable!`, `.unwrap()`, and `unsafe` code.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/astral-sh/uv/HEAD/AGENTS.md",
     "repo_scope": "uv Rust workspace root (3,746 bytes)",
     "heading_structure": "No Markdown headings (flat bulleted rule list opening `- Read CONTRIBUTING.md for guidelines on how to run tools`)",
     "precedence_or_nested_files": "Root instruction list referencing CONTRIBUTING.md for tool execution"
    },
    "telemetry": {
     "artifact_kind": "agents_md",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "Read CONTRIBUTING.md for guidelines on how to run tools"
    },
    "source_url": "https://raw.githubusercontent.com/astral-sh/uv/HEAD/AGENTS.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/astral-sh/uv/HEAD/AGENTS.md",
  "note": "Serves heading-free root `AGENTS.md` (`text/plain`), opening with bulleted rules referencing `CONTRIBUTING.md` and `insta` snapshots."
 },
 {
  "id": "github-com-huggingface-skills",
  "org_id": "huggingface",
  "name": "Hugging Face skills",
  "url": "https://github.com/huggingface/skills",
  "type": "sdk",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Hugging Face",
    "role": "Skill repository & plugin bundle",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`huggingface/skills` repository publishing `SKILL.md` folders led by `hf-cli`, with Claude, Cursor, `gemini-extension.json`, and `agentsmd/AGENTS.md` fallback manifests.",
    "full_detail_md": "Hugging Face's `huggingface/skills` repository packages AI/ML workflow folders containing `SKILL.md` with YAML frontmatter (`name` and `description`), exposing `hf-cli` as the bootstrap skill in `.claude-plugin/marketplace.json` and `.cursor-plugin/marketplace.json` (with full skills installed via `hf skills add`), `gemini-extension.json` for Gemini CLI, and `agentsmd/AGENTS.md` for agents that do not support skills.",
    "facets": {
     "transport_or_packaging": "Git repository, hf skills add CLI, and Claude/Cursor/Gemini extension manifests",
     "manifest_or_entry": "SKILL.md folders plus .claude-plugin/marketplace.json, .cursor-plugin/plugin.json, gemini-extension.json, and agentsmd/AGENTS.md",
     "execution_or_sandbox": "Host coding agent loads SKILL.md instructions and helper scripts for Hub CLI and training jobs",
     "verification_posture": "First-party GitHub repository snapshot checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://github.com/huggingface/skills"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/huggingface/skills",
  "note": "`huggingface/skills` repository publishing `SKILL.md` folders led by `hf-cli`, with Claude, Cursor, `gemini-extension.json`, and `agentsmd/AGENTS.md` fallback manifests."
 },
 {
  "id": "github-com-microsoft-vscode-agents-md",
  "org_id": "microsoft",
  "name": "VS Code",
  "url": "https://raw.githubusercontent.com/microsoft/vscode/HEAD/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "microsoft/vscode",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves root `AGENTS.md` (`# VS Code Agents Instructions`, `text/plain`) routing agents to `.github/copilot-instructions.md`.",
    "full_detail_md": "Serves root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 271 bytes, checked 2026-10-30) opening `# VS Code Agents Instructions` for AI coding agents working in the VS Code codebase and linking `.github/copilot-instructions.md` (`Copilot Instructions`) for the detailed project overview, architecture, coding guidelines, and validation steps.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/microsoft/vscode/HEAD/AGENTS.md",
     "repo_scope": "VS Code repository root (271-byte entry-point file)",
     "heading_structure": "# VS Code Agents Instructions",
     "precedence_or_nested_files": "Delegates detailed architecture, coding guidelines, and validation steps to .github/copilot-instructions.md"
    },
    "telemetry": {
     "artifact_kind": "agents_md",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# VS Code Agents Instructions"
    },
    "source_url": "https://raw.githubusercontent.com/microsoft/vscode/HEAD/AGENTS.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/microsoft/vscode/HEAD/AGENTS.md",
  "note": "Serves root `AGENTS.md` (`# VS Code Agents Instructions`, `text/plain`) routing agents to `.github/copilot-instructions.md`."
 },
 {
  "id": "github-com-pandas-dev-pandas-agents-md",
  "org_id": "pandas-dev",
  "name": "pandas",
  "url": "https://raw.githubusercontent.com/pandas-dev/pandas/HEAD/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "pandas-dev/pandas",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves root `AGENTS.md` (`# AGENTS.md`, `text/plain`) covering Meson Cython/C++ builds, GitHub interaction rules, and repository map.",
    "full_detail_md": "Serves root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 2,752 bytes, checked 2026-10-30) opening `# AGENTS.md` for the BSD-licensed Python, Cython, and C/C++ data analysis library built with Meson, with sections for `## Interactions on GitHub`, `## Required tooling`, `## Repository map`, and `## References`.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/pandas-dev/pandas/HEAD/AGENTS.md",
     "repo_scope": "pandas repository root (2,752 bytes; Python, Cython, and C/C++ built with Meson)",
     "heading_structure": "# AGENTS.md; ## Interactions on GitHub; ## Required tooling; ## Repository map; ## References",
     "precedence_or_nested_files": "Single root instruction file mapping package layout and Meson build tooling"
    },
    "telemetry": {
     "artifact_kind": "agents_md",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# AGENTS.md"
    },
    "source_url": "https://raw.githubusercontent.com/pandas-dev/pandas/HEAD/AGENTS.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/pandas-dev/pandas/HEAD/AGENTS.md",
  "note": "Serves root `AGENTS.md` (`# AGENTS.md`, `text/plain`) covering Meson Cython/C++ builds, GitHub interaction rules, and repository map."
 },
 {
  "id": "github-copilot",
  "org_id": "github",
  "name": "GitHub Copilot",
  "url": "https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions",
  "type": "harness",
  "implements": [
   "agents-md",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "GitHub Copilot",
    "role": "Coding agent",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Loads one or more `AGENTS.md` files anywhere in the repository; nearest file in the directory tree takes precedence.",
    "full_detail_md": "Supports one or more `AGENTS.md` files stored anywhere within a repository, resolving conflicts by giving precedence to the nearest `AGENTS.md` file in the directory tree, alongside repository-wide `copilot-instructions.md` in `.github`, path-specific `NAME.instructions.md` files under `.github/instructions`, or a single root `CLAUDE.md` or `GEMINI.md` file.",
    "facets": {
     "discovery_behavior": "Automatic discovery of one or more AGENTS.md files anywhere in the repository",
     "hierarchy_precedence": "Nearest AGENTS.md file in the directory tree takes precedence",
     "fallback_files": ".github/copilot-instructions.md; .github/instructions/*.md; root CLAUDE.md; root GEMINI.md",
     "verification_posture": "Documented in GitHub Copilot repository custom instructions documentation"
    },
    "telemetry": null,
    "source_url": "https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "GitHub Copilot",
    "role": "Coding agent client",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Admins configure a registry on `v0.1`, requiring `GET /v0.1/servers` and `GET /v0.1/servers/{serverName}/versions/latest`.",
    "full_detail_md": "GitHub Copilot organization and enterprise admins configure an MCP registry that must follow the `v0.1` MCP registry specification. Required routes include `GET /v0.1/servers` and `GET /v0.1/servers/{serverName}/versions/latest`. The docs say the `v0` specification is unstable and should not be implemented.",
    "facets": {
     "registry_or_namespace": "GitHub Copilot organization and enterprise MCP registry",
     "api_or_schema_version": "v0.1 MCP registry specification (v0 called unstable and not for implementation)",
     "transport_or_package_types": "Requires GET /v0.1/servers and GET /v0.1/servers/{serverName}/versions/latest",
     "verification_posture": "Document citation of GitHub Docs configure-mcp-registry (checked 2026-10-30; page undated)"
    },
    "telemetry": null,
    "source_url": "https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions",
  "note": "Loads one or more `AGENTS.md` files anywhere in the repository; nearest file in the directory tree takes precedence."
 },
 {
  "id": "github-copilot-agent-finder",
  "org_id": "github-copilot-agent-finder",
  "name": "GitHub Copilot Agent Finder",
  "url": "https://raw.githubusercontent.com/github/agentfinder-catalog/main/README.md",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "GitHub Copilot Agent Finder",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "The catalog workflow checks the GitHub MCP Registry every hour, independent of repository pushes, and opens or updates the `automation/update-ai-catalog` pull request when the generated catalog changes.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/github/agentfinder-catalog/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/github/agentfinder-catalog/main/README.md",
  "note": "The catalog workflow checks the GitHub MCP Registry every hour, independent of repository pushes, and opens or updates the `automation/update-ai-catalog` pull request when the generated catalog changes."
 },
 {
  "id": "github-copilot-cli",
  "org_id": "github",
  "name": "GitHub Copilot CLI",
  "url": "https://docs.github.com/en/copilot/reference/copilot-cli-reference/acp-server",
  "type": "harness",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GitHub Copilot CLI",
    "role": "Native CLI coding agent",
    "status": "Supported (preview)",
    "status_display": "Supported (preview) · as of 2026-01-28",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-28",
    "col4_md": "Public preview `--acp` server on `copilot` over `--stdio` (default) or `--port` TCP, launched 2026-01-28.",
    "full_detail_md": "GitHub Copilot CLI added public-preview ACP server support on 2026-01-28 via the `--acp` option on the `copilot` command, supporting `--stdio` (default) or `--port` TCP transports along with session flags such as `--available-tools`, `--excluded-tools`, and `--effort`.",
    "facets": {
     "role_in_acp": "Agent server",
     "integration_mode": "Native CLI server mode (copilot --acp, public preview)",
     "transport": "JSON-RPC 2.0 over stdio (--stdio, default) or TCP port (--port)",
     "verification_posture": "First-party GitHub reference documentation & changelog (public preview, 2026-01-28)",
     "sdk_or_package": "GitHub Copilot CLI (copilot --acp)"
    },
    "telemetry": null,
    "source_url": "https://docs.github.com/en/copilot/reference/copilot-cli-reference/acp-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.github.com/en/copilot/reference/copilot-cli-reference/acp-server",
  "note": "Public preview `--acp` server on `copilot` over `--stdio` (default) or `--port` TCP, launched 2026-01-28."
 },
 {
  "id": "github-copilot-vscode",
  "org_id": "github",
  "name": "GitHub Copilot in VS Code",
  "url": "https://code.visualstudio.com/docs/agent-customization/agent-skills",
  "type": "harness",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "GitHub Copilot in VS Code",
    "role": "IDE & CLI coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-18",
    "col4_md": "Loads skills from `~/.copilot/skills/`, `~/.claude/skills/`, and `~/.agents/skills/` across VS Code, Copilot CLI, and Copilot coding agent.",
    "full_detail_md": "Launched on `2025-12-18`, GitHub Copilot and Visual Studio Code support Agent Skills across GitHub Copilot in VS Code, Copilot CLI, the Copilot coding agent, and the experimental OpenAI Codex integration, reading personal skills from `~/.copilot/skills/`, `~/.claude/skills/`, and `~/.agents/skills/` while noting that supported locations and optional features vary by agent.",
    "facets": {
     "transport_or_packaging": "Workspace and user directories (~/.copilot/skills/, ~/.claude/skills/, ~/.agents/skills/)",
     "manifest_or_entry": "Skill folders containing instructions, scripts, and resources",
     "execution_or_sandbox": "On-demand context loading in VS Code, Copilot CLI, and Copilot coding agent",
     "verification_posture": "First-party GitHub changelog (2025-12-18) and VS Code documentation checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://github.blog/changelog/2025-12-18-github-copilot-now-supports-agent-skills/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.blog/changelog/2025-12-18-github-copilot-now-supports-agent-skills/",
  "note": "Loads skills from `~/.copilot/skills/`, `~/.claude/skills/`, and `~/.agents/skills/` across VS Code, Copilot CLI, and Copilot coding agent."
 },
 {
  "id": "github-mcp",
  "org_id": "github",
  "name": "GitHub MCP Server",
  "url": "https://api.githubcopilot.com/mcp/",
  "type": "origin",
  "implements": [
   "mcp",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GitHub",
    "role": "Remote & local MCP server",
    "status": "Live (HTTP 401)",
    "status_display": "Live (HTTP 401) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Remote HTTP server at `https://api.githubcopilot.com/mcp/` with OAuth `resource_metadata` challenge and Go `stdio` server.",
    "full_detail_md": "GitHub operates a remote HTTP MCP server at `https://api.githubcopilot.com/mcp/` that challenges unauthenticated requests with HTTP 401 and `WWW-Authenticate: Bearer` pointing to `https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp/`, alongside the open-source Go `github/github-mcp-server` binary for local `stdio` and Docker deployments.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1 Protected Resource Metadata, GitHub PAT, GitHub App",
     "primitives": "tools, resources, prompts",
     "sdk_or_package": "github.com/github/github-mcp-server"
    },
    "telemetry": {
     "http_status": 401,
     "content_type": "text/plain; charset=utf-8",
     "www_authenticate_scheme": "Bearer"
    },
    "source_url": "https://api.githubcopilot.com/mcp/"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GitHub",
    "role": "Server publisher",
    "status": "Listed in Official Registry (HTTP 200 server.json)",
    "status_display": "Listed in Official Registry (HTTP 200 server.json) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-21",
    "col4_md": "`io.github.github/github-mcp-server` `2.0.3` (published 2026-10-21): `stdio` OCI and `streamable-http` (`https://api.githubcopilot.com/mcp/`).",
    "full_detail_md": "HTTP 200 `application/json`. Latest `io.github.github/github-mcp-server` is version `2.0.3` on schema `2025-12-11`, with registry status `active` and `isLatest` true, published `2026-10-21`. It ships OCI package `ghcr.io/github/github-mcp-server:2.0.3` over `stdio` and a `streamable-http` remote at `https://api.githubcopilot.com/mcp/`.",
    "facets": {
     "registry_or_namespace": "io.github.github/github-mcp-server",
     "api_or_schema_version": "Record publishedAt 2026-10-21; validates against server.schema.json (2025-12-11).",
     "transport_or_package_types": "OCI ghcr.io/github/github-mcp-server:2.0.3 (stdio) and a streamable-http remote",
     "verification_posture": "HTTP 200 registry record probe (checked 2026-10-30, publishedAt 2026-10-21); proves registry metadata listing rather than live MCP server execution."
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "server_name": "io.github.github/github-mcp-server",
     "version": "2.0.3"
    },
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.github%2Fgithub-mcp-server/versions/2.0.3"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.githubcopilot.com/mcp/",
  "note": "Remote HTTP server at `https://api.githubcopilot.com/mcp/` with OAuth `resource_metadata` challenge and Go `stdio` server."
 },
 {
  "id": "github-mcp-registry",
  "org_id": "github",
  "name": "GitHub MCP Registry",
  "url": "https://github.blog/ai-and-ml/github-copilot/meet-the-github-mcp-registry-the-fastest-way-to-discover-mcp-servers/",
  "type": "venue",
  "implements": [
   "ai-catalog-well-known-file",
   "mcp",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GitHub MCP Registry",
    "role": "Sub-registry & IDE directory",
    "status": "Supported",
    "status_display": "Supported · as of 2025-09-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-16",
    "col4_md": "Ingests servers self-published to the OSS MCP Community Registry into GitHub and VS Code.",
    "full_detail_md": "Announced on 2025-09-16, the GitHub MCP Registry ingests servers self-published to the OSS MCP Community Registry so they automatically appear in the GitHub MCP Registry for discovery and installation in VS Code.",
    "facets": {
     "transport": "HTTPS directory & VS Code integration",
     "auth_or_oauth": "GitHub authentication",
     "primitives": "MCP server discovery & installation",
     "sdk_or_package": "OSS MCP Community Registry ingestion"
    },
    "telemetry": null,
    "source_url": "https://github.blog/ai-and-ml/github-copilot/meet-the-github-mcp-registry-the-fastest-way-to-discover-mcp-servers/"
   },
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "GitHub MCP Registry",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Registry catalog at `api.mcp.github.com/.well-known/ai-catalog.json` with `Content-Type: application/ai-catalog+json`, host.displayName `GitHub MCP Registry`, and entries such as `urn:ai:registry.modelcontextprotocol.io:microsoft:markitdown`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.mcp.github.com/.well-known/ai-catalog.json"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GitHub MCP Registry",
    "role": "Downstream marketplace",
    "status": "Partial",
    "status_display": "Partial · as of 2026-05-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-05-19",
    "col4_md": "On 2025-09-16 OSS registry servers auto-appear; 2026-05-19 adds version sync, while `github.com/mcp` onboarding stays manual.",
    "full_detail_md": "On 2025-09-16 GitHub said servers published to the OSS MCP Community Registry would automatically appear in the GitHub MCP Registry. On 2026-05-19 a GitHub collaborator wrote that the GitHub MCP Registry can sync versions from the open source registry, while onboarding a new server is still a manual curation process today. The same discussion says adding a new server to `github.com/mcp` is a manual curation step.",
    "facets": {
     "registry_or_namespace": "github.com/mcp, downstream of the OSS MCP Community Registry",
     "api_or_schema_version": "Syncs versions from the open-source registry; new-server onboarding stays manual (as of 2026-05-19)",
     "transport_or_package_types": "Marketplace listing rather than a package transport",
     "verification_posture": "Document citation of the 2025-09-16 launch post and the 2026-05-19 maintainer discussion (checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://github.blog/ai-and-ml/github-copilot/meet-the-github-mcp-registry-the-fastest-way-to-discover-mcp-servers/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.blog/ai-and-ml/github-copilot/meet-the-github-mcp-registry-the-fastest-way-to-discover-mcp-servers/",
  "note": "Ingests servers self-published to the OSS MCP Community Registry into GitHub and VS Code."
 },
 {
  "id": "glama",
  "org_id": "glama",
  "name": "Glama",
  "url": "https://glama.ai/mcp/methodology",
  "type": "venue",
  "implements": [
   "mcp",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Glama",
    "role": "Aggregator & sandbox index",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Ingests the official registry and layers sandbox schema captures, behavioral analysis, and TDQS scores.",
    "full_detail_md": "Downstream MCP ecosystem directory and aggregator that ingests and republishes entries from the Official MCP Registry and layers sandbox-derived behavioral analysis, schema captures from actual server runs, and Tool Definition Quality Scores (TDQS).",
    "facets": {
     "transport": "HTTPS directory & sandbox runner",
     "auth_or_oauth": "Public web catalog",
     "primitives": "Schema captures from actual server runs, TDQS scores",
     "sdk_or_package": "Official MCP Registry ingest"
    },
    "telemetry": null,
    "source_url": "https://glama.ai/mcp/methodology"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Glama",
    "role": "Downstream directory",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Glama re-publishes the official registry and adds sandbox data, including schema captures and `TDQS` scores.",
    "full_detail_md": "Glama ingests and re-publishes everything in the official registry, and layers its own sandbox-derived data on top, including behavioural analysis, schema captures from actual server runs, and TDQS scores.",
    "facets": {
     "registry_or_namespace": "Glama downstream directory of the official registry",
     "api_or_schema_version": "Re-publishes official registry records and overlays sandbox-derived data",
     "transport_or_package_types": "Directory metadata with schema captures and TDQS scores",
     "verification_posture": "Document citation of the Glama indexing methodology (checked 2026-10-30; page undated)"
    },
    "telemetry": null,
    "source_url": "https://glama.ai/mcp/methodology"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://glama.ai/mcp/methodology",
  "note": "Ingests the official registry and layers sandbox schema captures, behavioral analysis, and TDQS scores."
 },
 {
  "id": "glossier",
  "org_id": "glossier",
  "name": "Glossier",
  "url": "https://www.glossier.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Glossier",
    "role": "Seller (Shopify merchant)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`.",
    "full_detail_md": "The live profile declares protocol version 2026-08-25 (the ucp.version field, not a publication date) on glossier-admin.myshopify.com, where dev.ucp.shopping binds transports mcp and embedded and service dev.ucp.common is published. Payment handlers are com.google.pay at handler spec 2026-01-11, dev.shopify.card at handler spec 2026-01-15, and dev.shopify.shop_pay at handler spec 2026-04-08, and capabilities include dev.ucp.shopping.checkout plus dev.ucp.common.identity_linking.",
    "facets": {
     "commerce_surface": "Shopify storefront glossier-admin.myshopify.com",
     "payment_handlers_or_rail": "com.google.pay (handler spec 2026-01-11), dev.shopify.card (handler spec 2026-01-15), dev.shopify.shop_pay (handler spec 2026-04-08)",
     "transport_bindings": "dev.ucp.shopping over mcp and embedded; dev.ucp.common over mcp",
     "spec_version": "ucp.version 2026-08-25 (protocol version, not a publication date); supported_versions also lists 2026-04-08 and 2026-01-23"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8",
     "ucp_version": "2026-08-25",
     "transports": [
      "mcp",
      "embedded"
     ],
     "payment_handlers": [
      "com.google.pay",
      "dev.shopify.card",
      "dev.shopify.shop_pay"
     ],
     "merchant_host": "glossier-admin.myshopify.com",
     "publishes_dev_ucp_common_service": true
    },
    "source_url": "https://www.glossier.com/.well-known/ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.glossier.com/.well-known/ucp",
  "note": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`."
 },
 {
  "id": "godaddy-agent-identity",
  "org_id": "godaddy-agent-identity",
  "name": "GoDaddy Agent Identity",
  "url": "https://www.godaddy.com/en/ans",
  "type": "authority",
  "implements": [
   "ans"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "ans",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "GoDaddy Agent Identity",
    "role": "Identity issuer / CA",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2025-11-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-20",
    "col4_md": "ANS private CA signs identity certificates. The public log at transparency.ans.godaddy.com uses checkpoint format `c2sp-tlog/v1` and origin `transparency.ans.godaddy.com`. The ANS API has been live for builders since 2025-11-20. Since 2026-10 a Personal Access Token with ANS scopes can register and manage agents. The registry page still shows Publish Agent and Manage Agents as Coming Soon. The Nov. 10, 2026 Linux Foundation release lists GoDaddy among 11 organizations that have contributed to or adopted ANS.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.godaddy.com/en/ans"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.godaddy.com/en/ans",
  "note": "ANS private CA signs identity certificates. The public log at transparency.ans.godaddy.com uses checkpoint format `c2sp-tlog/v1` and origin `transparency.ans.godaddy.com`. The ANS API has been live for builders since 2025-11-20. Since 2026-10 a Personal Access Token with ANS scopes can register and manage agents. The registry page still shows Publish Agent and Manage Agents as Coming Soon. The Nov"
 },
 {
  "id": "google-a2a-x402",
  "org_id": "google",
  "name": "Google Cloud a2a-x402 Extension",
  "url": "https://github.com/google-agentic-commerce/a2a-x402",
  "type": "sdk",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Google Cloud (a2a-x402)",
    "role": "Protocol extension",
    "status": "Supported",
    "status_display": "Supported · as of 2025-09-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-16",
    "col4_md": "Carries x402 payloads over A2A JSON-RPC tasks via `x402.payment.required` and `x402.payment.payload` metadata in Python and TypeScript.",
    "full_detail_md": "Launched alongside Google Cloud's Agent Payments Protocol (AP2) on September 16, 2025, the `google-agentic-commerce/a2a-x402` extension maps x402 v2 payments onto A2A JSON-RPC task metadata (`x402.payment.required`, `x402.payment.payload`, and states `payment-required`, `payment-submitted`, and `payment-completed`) with Python and TypeScript reference libraries.",
    "facets": {
     "settlement_rail": "x402 v2 payment payloads carried over Agent-to-Agent (A2A) JSON-RPC tasks",
     "supported_assets": "On-chain cryptocurrency / stablecoin tokens (e.g., USD Coin)",
     "chains_or_networks": "CAIP-2 on-chain networks (e.g., `eip155:8453`)",
     "headers_or_methods": "A2A task state `input-required` with `x402.payment.required` and `x402.payment.payload` metadata (`payment-required`, `payment-submitted`, `payment-completed`)"
    },
    "telemetry": null,
    "source_url": "https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol",
  "note": "Carries x402 payloads over A2A JSON-RPC tasks via `x402.payment.required` and `x402.payment.payload` metadata in Python and TypeScript."
 },
 {
  "id": "google-adk",
  "org_id": "google",
  "name": "Google Agent Development Kit",
  "url": "https://github.com/aaif/project-proposals/issues/37",
  "type": "sdk",
  "implements": [
   "a2a",
   "a2ui",
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Google ADK",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-04",
    "col4_md": "AAIF proposal lists native `Google ADK` client and server support across local runtimes and `Agent Platform Runtime`.",
    "full_detail_md": "The AAIF Growth Stage proposal (#37, approved by the Governing Board on 2026-08-04) and AAIF announcement blog (2026-08-17) report that Google's Agent Development Kit (`Google ADK`) includes native A2A support across local and Vertex AI Agent Engine / `Agent Platform Runtime` deployments via `RemoteA2aAgent` and `to_a2a()` helpers.",
    "facets": {
     "transport_bindings": "A2A client and server helpers (RemoteA2aAgent, to_a2a())",
     "discovery_artifact": "Agent Card publishing via to_a2a()",
     "protocol_version": "Not specified in AAIF proposal (approved 2026-08-04)",
     "auth_schemes": "Google Cloud / Vertex AI Agent Engine and custom runtime auth",
     "verification_posture": "Listed in AAIF project proposal #37 and AAIF blog (no standalone ADK docs in source bundle)"
    },
    "telemetry": null,
    "source_url": "https://github.com/aaif/project-proposals/issues/37"
   },
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Google ADK",
    "role": "Agent framework",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "ADK integrated the `v0.8` basic catalog; the roadmap still lists ADK as In Progress.",
    "full_detail_md": "The ecosystem page says ADK integrated the A2UI v0.8 basic catalog and that the A2UI Python agent SDK provides an ADK extension for generating A2UI from agents, including the Restaurant Finder sample at samples/agent/adk/restaurant_finder. The roadmap still lists ADK as In Progress and says it is still designing developer ergonomics.",
    "facets": {
     "transport_or_binding": "A2UI messages converted between A2A DataPart metadata and ADK events",
     "component_or_catalog": "A2UI v0.8 basic catalog",
     "spec_version": "v0.8 catalog integration; roadmap status In Progress",
     "sdk_or_renderer": "A2UI Python agent SDK ADK extension; samples/agent/adk/restaurant_finder"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/ecosystem/a2ui-in-the-world/"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Google Agent Development Kit",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · as of 2025-09-26",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-26",
    "col4_md": "ADK covers streaming events, client state, and bi-directional traffic; overview lists ADK and ADK JavaScript.",
    "full_detail_md": "On 2025-09-26 Google wrote that the Agent Development Kit (ADK) now works with AG-UI, and ADK's integration page says AG-UI handles streaming events, client state, and bi-directional communication between agents and users. The overview lists Google ADK as Supported, with Docs and Demos, and lists Google ADK (JavaScript) as Supported, with a Quickstart and Demos.",
    "facets": {
     "transport": "Not named beyond the AG-UI integration (SSE versus protobuf not stated)",
     "event_or_state_model": "Streaming events, client state, and bi-directional agent-user messages",
     "integration_role": "Agent framework (Python ADK and ADK JavaScript)",
     "sdk_or_package": "Google ADK and Google ADK (JavaScript); package id not in the cited pages"
    },
    "telemetry": null,
    "source_url": "https://developers.googleblog.com/en/delight-users-by-combining-adk-agents-with-fancy-frontends-using-ag-ui/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/aaif/project-proposals/issues/37",
  "note": "AAIF proposal lists native `Google ADK` client and server support across local runtimes and `Agent Platform Runtime`."
 },
 {
  "id": "google-agent",
  "org_id": "google",
  "name": "Google-Agent",
  "url": "https://agent.bot.goog",
  "type": "origin",
  "implements": [
   "http-message-signatures",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Google (Google-Agent)",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Publishes five `Ed25519` JWKs and directory-response signature headers; experimentally signs a subset of `Google-Agent` requests.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` for `https://agent.bot.goog`, publishing five `Ed25519` JWKs (`\"alg\":\"EdDSA\"`) and directory-response signature headers (`tag=\"http-message-signatures-directory\"`, signature validation not established by the recorded HTTP observation); Google documents that it experimentally signs only a subset of `Google-Agent` requests.",
    "facets": {
     "signature_or_key_format": "Publishes 5 OKP Ed25519 JWKs (`alg: EdDSA`, `use: sig`) and directory-response signature headers; signature validation not established by the recorded HTTP observation",
     "directory_or_header": "HTTP 200 `application/http-message-signatures-directory+json` at `https://agent.bot.goog`",
     "signing_algorithm": "Ed25519 (`alg=\"ed25519\"`, `tag=\"http-message-signatures-directory\"`)",
     "verification_role": "Bot / Agent signer (experimental; signs a subset of Google-Agent requests)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 5,
     "alg": "EdDSA",
     "use": "sig",
     "kids": [
      "mhxuPw",
      "cYSMkA",
      "bUCe2A",
      "DYiMjA",
      "Ggh50g"
     ],
     "signature_label": "g"
    },
    "source_url": "https://agent.bot.goog/.well-known/http-message-signatures-directory"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Google (Google-Agent)",
    "role": "Bot / Agent signer (Web Bot Auth profile)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Web Bot Auth profile: publishes five `Ed25519` JWKs and experimentally signs a subset of `Google-Agent` requests.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` for `https://agent.bot.goog`, publishing five `OKP` `Ed25519` JWKs (`\"alg\":\"EdDSA\"`, `\"use\":\"sig\"`) and directory-response signature headers (`alg=\"ed25519\"`, `tag=\"http-message-signatures-directory\"`; signature validation not established by the recorded HTTP observation); Google documents that it experimentally signs only a subset of `Google-Agent` requests under the Web Bot Auth profile of RFC 9421.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth (Experimental) profile of RFC 9421 (`https://agent.bot.goog`)",
     "signature_fields": "HTTP 200 `application/http-message-signatures-directory+json` (`Signature`, `Signature-Input`, `Signature-Agent`)",
     "algorithms_or_keys": "Publishes 5 OKP `Ed25519` JWKs (`alg: EdDSA`, `use: sig`) and directory-response signature headers",
     "verification_posture": "Bot / Agent signer (experimental; signs a subset of Google-Agent requests; directory signature validation not established by HTTP observation)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 5,
     "alg": "EdDSA",
     "use": "sig",
     "kids": [
      "mhxuPw",
      "cYSMkA",
      "bUCe2A",
      "DYiMjA",
      "Ggh50g"
     ],
     "signature_label": "g"
    },
    "source_url": "https://agent.bot.goog/.well-known/http-message-signatures-directory"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://agent.bot.goog/.well-known/http-message-signatures-directory",
  "note": "Publishes five `Ed25519` JWKs and directory-response signature headers; experimentally signs a subset of `Google-Agent` requests."
 },
 {
  "id": "google-ai-mode-gemini",
  "org_id": "google",
  "name": "Google",
  "url": "https://blog.google",
  "type": "agent",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Google (AI Mode in Search & Gemini app)",
    "role": "Buying agent / AI surface (Co-author)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-15",
    "col4_md": "U.S. Universal Cart on Search and Gemini; checkout powered by UCP.",
    "full_detail_md": "Universal Cart is rolling out in the U.S. across Google Search and the Gemini app, with checkout powered by UCP (datePublished 2026-10-15). At launch, a UCP integration powers AI Mode in Google Search and the Gemini web and mobile apps.",
    "facets": {
     "commerce_surface": "AI Mode in Google Search and the Gemini web and mobile apps",
     "payment_handlers_or_rail": "Universal Cart checkout powered by UCP",
     "transport_bindings": "Buying-agent surface; merchant profiles are discovered separately",
     "spec_version": "Universal Cart datePublished 2026-10-15; launch FAQ describes the AI Mode and Gemini surfaces"
    },
    "telemetry": null,
    "source_url": "https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/",
  "note": "U.S. Universal Cart on Search and Gemini; checkout powered by UCP."
 },
 {
  "id": "google-antigravity",
  "org_id": "google",
  "name": "Google Antigravity",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "harness",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Google Antigravity",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists Google Antigravity as Supported under Agent Framework - 1st Party.",
    "full_detail_md": "The AG-UI overview lists Google Antigravity as Supported under Agent Framework - 1st Party, with Docs and Demos. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "1st-party agent framework (directory listing)",
     "sdk_or_package": "Not named; Docs and Demos only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "Overview lists Google Antigravity as Supported under Agent Framework - 1st Party."
 },
 {
  "id": "google-chrome-lighthouse",
  "org_id": "google-chrome-lighthouse",
  "name": "Google Chrome Lighthouse (ard-schema)",
  "url": "https://github.com/GoogleChrome/lighthouse/pull/17168",
  "type": "sdk",
  "implements": [
   "ard"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Google Chrome Lighthouse (ard-schema)",
    "role": "CLI / Validator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-31",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-31",
    "col4_md": "`ard-schema` conformance audit in the Lighthouse agentic-browsing category; PR #17168 merged 2026-08-31 and shipped in Lighthouse v13.5.0 on 2026-09; checks the catalog of the site being audited",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/GoogleChrome/lighthouse/pull/17168"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/GoogleChrome/lighthouse/pull/17168",
  "note": "`ard-schema` conformance audit in the Lighthouse agentic-browsing category; PR #17168 merged 2026-08-31 and shipped in Lighthouse v13.5.0 on 2026-09; checks the catalog of the site being audited"
 },
 {
  "id": "google-cloud-agent-identity",
  "org_id": "google",
  "name": "Agent Identity",
  "url": "https://docs.cloud.google.com/iam/docs/agent-identity-overview",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Google Cloud Agent Identity",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Attested SPIFFE ID per agent, used with MCP servers and mapped to the resource URI.",
    "full_detail_md": "Agent Identity provides a strongly attested, cryptographic identity for each agent that is based on the SPIFFE standard. Each agent is assigned a unique identity string, or SPIFFE ID. This identity is strongly attested, tied to the agent's lifecycle, and mapped directly to the resource URI where the agent is hosted. With Agent Identity, an agent can authenticate to MCP servers, cloud resources, endpoints, and other agents. The page was last updated 2026-10-29 UTC.",
    "facets": {
     "svid_or_bundle_format": "A unique SPIFFE ID string per agent. The overview does not name X.509-SVID, JWT-SVID, or WIT-SVID.",
     "api_or_federation_surface": "The agent authenticates to MCP servers, cloud resources, endpoints, and other agents.",
     "attestation_or_trust_domain": "Strongly attested, tied to the agent lifecycle, and mapped to the resource URI where the agent is hosted.",
     "verification_posture": "Google Cloud Agent Identity documentation, last updated 2026-10-29 UTC."
    },
    "telemetry": null,
    "source_url": "https://docs.cloud.google.com/iam/docs/agent-identity-overview"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.cloud.google.com/iam/docs/agent-identity-overview",
  "note": "Attested SPIFFE ID per agent, used with MCP servers and mapped to the resource URI."
 },
 {
  "id": "google-cloud-knowledge-catalog",
  "org_id": "google",
  "name": "Google Cloud Knowledge Catalog",
  "url": "https://cloud.google.com/blog/products/data-analytics/knowledge-catalog-self-learning-context-enrichment-for-ai-agents",
  "type": "origin",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Google Cloud Knowledge Catalog",
    "role": "Context catalog",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-23",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-23",
    "col4_md": "Imports an OKF bundle as a context set and exports it back out as OKF.",
    "full_detail_md": "The 2026-06-12 launch post says Google Cloud's Knowledge Catalog can ingest Open Knowledge Format and serve it to Google Cloud agents. The context-enrichment post's datePublished is 2026-10-22 and its page byline is October 23, 2026; that post says a context set can be imported from an OKF bundle and exported back out as OKF.",
    "facets": {
     "artifact_or_endpoint": "Knowledge Catalog context-set import and OKF export",
     "content_type_or_schema": "OKF bundle imported as a context set and exported back out as OKF",
     "discovery_mechanism": "Google Cloud blog documentation of catalog ingest and export",
     "version_or_posture": "Vendor-documented catalog support; datePublished 2026-10-22 is distinct from the October 23, 2026 byline"
    },
    "telemetry": null,
    "source_url": "https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing",
  "note": "Imports an OKF bundle as a context set and exports it back out as OKF."
 },
 {
  "id": "google-cloud-managed-workload-identities",
  "org_id": "google",
  "name": "Managed Workload Identities",
  "url": "https://docs.cloud.google.com/iam/docs/managed-workload-identity",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Google Cloud Managed Workload Identities",
    "role": "Identity issuer / CA",
    "status": "Partial",
    "status_display": "Partial · as of 2026-11-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Issues SPIFFE IDs for mTLS across Compute Engine (`.workload.id.goog`), GKE (`.svc.id.goog`, Preview), and agents (`.system.id.goog`).",
    "full_detail_md": "Google Cloud's Managed Workload Identities documentation (last updated 2026-11-04 UTC) states that managed workload identities are based on SPIFFE for mutual TLS (mTLS) authentication: Managed workload identities for Compute Engine (using `.workload.id.goog` SPIFFE IDs) and Agent identity workloads (using `.system.id.goog` SPIFFE IDs) are available, while Managed workload identities for GKE (`.svc.id.goog` SPIFFE IDs) is marked Preview.",
    "facets": {
     "svid_or_bundle_format": "SPIFFE IDs for mTLS. Compute Engine uses .workload.id.goog. GKE uses .svc.id.goog. Agent identities use spiffe://agents.global.org-ORGANIZATION_ID.system.id.goog/resources/aiplatform/projects/PROJECT_NUMBER/locations/LOCATION/reasoningEngines/AGENT_NAME.",
     "api_or_federation_surface": "Mutual TLS (mTLS) authentication between workloads.",
     "attestation_or_trust_domain": "Attested identities bound to GKE and Compute Engine workloads through identity pools and attestation policies.",
     "verification_posture": "Google Cloud documentation last updated 2026-11-04 UTC. Managed workload identities for GKE are marked Preview, so support is partial."
    },
    "telemetry": null,
    "source_url": "https://docs.cloud.google.com/iam/docs/managed-workload-identity"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://docs.cloud.google.com/iam/docs/managed-workload-identity",
  "note": "Issues SPIFFE IDs for mTLS across Compute Engine (`.workload.id.goog`), GKE (`.svc.id.goog`, Preview), and agents (`.system.id.goog`)."
 },
 {
  "id": "google-crawlers",
  "org_id": "google",
  "name": "Google crawlers",
  "url": "https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Google",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`Google-Extended` (control-only token) governs Gemini training and grounding; `Google-CloudVertexBot` governs site-owner Vertex AI Agent crawls.",
    "full_detail_md": "`Google-Extended` is a robots.txt user-agent token for whether content Google crawls may be used for training future Gemini models and for grounding. It has no separate HTTP request user agent string. `Google-CloudVertexBot` affects crawls requested by site owners for building Vertex AI Agents and has no effect on Google Search.",
    "facets": {
     "user_agent_token": [
      "Google-Extended",
      "Google-CloudVertexBot"
     ],
     "operator_purpose": "Google-Extended: Gemini training and grounding control token (no separate HTTP UA); Google-CloudVertexBot: site-owner Vertex AI Agent crawls",
     "ip_verification_url": "https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers",
     "robots_directives_honored": "robots.txt user-agent token matching without affecting Google Search"
    },
    "telemetry": null,
    "source_url": "https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers",
  "note": "`Google-Extended` (control-only token) governs Gemini training and grounding; `Google-CloudVertexBot` governs site-owner Vertex AI Agent crawls."
 },
 {
  "id": "google-jules",
  "org_id": "google",
  "name": "Jules",
  "url": "https://jules.google/docs/changelog/2025-06-20/",
  "type": "harness",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Google Jules",
    "role": "Coding agent",
    "status": "Supported",
    "status_display": "Supported · as of 2025-06-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-06-20",
    "col4_md": "Reads context from `AGENTS.md` automatically when present in a repository (shipped 2025-06-20).",
    "full_detail_md": "Added native `AGENTS.md` repository context ingestion in its 20 June 2025 agent upgrade and is named on `agents.md` as one of the collaborating coding agents that shaped the format.",
    "facets": {
     "discovery_behavior": "Automatically reads repository AGENTS.md for project context",
     "hierarchy_precedence": "Repository AGENTS.md lookup (nested precedence rules not detailed in changelog)",
     "fallback_files": "None stated in changelog",
     "verification_posture": "Documented in Google Jules 2025-06-20 changelog and agents.md specification"
    },
    "telemetry": null,
    "source_url": "https://jules.google/docs/changelog/2025-06-20/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://jules.google/docs/changelog/2025-06-20/",
  "note": "Reads context from `AGENTS.md` automatically when present in a repository (shipped 2025-06-20)."
 },
 {
  "id": "google-opal",
  "org_id": "google",
  "name": "Google Opal",
  "url": "https://opal.google/",
  "type": "harness",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Google Opal",
    "role": "Host app",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Ecosystem page says Opal uses A2UI for mini-apps; the Opal site labels the product Experiment.",
    "full_detail_md": "The ecosystem page says the Opal team uses A2UI to power the dynamic, generative UI system for Opal's AI mini-apps. The Opal site labels the product Experiment and says Opal is graduating out of Labs on November 17, 2026, as custom workflows transition to skills in Gemini, and that page does not contain the string A2UI.",
    "facets": {
     "transport_or_binding": "Host app; the ecosystem page attributes mini-app UI to A2UI",
     "component_or_catalog": "Dynamic generative UI for AI mini-apps",
     "spec_version": "Opal site says Experiment and graduates on November 17, 2026; that page does not name A2UI",
     "sdk_or_renderer": "Google Opal host"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/ecosystem/a2ui-in-the-world/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://a2ui.org/ecosystem/a2ui-in-the-world/",
  "note": "Ecosystem page says Opal uses A2UI for mini-apps; the Opal site labels the product Experiment."
 },
 {
  "id": "google-pay",
  "org_id": "google",
  "name": "Google Pay",
  "url": "https://pay.google.com",
  "type": "authority",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Google Pay",
    "role": "Wallet",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-15",
    "col4_md": "`com.google.pay` on Gemini and AI Mode; checkout in Universal Cart.",
    "full_detail_md": "The handler is identified as com.google.pay inside payment_handlers, and the docs describe Google Pay as the credential provider on Google AI surfaces such as Gemini and AI Mode. Universal Cart (datePublished 2026-10-15) says shoppers can check out with Google Pay in the cart.",
    "facets": {
     "commerce_surface": "Credential provider on Gemini and AI Mode",
     "payment_handlers_or_rail": "com.google.pay inside payment_handlers; Google Pay checkout in Universal Cart",
     "transport_bindings": "Handler declared on merchant profiles; cart checkout is the Google surface",
     "spec_version": "Handler name com.google.pay; Universal Cart datePublished 2026-10-15 (article date, not the handler spec version)"
    },
    "telemetry": null,
    "source_url": "https://developers.google.com/pay/api/universal-commerce-protocol/google-pay-payment-handler"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developers.google.com/pay/api/universal-commerce-protocol/google-pay-payment-handler",
  "note": "`com.google.pay` on Gemini and AI Mode; checkout in Universal Cart."
 },
 {
  "id": "goose",
  "org_id": "block",
  "name": "goose",
  "url": "https://goose-docs.ai/docs/gdk/acp/",
  "type": "harness",
  "implements": [
   "agent-client-protocol",
   "agents-md",
   "anthropic-agent-skills-format",
   "mcp-apps",
   "oauth-cimd"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Block goose",
    "role": "Native CLI coding agent & desktop client",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Native `goose acp` subprocess over `stdio` and `goose serve` daemon at `http://127.0.0.1:3284/acp`.",
    "full_detail_md": "Block's `goose` implements ACP natively: clients launch `goose acp` as a subprocess whose `stdin` and `stdout` carry ACP messages, or connect to `goose serve` over HTTP and WebSocket at `http://127.0.0.1:3284/acp` (which is also how `goose Desktop` talks to its backend).",
    "facets": {
     "role_in_acp": "Agent server and desktop client",
     "integration_mode": "Native CLI subprocess (goose acp) and HTTP/WebSocket server (goose serve)",
     "transport": "stdio, HTTP, and WebSocket (http://127.0.0.1:3284/acp)",
     "verification_posture": "First-party GDK documentation & official ACP Registry listing",
     "sdk_or_package": "goose CLI (goose acp / goose serve)"
    },
    "telemetry": null,
    "source_url": "https://goose-docs.ai/docs/gdk/acp/"
   },
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "goose",
    "role": "Open-source agent harness",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Loads `SKILL.md` subdirectories from `~/.agents/skills/` and compatibility paths `.goose/skills/`, `.claude/skills/`, and `~/.claude/skills/`.",
    "full_detail_md": "Block's open-source `goose` agent loads `SKILL.md` files with required `name` and `description` YAML frontmatter from named subdirectories such as `~/.agents/skills/code-review/SKILL.md`, and also scans compatibility directories `.goose/skills/`, `.claude/skills/`, and `~/.claude/skills/`.",
    "facets": {
     "transport_or_packaging": "Local skill directories (~/.agents/skills/, .goose/skills/, .claude/skills/, ~/.claude/skills/) and plugins",
     "manifest_or_entry": "SKILL.md with required YAML name and description frontmatter",
     "execution_or_sandbox": "Progressive disclosure of skill instructions and supporting files in local agent sessions",
     "verification_posture": "First-party goose documentation checked 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://goose-docs.ai/docs/guides/context-engineering/using-skills/"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Block (goose)",
    "role": "Coding agent / CLI",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Named in the compatible coding-agent roster on `agents.md`.",
    "full_detail_md": "Listed on `agents.md` under compatible AI coding agents and tools (`goose` by Block); runtime `AGENTS.md` discovery and hierarchy precedence mechanics inside `goose` are not independently verified in the cited documentation snapshots.",
    "facets": {
     "discovery_behavior": "Listed on agents.md — implementation behavior not independently verified",
     "hierarchy_precedence": "Not independently verified in cited documentation",
     "fallback_files": "Not independently verified in cited documentation",
     "verification_posture": "Listed on agents.md — implementation behavior not independently verified"
    },
    "telemetry": null,
    "source_url": "https://agents.md/"
   },
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "goose",
    "role": "AI host",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-01-26",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-26",
    "col4_md": "Tutorial calls MCP Apps experimental and draft-based, not a finished release.",
    "full_detail_md": "goose's tutorial says MCP Apps render inside the goose chat and that support is experimental and based on a draft specification, so this row stays Experimental rather than Supported. The 2026-01-26 launch post lists Goose as available that day and calls goose the reference implementation for MCP, which is a separate claim from the tutorial's draft basis.",
    "facets": {
     "transport_or_channel": "MCP Apps render inside the goose chat interface",
     "ui_resource_or_primitive": "Interactive UI from an MCP server, rather than text alone",
     "sandbox_or_security": "Tutorial does not publish a CSP; it marks support experimental and draft-based",
     "sdk_or_version": "Tutorial: experimental, based on a draft specification; 2026-01-26 launch post lists Goose as available"
    },
    "telemetry": null,
    "source_url": "https://goose-docs.ai/docs/tutorials/building-mcp-apps/"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Block, goose",
    "role": "OAuth client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `client_name` goose; PKCE `S256`.",
    "full_detail_md": "`https://goose-docs.ai/oauth/client-metadata.json` returned HTTP 200 `application/json`, with `client_id` equal to that URL, `client_name` goose, and `token_endpoint_auth_method` `none`. `redirect_uris` are `http://127.0.0.1/oauth_callback` and `http://[::1]/oauth_callback`, and `code_challenge_methods_supported` is `S256`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "Published client metadata JSON; client_name goose; client_id equals the document URL",
     "auth_method_or_pkce": "token_endpoint_auth_method none; code_challenge_methods_supported S256; grant_types authorization_code and refresh_token",
     "uri_or_ssrf_rules": "redirect_uris are http://127.0.0.1/oauth_callback and http://[::1]/oauth_callback; client_id is https://goose-docs.ai/oauth/client-metadata.json",
     "draft_or_spec_version": "Live client metadata JSON checked 2026-10-30; the document does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_name": "goose",
     "token_endpoint_auth_method": "none"
    },
    "source_url": "https://goose-docs.ai/oauth/client-metadata.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://goose-docs.ai/docs/gdk/acp/",
  "note": "Native `goose acp` subprocess over `stdio` and `goose serve` daemon at `http://127.0.0.1:3284/acp`."
 },
 {
  "id": "greymatter",
  "org_id": "greymatter",
  "name": "Greymatter.io",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Greymatter.io",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Commercial works-with listing marks all four columns, including Workload API.",
    "full_detail_md": "The SPIFFE overview's commercial works-with table lists Greymatter.io with a support mark in each of its four columns: X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. Those columns mean X.509 SVID-based authentication, JWT SVID-based authentication, federated SPIFFE authentication based on trust domain name, and attaching to the SPIFFE Workload API.",
    "facets": {
     "svid_or_bundle_format": "Marks for both X.509 SVID-based authentication and JWT SVID-based authentication.",
     "api_or_federation_surface": "SPIFFE Authentication and the Workload API are both marked.",
     "attestation_or_trust_domain": "Federated SPIFFE authentication based on trust domain name is marked. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Commercial works-with listing marks all four columns, including Workload API."
 },
 {
  "id": "guildskills-registry",
  "org_id": "guildskills",
  "name": "GuildSkills",
  "url": "https://guildskills.com/",
  "type": "sdk",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "GuildSkills",
    "role": "Cross-agent SKILL.md registry",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Vendor-declared registry counter of `195,000+` SKILL.md files and `30+` clients (self-reported, not deduplicated or security-vetted).",
    "full_detail_md": "GuildSkills describes itself as the registry for the open Agent Skills standard and names Hermes Agent, Cursor, OpenAI Codex, Gemini CLI, OpenCode, Goose, Letta, Roo Code, and Claude Code among 30+ clients.",
    "facets": {
     "transport_or_packaging": "Cross-agent catalog of SKILL.md files",
     "manifest_or_entry": "195,000+ SKILL.md files",
     "execution_or_sandbox": "Catalog and install layer; skills stay with their authors",
     "verification_posture": "Homepage claim checked 2026-11-06"
    },
    "telemetry": null,
    "source_url": "https://guildskills.com/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://guildskills.com/",
  "note": "Vendor-declared registry counter of `195,000+` SKILL.md files and `30+` clients (self-reported, not deduplicated or security-vetted)."
 },
 {
  "id": "hachette-fr",
  "org_id": "hachette-livre",
  "name": "Hachette Livre",
  "url": "https://www.hachette.fr/",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Hachette Livre",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Homepage HTML (HTTP 200, `text/html`, checked 2026-10-30) sets meta `tdm-reservation` to `1`. This fetch does not include a tdm-policy property. The adopters list says Hachette Livre has implemented the protocol on most websites of the group's publishing houses.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/html",
     "attachment": "html-meta",
     "tdm_reservation": "1"
    },
    "source_url": "https://www.hachette.fr/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.hachette.fr/",
  "note": "Homepage HTML (HTTP 200, `text/html`, checked 2026-10-30) sets meta `tdm-reservation` to `1`. This fetch does not include a tdm-policy property. The adopters list says Hachette Livre has implemented the protocol on most websites of the group's publishing houses."
 },
 {
  "id": "hashicorp-vault-1-21",
  "org_id": "hashicorp",
  "name": "Vault 1.21",
  "url": "https://developer.hashicorp.com/vault/docs/auth/spiffe",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "HashiCorp Vault 1.21",
    "role": "Relying server / Gateway",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-28",
    "col4_md": "Vault Enterprise `spiffe` auth takes X.509 or JWT SVIDs and can issue X509-SVIDs.",
    "full_detail_md": "HashiCorp's official Vault Enterprise documentation states that the `spiffe` auth method lets workloads authenticate to Vault using either X.509 or JWT-based SPIFFE Verifiable Identity Documents (SVIDs) validated against a configured trust bundle across bare metal, VMs, or multi-cloud Kubernetes. InfoQ reported on Mar 28, 2026 that Vault 1.21 introduced native SPIFFE authentication and X509-SVID issuance.",
    "facets": {
     "svid_or_bundle_format": "Validates X.509 certificates or JWTs against a configured trust bundle, and can issue X509-SVIDs.",
     "api_or_federation_surface": "Vault Enterprise spiffe auth method, introduced in Vault 1.21.",
     "attestation_or_trust_domain": "The same trust-bundle check applies on bare metal, VMs, or multi-cloud Kubernetes.",
     "verification_posture": "HashiCorp Vault Enterprise documentation, plus an InfoQ report dated March 28, 2026. Vault is both a consumer and an issuer of SPIFFE identities."
    },
    "telemetry": null,
    "source_url": "https://developer.hashicorp.com/vault/docs/auth/spiffe"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://developer.hashicorp.com/vault/docs/auth/spiffe",
  "note": "Vault Enterprise `spiffe` auth takes X.509 or JWT SVIDs and can issue X509-SVIDs."
 },
 {
  "id": "hcaptcha",
  "org_id": "hcaptcha",
  "name": "hCaptcha Enterprise",
  "url": "https://www.hcaptcha.com/blog/web-bot-auth",
  "type": "authority",
  "implements": [
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "hCaptcha",
    "role": "Relying server",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-02",
    "col4_md": "hCaptcha Enterprise validates Web Bot Auth (WBA) cryptographic signatures to identify partner AI agent platform traffic.",
    "full_detail_md": "hCaptcha Enterprise supports Web Bot Auth (WBA), allowing partner agent platforms to cryptographically authenticate outbound HTTP traffic to relying websites (published October 2, 2026).",
    "facets": {
     "signature_or_key_format": "Web Bot Auth (WBA) cryptographic traffic identification",
     "directory_or_header": "Web Bot Auth HTTP request signatures",
     "signing_algorithm": "Web Bot Auth cryptographic signatures",
     "verification_role": "Relying server (hCaptcha Enterprise identifies partner agent platform traffic)"
    },
    "telemetry": null,
    "source_url": "https://www.hcaptcha.com/blog/web-bot-auth"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.hcaptcha.com/blog/web-bot-auth",
  "note": "hCaptcha Enterprise validates Web Bot Auth (WBA) cryptographic signatures to identify partner AI agent platform traffic."
 },
 {
  "id": "headlessdomains",
  "org_id": "headlessdomains",
  "name": "HeadlessDomains",
  "url": "https://headlessdomains.com/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "HeadlessDomains",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "https://headlessdomains.com/auth.md says HeadlessDomains supports agent-native authentication for autonomous domain registration, renewal, profile updates, and DNS-linked identity operations. Fetched status 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://headlessdomains.com/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://headlessdomains.com/auth.md",
  "note": "https://headlessdomains.com/auth.md says HeadlessDomains supports agent-native authentication for autonomous domain registration, renewal, profile updates, and DNS-linked identity operations. Fetched status 200 on 2026-10-29."
 },
 {
  "id": "helpagent-club-registrants",
  "org_id": "helpagent-club-registrants",
  "name": "helpagent.club registrants",
  "url": "https://transparency.ans.godaddy.com/tile/entries/1750",
  "type": "agent",
  "implements": [
   "ans"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "ans",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "helpagent.club registrants",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-28",
    "col4_md": "Log tile 1750 holds 256 registrations dated 2026-10-28, including Vetus Carta Rare Maps Customer Support Agent. Sample badge `_ans-badge.support-e4c874ed-305c-4f6e-bc10-579d7684160d.helpagent.club` is `v=ans-badge1; version=v1.0.0; url=https://transparency.ans.godaddy.com/v1/agents/a9ed929d-537b-421e-81ee-1e339153e83f`. Matching `_ans` TXT is `v=ans1; version=v1.0.0; p=a2a; mode=direct`. Twelve sampled hosts had the badge and `_ans` TXT on both resolvers, without DNSSEC.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://transparency.ans.godaddy.com/tile/entries/1750"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://transparency.ans.godaddy.com/tile/entries/1750",
  "note": "Log tile 1750 holds 256 registrations dated 2026-10-28, including Vetus Carta Rare Maps Customer Support Agent. Sample badge `_ans-badge.support-e4c874ed-305c-4f6e-bc10-579d7684160d.helpagent.club` is `v=ans-badge1; version=v1.0.0; url=https://transparency.ans.godaddy.com/v1/agents/a9ed929d-537b-421e-81ee-1e339153e83f`. Matching `_ans` TXT is `v=ans1; version=v1.0.0; p=a2a; mode=direct`. Twelve sa"
 },
 {
  "id": "here-now",
  "org_id": "here-now",
  "name": "here.now",
  "url": "https://here.now/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "here.now",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://here.now/auth.md documents email-code API key creation: POST /api/auth/agent/request-code with header X-HereNow-Client. The same file says here.now does not support agent-verified ID-JAG registration, OAuth client registration, MCP auth, or a third-party identity-provider assertion.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://here.now/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://here.now/auth.md",
  "note": "https://here.now/auth.md documents email-code API key creation: POST /api/auth/agent/request-code with header X-HereNow-Client. The same file says here.now does not support agent-verified ID-JAG registration, OAuth client registration, MCP auth, or a third-party identity-provider assertion."
 },
 {
  "id": "honeydew",
  "org_id": "honeydew",
  "name": "Honeydew",
  "url": "https://honeydew.ai/docs/integration/apache-ossie-osi",
  "type": "origin",
  "implements": [
   "osi"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "osi",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Honeydew",
    "role": "Data platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Honeydew ships a bidirectional converter between Apache Ossie YAML and the Honeydew workspace format. The converter tracks the current draft and can change as the spec stabilizes. Docs returned status 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://honeydew.ai/docs/integration/apache-ossie-osi"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://honeydew.ai/docs/integration/apache-ossie-osi",
  "note": "Honeydew ships a bidirectional converter between Apache Ossie YAML and the Honeydew workspace format. The converter tracks the current draft and can change as the spec stabilizes. Docs returned status 200 on 2026-10-29."
 },
 {
  "id": "hugging-face",
  "org_id": "huggingface",
  "name": "Hugging Face",
  "url": "https://huggingface.co/.well-known/ai-catalog.json",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file",
   "api-catalog-rfc9727",
   "mcp-server-cards"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Hugging Face",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Level 2 catalog advertising the Discover registry (`urn:air:huggingface.co:registry:discover`, type `application/ai-registry+json`) and the Hub MCP Server Card.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://huggingface.co/.well-known/ai-catalog.json"
   },
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Hugging Face",
    "role": "ML hub API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Profiled `application/linkset+json` with `item` and `rel=\"api-catalog\"`.",
    "full_detail_md": "On 2026-11-04, `https://huggingface.co/.well-known/api-catalog` returned HTTP 200 (`content-length: 254`) as `application/linkset+json; charset=utf-8` with profile `https://www.rfc-editor.org/info/rfc9727` and `Link: </.well-known/api-catalog>; rel=\"api-catalog\"`. The linkset lists `item` href `https://huggingface.co` and `service-desc` `https://huggingface.co/.well-known/openapi.json` (`application/json`).",
    "facets": {
     "well_known_endpoint": "https://huggingface.co/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; charset=utf-8; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_relations": "item (https://huggingface.co); service-desc (https://huggingface.co/.well-known/openapi.json, application/json)",
     "http_or_link_header": "HTTP 200; Link: </.well-known/api-catalog>; rel=\"api-catalog\""
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; charset=utf-8; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_header_rel_api_catalog": true,
     "has_item_array": true
    },
    "source_url": "https://huggingface.co/.well-known/api-catalog"
   },
   {
    "protocol_id": "mcp-server-cards",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Hugging Face (Hugging Face MCP Server)",
    "role": "Server Card publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GET https://huggingface.co/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://huggingface.co/mcp, card name huggingface.co/mcp. https://huggingface.co/.well-known/ai-catalog.json (status 200, application/ai-catalog+json) links to this card. The hf-mcp-server README says the public Streamable HTTP deployment serves the card at /mcp/server-card.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://huggingface.co/mcp/server-card"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://huggingface.co/.well-known/ai-catalog.json",
  "note": "Level 2 catalog advertising the Discover registry (`urn:air:huggingface.co:registry:discover`, type `application/ai-registry+json`) and the Hub MCP Server Card."
 },
 {
  "id": "hugging-face-discover-tool",
  "org_id": "hugging-face-discover-tool",
  "name": "Hugging Face Discover Tool",
  "url": "https://huggingface.co/blog/agentic-resource-discovery-launch",
  "type": "sdk",
  "implements": [
   "ard"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Hugging Face Discover Tool",
    "role": "Resolver / Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Hugging Face's reference implementation of ARD; search over thousands of Skills, ML applications, and MCP servers on Hugging Face and across other ARD discovery services",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://huggingface.co/blog/agentic-resource-discovery-launch"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://huggingface.co/blog/agentic-resource-discovery-launch",
  "note": "Hugging Face's reference implementation of ARD; search over thousands of Skills, ML applications, and MCP servers on Hugging Face and across other ARD discovery services"
 },
 {
  "id": "hugging-face-hf-discover",
  "org_id": "hugging-face-hf-discover",
  "name": "Hugging Face, hf-discover",
  "url": "https://github.com/huggingface/hf-discover",
  "type": "authority",
  "implements": [
   "mcp-server-cards"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-server-cards",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Hugging Face, hf-discover",
    "role": "Server Card publisher",
    "status": "Supported",
    "status_display": "Supported · as of 2026-06-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-30",
    "col4_md": "The hf-discover README, last changed 2026-06-30, says a request for application/mcp-server-card+json adds filter=mcp-server to the downstream Hub search and returns MCP server card catalog entries that point at this adapter's generated server.json route.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/huggingface/hf-discover"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/huggingface/hf-discover",
  "note": "The hf-discover README, last changed 2026-06-30, says a request for application/mcp-server-card+json adds filter=mcp-server to the downstream Hub search and returns MCP server card catalog entries that point at this adapter's generated server.json route."
 },
 {
  "id": "huggingface-inference-providers",
  "org_id": "huggingface",
  "name": "Hugging Face Inference Providers",
  "url": "https://evalstate-openresponses.hf.space/v1/responses",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Hugging Face Inference Providers",
    "role": "Inference router",
    "status": "Supported (preview)",
    "status_display": "Supported (preview) · as of 2026-01-15",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-15",
    "col4_md": "Early-access Space `https://evalstate-openresponses.hf.space/v1/responses` shows `response.reasoning.delta`. Ben Burtenshaw and Shaun Smith (HuggingFace) are initial TSC voting members.",
    "full_detail_md": "Hugging Face's January 15, 2026 post says Open Responses can be tried with Hugging Face Inference Providers today, and that an early access version is available on Hugging Face Spaces. The same post curls https://evalstate-openresponses.hf.space/v1/responses and shows a response.reasoning.delta event, and AWS lists Hugging Face among the providers serving the format. Ben Burtenshaw and Shaun Smith (HuggingFace) are initial TSC voting members.",
    "facets": {
     "endpoint_or_route": "https://evalstate-openresponses.hf.space/v1/responses",
     "streaming_or_items": "response.reasoning.delta event in the early-access curl",
     "tool_or_state_model": "Open Responses API schema; the curl sends OpenResponses-Version: latest",
     "sdk_or_version": "Early access on Hugging Face Spaces; post published January 15, 2026"
    },
    "telemetry": null,
    "source_url": "https://huggingface.co/blog/open-responses"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://huggingface.co/blog/open-responses",
  "note": "Early-access Space `https://evalstate-openresponses.hf.space/v1/responses` shows `response.reasoning.delta`. Ben Burtenshaw and Shaun Smith (HuggingFace) are initial TSC voting members."
 },
 {
  "id": "huggingface-mcp",
  "org_id": "huggingface",
  "name": "Hugging Face MCP Server",
  "url": "https://huggingface.co/mcp",
  "type": "origin",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Hugging Face",
    "role": "Remote MCP server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Streamable HTTP at `https://huggingface.co/mcp` returning `2026-07-28`, `tools`, `resources`, and `io.modelcontextprotocol/skills`.",
    "full_detail_md": "Hugging Face operates a public Streamable HTTP MCP server at `https://huggingface.co/mcp` (`huggingface.co/mcp` v`0.4.31`) advertising protocol revision `2026-07-28`, `tools`, `resources`, and the `io.modelcontextprotocol/skills` extension (`directoryRead: true`) for searching Hub models, datasets, Spaces, and papers.",
    "facets": {
     "transport": "Streamable HTTP",
     "auth_or_oauth": "Bearer token (HF_TOKEN) or anonymous public access",
     "primitives": "tools, resources, io.modelcontextprotocol/skills",
     "sdk_or_package": "huggingface.co/mcp v0.4.31"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "spec_version": "2026-07-28",
     "server_name": "huggingface.co/mcp",
     "server_version": "0.4.31"
    },
    "source_url": "https://huggingface.co/mcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://huggingface.co/mcp",
  "note": "Streamable HTTP at `https://huggingface.co/mcp` returning `2026-07-28`, `tools`, `resources`, and `io.modelcontextprotocol/skills`."
 },
 {
  "id": "human-security",
  "org_id": "human-security",
  "name": "HUMAN Security",
  "url": "https://www.humansecurity.com/learn/blog/human-verified-ai-agent-open-source/",
  "type": "authority",
  "implements": [
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "HUMAN Security",
    "role": "Relying server",
    "status": "Partial",
    "status_display": "Partial · as of 2025-07-21",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-07-21",
    "col4_md": "Open-source HUMAN Verified AI Agent gateway verifies RFC 9421 request signatures against a public key registry.",
    "full_detail_md": "Provides an open-source reference verifier gateway (`HUMAN Verified AI Agent`, published July 21, 2025) that checks incoming HTTP Message Signatures (RFC 9421) against a public key registry so relying web services can cryptographically validate which agent sent a request.",
    "facets": {
     "signature_or_key_format": "HTTP Message Signatures (RFC 9421)",
     "directory_or_header": "Public key registry checked by the open-source gateway service",
     "signing_algorithm": "HTTP Message Signatures (RFC 9421)",
     "verification_role": "Relying server (open-source reference verifier gateway)"
    },
    "telemetry": null,
    "source_url": "https://www.humansecurity.com/learn/blog/human-verified-ai-agent-open-source/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.humansecurity.com/learn/blog/human-verified-ai-agent-open-source/",
  "note": "Open-source HUMAN Verified AI Agent gateway verifies RFC 9421 request signatures against a public key registry."
 },
 {
  "id": "human-verified-ai-agents",
  "org_id": "human-security",
  "name": "HUMAN Verified AI Agents",
  "url": "https://github.com/HumanSecurity/human-verified-ai-agent",
  "type": "sdk",
  "implements": [
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "HUMAN Verified AI Agents",
    "role": "Reference client",
    "status": "Reference implementation (pre-WG draft)",
    "status_display": "Reference implementation (pre-WG draft) · as of 2026-10-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Open-source Python reference client in Appendix F.1 targeting `draft-meunier-web-bot-auth-architecture-03`; `draft-ietf-webbotauth-httpsig-protocol-01` conformance not established.",
    "full_detail_md": "Listed in Appendix F.1 of `draft-ietf-webbotauth-httpsig-protocol-01` at `https://github.com/HumanSecurity/human-verified-ai-agent` as an open-source Python client grouped under `draft-meunier-web-bot-auth-architecture-03`, providing cryptographically authenticated agent communication using RFC 9421 HTTP Message Signatures (announced July 21, 2025).",
    "facets": {
     "signature_or_key_format": "HTTP Message Signatures (RFC 9421) targeting `draft-meunier-web-bot-auth-architecture-03`",
     "directory_or_header": "Public key registry and RFC 9421 signature headers",
     "signing_algorithm": "HTTP Message Signatures (RFC 9421)",
     "verification_role": "Reference client (open-source Python client listed in IETF draft Appendix F.1)"
    },
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-ietf-webbotauth-httpsig-protocol-01.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ietf.org/archive/id/draft-ietf-webbotauth-httpsig-protocol-01.txt",
  "note": "Open-source Python reference client in Appendix F.1 targeting `draft-meunier-web-bot-auth-architecture-03`; `draft-ietf-webbotauth-httpsig-protocol-01` conformance not established."
 },
 {
  "id": "iab-artf-go-reference",
  "org_id": "iabtechlab",
  "name": "IAB Tech Lab Go reference server",
  "url": "https://github.com/IABTechLab/agentic-real-time-framework",
  "type": "sdk",
  "implements": [
   "artf"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "artf",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "IAB Tech Lab Go reference server",
    "role": "Reference server",
    "status": "Development",
    "status_display": "Development · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "Go reference server for ARTF v1.0. gRPC RTBExtensionPoint.GetMutations on port 50051. MCP tool extend_rtb on port 50052, or /mcp on port 8081 when the web UI and MCP are both enabled. Kubernetes liveness and readiness probes on port 8080. MCP library pin github.com/mark3labs/mcp-go 0.43.1.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/IABTechLab/agentic-real-time-framework/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/IABTechLab/agentic-real-time-framework/main/README.md",
  "note": "Go reference server for ARTF v1.0. gRPC RTBExtensionPoint.GetMutations on port 50051. MCP tool extend_rtb on port 50052, or /mcp on port 8081 when the web UI and MCP are both enabled. Kubernetes liveness and readiness probes on port 8080. MCP library pin github.com/mark3labs/mcp-go 0.43.1."
 },
 {
  "id": "iab-artf-protobuf-codegen",
  "org_id": "iabtechlab",
  "name": "IAB Tech Lab protobuf codegen",
  "url": "https://github.com/IABTechLab/agentic-real-time-framework",
  "type": "sdk",
  "implements": [
   "artf"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "artf",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "IAB Tech Lab protobuf codegen",
    "role": "SDK",
    "status": "Development",
    "status_display": "Development · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "make generate fetches the OpenRTB 2.6 proto and emits Go by default. LANG or LANGS selects Java, C++, and Rust bindings.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/IABTechLab/agentic-real-time-framework/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/IABTechLab/agentic-real-time-framework/main/README.md",
  "note": "make generate fetches the OpenRTB 2.6 proto and emits Go by default. LANG or LANGS selects Java, C++, and Rust bindings."
 },
 {
  "id": "iab-artf-rust-reference",
  "org_id": "iabtechlab",
  "name": "IAB Tech Lab Rust reference implementation",
  "url": "https://iabtechlab.com/a-milestone-for-the-agentic-advertising-ecosystem/",
  "type": "sdk",
  "implements": [
   "artf"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "artf",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "IAB Tech Lab Rust reference implementation",
    "role": "Reference server",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-08-12",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-08-12",
    "col4_md": "The 2026-08-12 milestone lists a Rust reference implementation with the orchestration layer that allows one ARTF node to call other ARTF nodes and merge their responses to a single bid request mutation.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://iabtechlab.com/a-milestone-for-the-agentic-advertising-ecosystem/"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://iabtechlab.com/a-milestone-for-the-agentic-advertising-ecosystem/",
  "note": "The 2026-08-12 milestone lists a Rust reference implementation with the orchestration layer that allows one ARTF node to call other ARTF nodes and merge their responses to a single bid request mutation."
 },
 {
  "id": "ibm-api-connect-cms-portal",
  "org_id": "ibm",
  "name": "IBM API Connect CMS Portal",
  "url": "https://community.ibm.com/community/user/blogs/xuantong-liu/2025/10/13/introducing-api-catalog-support-in-ibm-api-connect",
  "type": "origin",
  "implements": [
   "api-catalog-rfc9727"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "IBM API Connect CMS Portal",
    "role": "API management developer portal",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-16",
    "col4_md": "CMS Portal `v12.1.0.0` generates `linkset.json` at `{PortalURL}/.well-known/api-catalog` for public APIs.",
    "full_detail_md": "IBM API Connect CMS Portal `v12.1.0.0` (article dated 2025-12-16) adds a Drupal `api_catalog` module that generates `linkset.json` at `{PortalURL}/.well-known/api-catalog` for published APIs with public visibility, disabled until a portal administrator enables it. The sample linkset sets profile `https://www.rfc-editor.org/rfc/rfc9727` and lists each API with an `item` href.",
    "facets": {
     "well_known_endpoint": "{PortalURL}/.well-known/api-catalog",
     "content_type_or_profile": "linkset.json; sample profile https://www.rfc-editor.org/rfc/rfc9727",
     "link_relations": "item href per public API (sample type application/openapi+json)",
     "http_or_link_header": "Documented GET {PortalURL}/.well-known/api-catalog; module writes linkset.json"
    },
    "telemetry": null,
    "source_url": "https://community.ibm.com/community/user/blogs/xuantong-liu/2025/10/13/introducing-api-catalog-support-in-ibm-api-connect"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://community.ibm.com/community/user/blogs/xuantong-liu/2025/10/13/introducing-api-catalog-support-in-ibm-api-connect",
  "note": "CMS Portal `v12.1.0.0` generates `linkset.json` at `{PortalURL}/.well-known/api-catalog` for public APIs."
 },
 {
  "id": "ibm-beeai",
  "org_id": "ibm",
  "name": "IBM BeeAI",
  "url": "https://github.com/i-am-bee/acp",
  "type": "sdk",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "IBM BeeAI",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-17",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-08-17",
    "col4_md": "Merged deprecated `ACP` into `A2A` (August 2025); `BeeAI Framework` ships native client and server adapters.",
    "full_detail_md": "IBM's Agent Communication Protocol (`ACP`) repository README states that ACP is now part of `A2A` under the Linux Foundation following their August 2025 merger, winding down standalone `acp-sdk` development; the A2A project blog (2026-08-27) and AAIF Growth Stage proposal (#37, approved 2026-08-04) state that the `BeeAI Framework` ships native `A2AServer` and `A2AAgent` adapters completing the ACP-to-A2A migration.",
    "facets": {
     "transport_bindings": "A2A client and server adapters (A2AServer, A2AAgent)",
     "discovery_artifact": "A2A Agent Card (replacing legacy ACP GET /agents discovery)",
     "protocol_version": "Migrated from ACP v1.0.3 (August 2025 merger) to A2A",
     "auth_schemes": "Framework-configured A2A security schemes",
     "verification_posture": "Official i-am-bee/acp deprecation notice plus AAIF proposal #37 adapter listing"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/i-am-bee/acp/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/i-am-bee/acp/main/README.md",
  "note": "Merged deprecated `ACP` into `A2A` (August 2025); `BeeAI Framework` ships native client and server adapters."
 },
 {
  "id": "idira-secrets-manager",
  "org_id": "palo-alto-networks",
  "name": "Idira Secrets Manager",
  "url": "https://www.paloaltonetworks.com/idira/machine/secrets-management",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Idira Secrets Manager",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "SaaS secrets manager supporting SPIFFE authentication.",
    "full_detail_md": "Idira Secrets Manager by Palo Alto Networks is listed as a SaaS secrets manager supporting SPIFFE authentication.",
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/spiffe/new-website/blob/master/data/users.yaml"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/spiffe/new-website/blob/master/data/users.yaml",
  "note": "SaaS secrets manager supporting SPIFFE authentication."
 },
 {
  "id": "ieee",
  "org_id": "ieee",
  "name": "IEEE",
  "url": "https://www.ieee.org",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "IEEE",
    "role": "Publisher",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Adopters list: IEEE (https://www.ieee.org): as tdmrep.json, with a policy.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md",
  "note": "Adopters list: IEEE (https://www.ieee.org): as tdmrep.json, with a policy."
 },
 {
  "id": "ikea",
  "org_id": "ingka",
  "name": "IKEA",
  "url": "https://www.ikea.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "IKEA (Ingka)",
    "role": "Retailer (Custom UCP endpoint)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Active `2026-04-08` on `mcp` and `rest`; `com.google.pay` environment is `TEST`.",
    "full_detail_md": "The Ingka profile's active ucp.version is 2026-04-08, while supported_versions maps 2026-08-25 to a separate profile URI (a version key, not a publication date). Capabilities are dev.ucp.shopping.checkout and dev.ucp.shopping.fulfillment, transports are mcp at https://ucp.checkout.ingka.com/api/us/mcp/messages and rest at https://ucp.checkout.ingka.com/api/us/2026-04-08/rest, payment handler com.google.pay is environment TEST at handler spec 2026-01-23, and the body publishes ES256 signing keys.",
    "facets": {
     "commerce_surface": "Ingka checkout host ucp.checkout.ingka.com (US)",
     "payment_handlers_or_rail": "com.google.pay only, handler spec 2026-01-23, environment TEST",
     "transport_bindings": "mcp at /api/us/mcp/messages and rest at /api/us/2026-04-08/rest",
     "spec_version": "Active ucp.version 2026-04-08; supported_versions maps 2026-08-25 to a separate URI (version key, not a publication date)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "ucp_version": "2026-04-08",
     "supported_versions": [
      "2026-08-25"
     ],
     "transports": [
      "mcp",
      "rest"
     ],
     "payment_handlers": [
      "com.google.pay"
     ],
     "environment": "TEST",
     "endpoint": "https://ucp.checkout.ingka.com/api/us/mcp/messages"
    },
    "source_url": "https://www.ikea.com/.well-known/ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ikea.com/.well-known/ucp",
  "note": "Active `2026-04-08` on `mcp` and `rest`; `com.google.pay` environment is `TEST`."
 },
 {
  "id": "interchange",
  "org_id": "interchange",
  "name": "Interchange",
  "url": "https://interchange.io",
  "type": "agent",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Interchange",
    "role": "Sales agent",
    "status": "Listed",
    "status_display": "Listed · as of 2026-06-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-19",
    "col4_md": "Talpa's adagents.json lists `https://interchange.io` under `authorized_agents`, `authorized_for` All Talpa Network properties, with `authorization_type` `property_tags` and `delegation_type` `direct`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://kijk.nl/.well-known/adagents.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://kijk.nl/.well-known/adagents.json",
  "note": "Talpa's adagents.json lists `https://interchange.io` under `authorized_agents`, `authorized_for` All Talpa Network properties, with `authorization_type` `property_tags` and `delegation_type` `direct`."
 },
 {
  "id": "intercom-prm",
  "org_id": "intercom",
  "name": "Intercom MCP",
  "url": "https://mcp.intercom.com",
  "type": "origin",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Intercom",
    "role": "Protected resource",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`resource` and `authorization_servers` `https://mcp.intercom.com`; `scopes_supported` `mcp`, `operator`; `bearer_methods_supported` `header`.",
    "full_detail_md": "GET https://mcp.intercom.com/.well-known/oauth-protected-resource returned HTTP 200 `application/json` with `access-control-allow-origin` `*`. `resource` is `https://mcp.intercom.com`. `authorization_servers` is `https://mcp.intercom.com`. `scopes_supported` are `mcp` and `operator`. `bearer_methods_supported` is `header`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.intercom.com/.well-known/oauth-protected-resource (resource https://mcp.intercom.com; authorization_servers https://mcp.intercom.com; scopes_supported mcp and operator)",
     "registration_or_client_id_modes": "Not declared in this protected-resource document",
     "pkce_or_grant_types": "Not declared in this protected-resource document; bearer_methods_supported header",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03); access-control-allow-origin *"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-protected-resource",
     "resource": "https://mcp.intercom.com"
    },
    "source_url": "https://mcp.intercom.com/.well-known/oauth-protected-resource"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.intercom.com/.well-known/oauth-protected-resource",
  "note": "`resource` and `authorization_servers` `https://mcp.intercom.com`; `scopes_supported` `mcp`, `operator`; `bearer_methods_supported` `header`."
 },
 {
  "id": "interposed",
  "org_id": "interposed",
  "name": "Interposed",
  "url": "https://interposed.ai/blog/migrating-aauth-draft-9-to-11.html",
  "type": "sdk",
  "implements": [
   "aauth-hardt"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "aauth-hardt",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Interposed",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-10",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-10",
    "col4_md": "Go library `aauth-go`, described by Interposed on 2026-10-10 as its open-source implementation of AAuth, with a published migration from draft 9 to draft 11 of draft-hardt-oauth-aauth-protocol.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://interposed.ai/blog/migrating-aauth-draft-9-to-11.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://interposed.ai/blog/migrating-aauth-draft-9-to-11.html",
  "note": "Go library `aauth-go`, described by Interposed on 2026-10-10 as its open-source implementation of AAuth, with a published migration from draft 9 to draft 11 of draft-hardt-oauth-aauth-protocol."
 },
 {
  "id": "introspection",
  "org_id": "introspection",
  "name": "Introspection",
  "url": "https://registry.npmjs.org/@introspection-sdk/aauth-resource",
  "type": "authority",
  "implements": [
   "aauth-hardt"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "aauth-hardt",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Introspection",
    "role": "Relying server / Verifier",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "npm package `@introspection-sdk/aauth-resource` (registry record checked 2026-10-29) makes an HTTP API an AAuth resource for draft-hardt-oauth-aauth-protocol-11. That draft publishes resource metadata at `/.well-known/aauth-resource.json`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@introspection-sdk/aauth-resource"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@introspection-sdk/aauth-resource",
  "note": "npm package `@introspection-sdk/aauth-resource` (registry record checked 2026-10-29) makes an HTTP API an AAuth resource for draft-hardt-oauth-aauth-protocol-11. That draft publishes resource metadata at `/.well-known/aauth-resource.json`."
 },
 {
  "id": "io-github-microsoft-playwright-mcp",
  "org_id": "microsoft",
  "name": "Playwright MCP",
  "url": "https://github.com/microsoft/playwright-mcp",
  "type": "sdk",
  "implements": [
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Microsoft",
    "role": "Server publisher",
    "status": "Listed in Official Registry (HTTP 200 server.json)",
    "status_display": "Listed in Official Registry (HTTP 200 server.json) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-18",
    "col4_md": "`io.github.microsoft/playwright-mcp` `0.0.82` (published 2026-09-18): npm `@playwright/mcp` over `stdio`.",
    "full_detail_md": "HTTP 200 `application/json`. Latest `io.github.microsoft/playwright-mcp` is version `0.0.82` on schema `2025-12-11`, with registry status `active` and `isLatest` true, published `2026-09-18`. The npm package is `@playwright/mcp` at version `0.0.82` with transport `stdio`.",
    "facets": {
     "registry_or_namespace": "io.github.microsoft/playwright-mcp",
     "api_or_schema_version": "Record publishedAt 2026-09-18; validates against server.schema.json (2025-12-11).",
     "transport_or_package_types": "npm package @playwright/mcp over stdio",
     "verification_posture": "HTTP 200 registry record probe (checked 2026-10-30, publishedAt 2026-09-18); proves registry metadata listing rather than live MCP server execution."
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "server_name": "io.github.microsoft/playwright-mcp",
     "version": "0.0.82"
    },
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.microsoft%2Fplaywright-mcp/versions/0.0.82"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.microsoft%2Fplaywright-mcp/versions/0.0.82",
  "note": "`io.github.microsoft/playwright-mcp` `0.0.82` (published 2026-09-18): npm `@playwright/mcp` over `stdio`."
 },
 {
  "id": "istio",
  "org_id": "istio",
  "name": "Istio",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Istio",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication.",
    "full_detail_md": "The SPIFFE overview lists Istio under open-source software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID, JWT SVID, and SPIFFE Authentication, and is not marked for Workload API.",
    "facets": {
     "svid_or_bundle_format": "Marks for X.509 SVID-based authentication and JWT SVID-based authentication.",
     "api_or_federation_surface": "SPIFFE Authentication is marked (federated authentication by trust domain name). Workload API is not marked.",
     "attestation_or_trust_domain": "Trust-domain federation is the marked SPIFFE Authentication column. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication."
 },
 {
  "id": "jetbrains-ides",
  "org_id": "jetbrains",
  "name": "JetBrains IDEs",
  "url": "https://blog.jetbrains.com/ai/2026/01/acp-agent-registry/",
  "type": "harness",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "JetBrains IDEs",
    "role": "Native IDE client (co-steward)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-28",
    "col4_md": "Built-in ACP client and `ACP Registry` in JetBrains IDEs `2025.3`+ consuming `registry-for-jetbrains.json`.",
    "full_detail_md": "JetBrains co-develops ACP with Zed and integrates the `ACP Registry` directly into JetBrains IDEs in versions `2025.3` and later (announced 2026-01-28), consuming dedicated registry indices (`registry-for-jetbrains.json`, `registry-for-jetbrains-preview.json`, and `registry-for-jetbrains-air.json`).",
    "facets": {
     "role_in_acp": "IDE client and protocol co-steward",
     "integration_mode": "Native built-in ACP client and ACP Agent Registry integration (IDE v2025.3+)",
     "transport": "JSON-RPC 2.0 over stdio subprocesses",
     "verification_posture": "First-party JetBrains blog announcements & ACP Registry repository documentation",
     "sdk_or_package": "JetBrains IDEs 2025.3+ & JetBrains Air"
    },
    "telemetry": null,
    "source_url": "https://blog.jetbrains.com/ai/2025/10/jetbrains-zed-open-interoperability-for-ai-coding-agents-in-your-ide/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.jetbrains.com/ai/2025/10/jetbrains-zed-open-interoperability-for-ai-coding-agents-in-your-ide/",
  "note": "Built-in ACP client and `ACP Registry` in JetBrains IDEs `2025.3`+ consuming `registry-for-jetbrains.json`."
 },
 {
  "id": "jetpack-compose",
  "org_id": "google",
  "name": "A2UI Jetpack Compose renderer",
  "url": "https://a2ui.org/roadmap/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Jetpack Compose",
    "role": "Android renderer",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Roadmap lists Jetpack Compose Planned for Q2 2026; renderers matrix marks v0.9.1 Alpha and v1.0 Planned. The Google Developers Blog says the Jetpack Compose renderer supports 0.9.1 today, with 1.0 coming soon.",
    "full_detail_md": "The roadmap and published client-setup guide list Jetpack Compose as Planned for Android (Q2 2026), whereas the renderers reference table marks Jetpack Compose Alpha on v0.9.1 and Planned on v1.0.",
    "facets": {
     "transport_or_binding": "Android renderer across roadmap and renderers reference",
     "component_or_catalog": "Jetpack Compose (Planned on roadmap; Alpha on v0.9.1 in renderers matrix)",
     "spec_version": "Planned for Q2 2026 on roadmap; Alpha on v0.9.1 in renderers matrix",
     "sdk_or_renderer": "Jetpack Compose"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/roadmap/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://a2ui.org/roadmap/",
  "note": "Roadmap lists Jetpack Compose Planned for Q2 2026; renderers matrix marks v0.9.1 Alpha and v1.0 Planned. The Google Developers Blog says the Jetpack Compose renderer supports 0.9.1 today, with 1.0 coming soon."
 },
 {
  "id": "jomashop",
  "org_id": "jomashop",
  "name": "Jomashop",
  "url": "https://thepaypers.com/fraud-and-fincrime/news/skyfire-and-forter-partner-to-verify-ai-agents-at-checkout",
  "type": "venue",
  "implements": [
   "kyapay-token"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Jomashop",
    "role": "Seller (Pilot merchant)",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Pilot US watch & luxury retailer verifying agentic checkout purchases via Skyfire KYA tokens and Forter fraud decisioning",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://thepaypers.com/fraud-and-fincrime/news/skyfire-and-forter-partner-to-verify-ai-agents-at-checkout"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://thepaypers.com/fraud-and-fincrime/news/skyfire-and-forter-partner-to-verify-ai-agents-at-checkout",
  "note": "Pilot US watch & luxury retailer verifying agentic checkout purchases via Skyfire KYA tokens and Forter fraud decisioning"
 },
 {
  "id": "json-render",
  "org_id": "vercel",
  "name": "json-render",
  "url": "https://a2ui.org/ecosystem/a2ui-in-the-world/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "json-render",
    "role": "React renderer",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "The ecosystem page lists json-render as Vercel's React library for rendering A2UI component catalogs via Zod schemas.",
    "full_detail_md": "The ecosystem page lists json-render as Vercel's React library for rendering A2UI component catalogs via Zod schemas.",
    "facets": {
     "transport_or_binding": "React library listed on the A2UI ecosystem page",
     "component_or_catalog": "A2UI component catalogs expressed with Zod schemas",
     "spec_version": "Listed; the ecosystem page does not pin a json-render version",
     "sdk_or_renderer": "Vercel json-render"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/ecosystem/a2ui-in-the-world/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://a2ui.org/ecosystem/a2ui-in-the-world/",
  "note": "The ecosystem page lists json-render as Vercel's React library for rendering A2UI component catalogs via Zod schemas."
 },
 {
  "id": "keycloak-cimd",
  "org_id": "keycloak",
  "name": "Keycloak",
  "url": "https://www.keycloak.org",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Keycloak",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "URL `client_id` needs a profile with the `client-id-metadata-document` executor.",
    "full_detail_md": "Keycloak processes an authorization request whose `client_id` is a URL pointing at a Client ID Metadata Document by using a client policy profile that includes the `client-id-metadata-document` executor.",
    "facets": {
     "metadata_flag_or_profile": "Client policy profile includes the client-id-metadata-document executor so a URL client_id is processed as a Client ID Metadata Document",
     "auth_method_or_pkce": "Not named on the MCP authorization-server page beyond processing the URL client_id",
     "uri_or_ssrf_rules": "The client_id parameter is a URL pointing at the Client ID Metadata Document",
     "draft_or_spec_version": "Undated Keycloak documentation; it does not name a CIMD draft revision"
    },
    "telemetry": null,
    "source_url": "https://www.keycloak.org/securing-apps/mcp-authz-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.keycloak.org/securing-apps/mcp-authz-server",
  "note": "URL `client_id` needs a profile with the `client-id-metadata-document` executor."
 },
 {
  "id": "keycloak-id-jag",
  "org_id": "keycloak",
  "name": "Keycloak ID-JAG",
  "url": "https://www.keycloak.org/securing-apps/identity-assertion-jwt-authorization-grant",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Keycloak",
    "role": "Experimental ID-JAG receiver; issuer not yet",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The guide is based on `draft-ietf-oauth-identity-assertion-authz-grant-01` and says this feature is experimental and may introduce breaking changes. Do not use this feature in production environments. Implemented (Receiver Side): Keycloak can accept an ID-JAG Identity Assertion from an external issuer and grant a local access token. Not Yet Implemented (Issuer Side): native generation of the ID-JAG on demand is not yet fully implemented.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.keycloak.org/securing-apps/identity-assertion-jwt-authorization-grant"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.keycloak.org/securing-apps/identity-assertion-jwt-authorization-grant",
  "note": "The guide is based on `draft-ietf-oauth-identity-assertion-authz-grant-01` and says this feature is experimental and may introduce breaking changes. Do not use this feature in production environments. Implemented (Receiver Side): Keycloak can accept an ID-JAG Identity Assertion from an external issuer and grant a local access token. Not Yet Implemented (Issuer Side): native generation of the ID-JA"
 },
 {
  "id": "knox",
  "org_id": "knox",
  "name": "Pinterest Knox",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Pinterest Knox",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Open-source works-with listing: X.509 SVID and JWT SVID only.",
    "full_detail_md": "The SPIFFE overview lists Knox under open-source software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID and JWT SVID only. The SPIFFE site lists Pinterest Knox as a consumer whose customers authenticate to Knox with SPIFFE IDs.",
    "facets": {
     "svid_or_bundle_format": "Marks for X.509 SVID-based authentication and JWT SVID-based authentication only.",
     "api_or_federation_surface": "Neither SPIFFE Authentication nor the Workload API is marked.",
     "attestation_or_trust_domain": "No trust-domain federation mark. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Open-source works-with listing: X.509 SVID and JWT SVID only."
 },
 {
  "id": "kong-konnect-mcp-registry",
  "org_id": "kong",
  "name": "Kong Konnect MCP Registry",
  "url": "https://konghq.com",
  "type": "authority",
  "implements": [
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Kong Konnect MCP Registry",
    "role": "Enterprise registry",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-12",
    "col4_md": "March 2026 enterprise registry implementing a REST API aligned with `registry.modelcontextprotocol.io`.",
    "full_detail_md": "On `2026-03-12` Kong described the Kong Konnect MCP Registry as a registry that implements a REST API built in accordance with the AAIF official MCP registry specification. A later Kong page names `registry.modelcontextprotocol.io` as the community-maintained public registry that implements the MCP Registry Specification.",
    "facets": {
     "registry_or_namespace": "Kong Konnect MCP Registry; names registry.modelcontextprotocol.io as the public registry",
     "api_or_schema_version": "REST API built to the AAIF official MCP registry specification",
     "transport_or_package_types": "REST API",
     "verification_posture": "Document citation of the Kong engineering post published 2026-03-12 (checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://konghq.com/blog/engineering/mcp-registry-dynamic-tool-discovery"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://konghq.com/blog/engineering/mcp-registry-dynamic-tool-discovery",
  "note": "March 2026 enterprise registry implementing a REST API aligned with `registry.modelcontextprotocol.io`."
 },
 {
  "id": "kya-os-mcp-npm",
  "org_id": "decentralized-identity",
  "name": "@kya-os/mcp",
  "url": "https://www.npmjs.com/package/@kya-os/mcp",
  "type": "sdk",
  "implements": [
   "kya-os"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "kya-os",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "@kya-os/mcp",
    "role": "Reference SDK",
    "status": "Development",
    "status_display": "Development · as of 2026-10-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "npm `@kya-os/mcp` latest `1.21.2` (`2026-10-27`); self-reported `L3 full` on suite `1.1.0`.",
    "full_detail_md": "npm package @kya-os/mcp, whose registry time record was created 2026-05-14, publishes dist-tag latest 1.21.2 on 2026-10-27 and describes that version as the reference implementation of the KYA-OS protocol for Model Context Protocol servers covering delegation, proof, and session primitives; version 1.18.0 was published 2026-10-08. The builders registry says the conformance vectors derive from this codebase, so its full-suite pass is self-reported, not independent evidence, and lists @kya-os/mcp as L3 full on suite 1.1.0. Release v1.19.0, published 2026-10-09, names conformance suite 1.2.0.",
    "facets": {
     "passport_or_credential": "npm describes delegation, proof, and session primitives for Model Context Protocol servers. Builders lists a self-reported L3 full claim, not independent evidence.",
     "cryptographic_alg": "Builders describes DID identity and detached-JWS proofs for this package. The npm record does not name Ed25519.",
     "transport_or_binding": "MCP binding. The 1.21.2 description calls it the reference implementation for Model Context Protocol servers.",
     "sdk_or_package": "npm @kya-os/mcp dist-tag latest 1.21.2 published 2026-10-27; 1.18.0 published 2026-10-08; time record created 2026-05-14. Suite 1.1.0, Claim L3 full, self-reported."
    },
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@kya-os%2fmcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@kya-os%2fmcp",
  "note": "npm `@kya-os/mcp` latest `1.21.2` (`2026-10-27`); self-reported `L3 full` on suite `1.1.0`."
 },
 {
  "id": "kya-os-mcp-repo",
  "org_id": "decentralized-identity",
  "name": "decentralized-identity/kya-os-mcp",
  "url": "https://github.com/decentralized-identity/kya-os-mcp",
  "type": "sdk",
  "implements": [
   "kya-os"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "kya-os",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "decentralized-identity/kya-os-mcp",
    "role": "Reference implementation",
    "status": "Development",
    "status_display": "Development · as of 2026-10-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "Main-branch MCP reference repo, created `2026-03-10`; SPEC.md `1.0.0`, Status Stable.",
    "full_detail_md": "decentralized-identity/kya-os-mcp, created 2026-03-10 and last pushed 2026-10-27 under the MIT License, is the GitHub repository for the KYA-OS MCP protocol reference implementation covering delegation, proof generation, session lifecycle, and cryptographic identity. GOVERNANCE.md calls it the DIF TAAWG protocol reference implementation for the MCP binding; the README says the protocol was previously MCP-Identity / MCP-I and that @kya-os/mcp is the MCP binding and the first binding to ship; main-branch SPEC.md is Version 1.0.0 with Status Stable, which is a spec header on main rather than an npm dist-tag.",
    "facets": {
     "passport_or_credential": "Reference implementation for delegation, proof generation, session lifecycle, and cryptographic identity. Previously known as MCP-Identity / MCP-I.",
     "cryptographic_alg": "Main-branch SPEC.md is Version 1.0.0 with Status Stable. The GitHub repository record does not name an algorithm.",
     "transport_or_binding": "MCP binding. GOVERNANCE.md identifies the DIF TAAWG protocol reference implementation. @kya-os/mcp is the first binding to ship.",
     "sdk_or_package": "Repository decentralized-identity/kya-os-mcp, created 2026-03-10, pushed_at 2026-10-27, MIT License. Main SPEC.md 1.0.0 is the spec header, not a package dist-tag."
    },
    "telemetry": null,
    "source_url": "https://api.github.com/repos/decentralized-identity/kya-os-mcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/repos/decentralized-identity/kya-os-mcp",
  "note": "Main-branch MCP reference repo, created `2026-03-10`; SPEC.md `1.0.0`, Status Stable."
 },
 {
  "id": "kya-os-poc-demo-server",
  "org_id": "decentralized-identity",
  "name": "KYA-OS PoC demo server",
  "url": "https://demo-mcp.kya-os.ai",
  "type": "origin",
  "implements": [
   "kya-os"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "kya-os",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "KYA-OS PoC demo server",
    "role": "Reference MCP server",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "PoC `did:web:demo-mcp.kya-os.ai` pins `@kya-os/mcp` `1.18.0`, behind npm latest `1.21.2`.",
    "full_detail_md": "The Entity Card names this server KYA-OS PoC demo server (entityType mcp, id did:web:demo-mcp.kya-os.ai) with capabilities vault.read and vault.write, proofProfile org.kya-os/proof.v1, and statusListIndex 94. Provenance reports package @kya-os/mcp version 1.18.0, mcpProtocol 2026-07-28 (the MCP protocol date, not a publication date), node v20.20.2, and repository https://github.com/decentralized-identity/kya-os-mcp; the README describes a maintainer-operated pinned-release deployment at that DID, builders lists Deployed 1.18.0 checked 2026-10-30, and npm dist-tag latest is 1.21.2.",
    "facets": {
     "passport_or_credential": "Entity Card id did:web:demo-mcp.kya-os.ai, entityType mcp, capabilities vault.read and vault.write, statusListIndex 94.",
     "cryptographic_alg": "proofProfile org.kya-os/proof.v1. The card body does not print an Ed25519 public key.",
     "transport_or_binding": "MCP card at /.well-known/kya-os-card.json. Provenance mcpProtocol 2026-07-28 is the MCP protocol date, not a publication date. Node v20.20.2.",
     "sdk_or_package": "Pinned @kya-os/mcp 1.18.0. Builders lists Deployed 1.18.0, checked 2026-10-30. npm dist-tag latest is 1.21.2. Repository https://github.com/decentralized-identity/kya-os-mcp."
    },
    "telemetry": null,
    "source_url": "https://demo-mcp.kya-os.ai/.well-known/kya-os-card.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://demo-mcp.kya-os.ai/.well-known/kya-os-card.json",
  "note": "PoC `did:web:demo-mcp.kya-os.ai` pins `@kya-os/mcp` `1.18.0`, behind npm latest `1.21.2`."
 },
 {
  "id": "l402-space",
  "org_id": "alby",
  "name": "Alby",
  "url": "https://l402.space",
  "type": "origin",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Alby (l402.space)",
    "role": "Seller & cross-rail gateway",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Universal 402 gateway; `/l402/ping` returns `amountSats` 1.",
    "full_detail_md": "l402.space is a universal 402 gateway: the caller pays the gateway, and the gateway pays the upstream API over x402/USDC, MPP Tempo, MPP Lightning, or L402, using a WWW-Authenticate: L402 challenge with token and bolt11 invoice. A probe of /l402/ping returns Payment required with amountSats 1, and Alby's Aug 12, 2026 post describes the same gateway.",
    "facets": {
     "settlement_rail": "Caller pays the gateway on their rail; upstream may be x402/USDC, MPP Tempo, MPP Lightning, or L402",
     "token_or_macaroon": "Documented L402 token is a macaroon",
     "headers_or_challenge": "WWW-Authenticate: L402 token and bolt11 invoice",
     "sdk_or_endpoint": "https://l402.space/l402/ping returns Payment required and amountSats 1"
    },
    "telemetry": {
     "snapshot_http_status": 200,
     "body_error": "Payment required",
     "amount_sats": 1
    },
    "source_url": "https://l402.space/docs"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://l402.space/docs",
  "note": "Universal 402 gateway; `/l402/ping` returns `amountSats` 1."
 },
 {
  "id": "lago",
  "org_id": "lago",
  "name": "Lago (getlago.com)",
  "url": "https://getlago.com/agents.txt",
  "type": "origin",
  "implements": [
   "agents-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Lago (getlago.com)",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring an agents.json companion, MCP servers, a Skills file, and WebMCP",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "/agents.txt"
    },
    "source_url": "https://getlago.com/agents.txt"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://getlago.com/agents.txt",
  "note": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring an agents.json companion, MCP servers, a Skills file, and WebMCP"
 },
 {
  "id": "langchain",
  "org_id": "langchain",
  "name": "LangChain",
  "url": "https://docs.langchain.com/llms.txt",
  "type": "sdk",
  "implements": [
   "ag-ui",
   "llms-txt"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "LangChain",
    "role": "Framework docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://docs.langchain.com/llms.txt` (`# Docs by LangChain`, `text/plain`), linking recursive `/_llms/` sub-indexes and OpenAPI specs.",
    "full_detail_md": "Serves `https://docs.langchain.com/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 4,252 bytes, fetched 2026-11-04) opening `# Docs by LangChain` and instructing agents to follow `/_llms/agent-development-lifecycle.txt` (1,518 pages) and `/_llms/products-and-setup.txt` (223 pages) recursively alongside three OpenAPI specifications.",
    "facets": {
     "artifact_path": "https://docs.langchain.com/llms.txt",
     "companion_files": "/_llms/agent-development-lifecycle.txt (1,518 pages); /_llms/products-and-setup.txt (223 pages); OpenAPI specs",
     "content_type_or_bytes": "text/plain; charset=utf-8 (4,252 bytes)",
     "generator_or_consumer_mode": "Recursive Mintlify index pointing to /_llms/*.txt sub-indexes"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Docs by LangChain"
    },
    "source_url": "https://docs.langchain.com/llms.txt"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LangChain",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists LangChain as Supported; AG-UI began with the CopilotKit, LangChain, and CrewAI partnership.",
    "full_detail_md": "The AG-UI overview lists LangChain as Supported under Agent Framework - Partnerships, with Docs and Demos, and says AG-UI was born from CopilotKit's initial partnership with LangChain and CrewAI. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "Partnership agent framework (directory listing)",
     "sdk_or_package": "Not named; Docs and Demos only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://docs.langchain.com/llms.txt",
  "note": "Serves `https://docs.langchain.com/llms.txt` (`# Docs by LangChain`, `text/plain`), linking recursive `/_llms/` sub-indexes and OpenAPI specs."
 },
 {
  "id": "langfuse",
  "org_id": "langfuse",
  "name": "Langfuse",
  "url": "https://langfuse.com/docs/opentelemetry/get-started",
  "type": "origin",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Langfuse",
    "role": "OpenTelemetry backend",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Docs fetched 2026-11-04. Langfuse can operate as an OpenTelemetry Backend and can receive traces on `/api/public/otel` (OTLP). The exporter example uses `https://cloud.langfuse.com/api/public/otel`. The page says it focuses on spans with `gen_ai.*` attributes and names OpenTelemetry GenAI semantic conventions. Attributes in the `langfuse.*` namespace map OpenTelemetry span attributes directly to the Langfuse data model and take precedence over the generic OpenTelemetry conventions.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://langfuse.com/docs/opentelemetry/get-started"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://langfuse.com/docs/opentelemetry/get-started",
  "note": "Docs fetched 2026-11-04. Langfuse can operate as an OpenTelemetry Backend and can receive traces on `/api/public/otel` (OTLP). The exporter example uses `https://cloud.langfuse.com/api/public/otel`. The page says it focuses on spans with `gen_ai.*` attributes and names OpenTelemetry GenAI semantic conventions. Attributes in the `langfuse.*` namespace map OpenTelemetry span attributes directly to t"
 },
 {
  "id": "langgraph",
  "org_id": "langchain",
  "name": "LangGraph",
  "url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "type": "sdk",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LangGraph",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-27",
    "col4_md": "AAIF proposal lists hosted `/a2a/{assistant_id}` endpoints with auto-generated Agent Cards, `SSE` streaming, and `LangSmith` tracing.",
    "full_detail_md": "The A2A project blog (2026-08-27) names LangGraph among supporting frameworks, and the AAIF Growth Stage proposal (#37) states that LangGraph and `LangSmith` Deployment expose a hosted A2A endpoint at `/a2a/{assistant_id}` for every deployed agent with an auto-generated Agent Card, `SSE` streaming, and LangSmith distributed tracing.",
    "facets": {
     "transport_bindings": "Hosted HTTP endpoint at /a2a/{assistant_id} with Server-Sent Events (SSE) streaming",
     "discovery_artifact": "Auto-generated Agent Card per deployed assistant",
     "protocol_version": "Not specified in AAIF proposal (2026-08-27 blog / proposal #37)",
     "auth_schemes": "LangSmith Deployment authentication",
     "verification_posture": "Listed in A2A blog (2026-08-27) and AAIF proposal #37"
    },
    "telemetry": null,
    "source_url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "note": "AAIF proposal lists hosted `/a2a/{assistant_id}` endpoints with auto-generated Agent Cards, `SSE` streaming, and `LangSmith` tracing."
 },
 {
  "id": "langgraph-python-self-hosted",
  "org_id": "copilotkit",
  "name": "LangGraph (Python, self-hosted)",
  "url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LangGraph (Python, self-hosted)",
    "role": "Archived AG-UI adapter binding",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-06-03",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-03",
    "col4_md": "Archived Jun 3, 2026 skill `1.0.0`: client `LangGraphHttpAgent` from `@copilotkit/runtime/langgraph`, adapter `ag-ui-langgraph` (`add_langgraph_fastapi_endpoint`), port 8123.",
    "full_detail_md": "The CopilotKit integrations skill was archived by the owner on Jun 3, 2026 and is now read-only. Its supported-integrations table, which the live integrations page does not carry as adapter class names, lists LangGraph (Python, self-hosted) with client LangGraphHttpAgent, server adapter ag-ui-langgraph via add_langgraph_fastapi_endpoint, and agent port 8123. The same page describes the four-layer pattern: agent server, AG-UI adapter, CopilotRuntime, and frontend hooks useAgent, useFrontendTool, useRenderToolCall, and useHumanInTheLoop.",
    "facets": {
     "transport": "AG-UI HTTP adapter on port 8123",
     "event_or_state_model": "CopilotRuntime agents map plus frontend useAgent state",
     "integration_role": "Self-hosted LangGraph server behind ag-ui-langgraph",
     "sdk_or_package": "@copilotkit/runtime/langgraph and ag-ui-langgraph"
    },
    "telemetry": null,
    "source_url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "note": "Archived Jun 3, 2026 skill `1.0.0`: client `LangGraphHttpAgent` from `@copilotkit/runtime/langgraph`, adapter `ag-ui-langgraph` (`add_langgraph_fastapi_endpoint`), port 8123."
 },
 {
  "id": "las-wg-agent-permissions",
  "org_id": "las-wg-agent-permissions",
  "name": "LAS-WG agent-permissions (Python)",
  "url": "https://raw.githubusercontent.com/las-wg/agent-permissions-python/main/README.md",
  "type": "sdk",
  "implements": [
   "agent-permissions-json"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agent-permissions-json",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "LAS-WG agent-permissions (Python)",
    "role": "Validator / Parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Package `agent-permissions` 0.1.0 (in pyproject.toml) discovers a manifest via `<link rel=\"agent-permissions\">` or `/.well-known/agent-permissions.json`; predating the `strict` field, `validate_interaction` returns `allowed=False` with reason `No matching resource rule` when nothing matches.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/las-wg/agent-permissions-python/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/las-wg/agent-permissions-python/main/README.md",
  "note": "Package `agent-permissions` 0.1.0 (in pyproject.toml) discovers a manifest via `<link rel=\"agent-permissions\">` or `/.well-known/agent-permissions.json`; predating the `strict` field, `validate_interaction` returns `allowed=False` with reason `No matching resource rule` when nothing matches."
 },
 {
  "id": "last-record",
  "org_id": "last-record",
  "name": "Last Record (kbipul/last-record)",
  "url": "https://raw.githubusercontent.com/kbipul/last-record/main/README.md",
  "type": "authority",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Last Record (kbipul/last-record)",
    "role": "Verifier / Audit parser",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-18",
    "col4_md": "Browser and CLI checker, repository created 2026-09-18. It takes an agent tool-call log, checks each record against the draft's mandatory fields, and recomputes the SHA-256 hash chain. The repository description says the point is to show what that chain cannot prove, including after the tail of the log is cut.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/kbipul/last-record/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/kbipul/last-record/main/README.md",
  "note": "Browser and CLI checker, repository created 2026-09-18. It takes an agent tool-call log, checks each record against the draft's mandatory fields, and recomputes the SHA-256 hash chain. The repository description says the point is to show what that chain cannot prove, including after the tail of the log is cut."
 },
 {
  "id": "launch-publisher-partners",
  "org_id": "launch-publisher-partners",
  "name": "Launch publisher partners",
  "url": "https://www.cloudflare.com/press/press-releases/2025/cloudflare-just-changed-how-ai-crawlers-scrape-the-internet-at-large/",
  "type": "origin",
  "implements": [
   "cloudflare-pay-per-crawl"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-pay-per-crawl",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Press-release supporters",
    "role": "Publisher cohort (press-release supporters)",
    "status": "Listed",
    "status_display": "Listed · as of 2025-07-01",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2025-07-01",
    "col4_md": "Press-release supporters of permission-based AI crawling (including ADWEEK, AP, The Atlantic, Condé Nast, Fortune, Quora, Reddit, and TIME, with Quora naming Pay Per Crawl); live endpoints not independently verified.",
    "full_detail_md": "Cloudflare's July 1, 2025 press release lists content, media, and technology organizations supporting a permission-based model for AI crawling alongside early access to the Pay Per Crawl beta—including ADWEEK, The Associated Press, The Atlantic, Condé Nast, Fortune, Gannett | USA TODAY Network, O'Reilly Media, Pinterest, ProRata AI, Quora, Reddit, Sky News Group, SourceForge, Stack Overflow, TIME, Universal Music Group, Webflow, and Ziff Davis (with Quora stating commitment to supporting initiatives like Pay Per Crawl). Press-release listing indicates policy endorsement or early-access beta interest; live Pay Per Crawl endpoints on these domains are not independently verified.",
    "facets": {
     "scope_host": "https://www.cloudflare.com/press/press-releases/2025/cloudflare-just-changed-how-ai-crawlers-scrape-the-internet-at-large/",
     "policy_or_enforcement_role": "Press-release-announced cohort supporting permission-based AI crawling at Pay Per Crawl beta launch",
     "pricing_or_headers": "No per-domain charge rates disclosed in launch press release",
     "auth_mechanism": "Cloudflare Pay Per Crawl early-access beta program",
     "beta_or_availability_posture": "Announced launch partner cohort (private beta, 2025-07-01 press release) — live endpoints not independently verified"
    },
    "telemetry": null,
    "source_url": "https://www.cloudflare.com/press/press-releases/2025/cloudflare-just-changed-how-ai-crawlers-scrape-the-internet-at-large/"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://www.cloudflare.com/press/press-releases/2025/cloudflare-just-changed-how-ai-crawlers-scrape-the-internet-at-large/",
  "note": "Press-release supporters of permission-based AI crawling (including ADWEEK, AP, The Atlantic, Condé Nast, Fortune, Quora, Reddit, and TIME, with Quora naming Pay Per Crawl); live endpoints not independently verified."
 },
 {
  "id": "launchpad",
  "org_id": "launchpad",
  "name": "Launchpad",
  "url": "https://launchpad.net",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment",
   "aipref-vocabulary",
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "crawler_policy",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Launchpad",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "robots.txt on launchpad.net, bugs.launchpad.net, code.launchpad.net, and answers.launchpad.net each serves `Content-Usage: ai=n` in the `User-agent: *` group, with the comment `# Source: https://robotstxt.com/ai` and an adjacent `Content-Signal: ai-train=no, search=yes, ai-input=no`. The label ai is not a vocab-08 Table 1 label (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain",
     "attachment": "robots.txt",
     "content_usage": "Content-Usage: ai=n",
     "sibling_hosts_same_line": [
      "bugs.launchpad.net",
      "code.launchpad.net",
      "answers.launchpad.net"
     ]
    },
    "source_url": "https://launchpad.net/robots.txt"
   },
   {
    "protocol_id": "aipref-vocabulary",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Launchpad",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `Content-Usage: ai=n` in the `User-agent: *` group on launchpad.net, bugs.launchpad.net, code.launchpad.net, and answers.launchpad.net, next to `Content-Signal: ai-train=no, search=yes, ai-input=no`. The file comment cites `https://robotstxt.com/ai`. `ai` is the AI Training label in `draft-ietf-aipref-vocab-01` Table 1 and is not a `draft-ietf-aipref-vocab-08` Table 1 label.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "surface": "robots.txt",
     "content_usage": "ai=n",
     "hosts": [
      "launchpad.net",
      "bugs.launchpad.net",
      "code.launchpad.net",
      "answers.launchpad.net"
     ]
    },
    "source_url": "https://launchpad.net/robots.txt"
   },
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Launchpad",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "`https://launchpad.net/robots.txt` returned status 200 on 2026-10-29 with `Content-Signal: ai-train=no, search=yes, ai-input=no` in the group for all user agents, next to `Content-Usage: ai=n`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://launchpad.net/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://launchpad.net/robots.txt",
  "note": "robots.txt on launchpad.net, bugs.launchpad.net, code.launchpad.net, and answers.launchpad.net each serves `Content-Usage: ai=n` in the `User-agent: *` group, with the comment `# Source: https://robotstxt.com/ai` and an adjacent `Content-Signal: ai-train=no, search=yes, ai-input=no`. The label ai is not a vocab-08 Table 1 label (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored."
 },
 {
  "id": "leprogres-fr",
  "org_id": "le-progres",
  "name": "Le Progrès",
  "url": "https://www.leprogres.fr/",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Le Progrès",
    "role": "Newspaper",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Homepage response headers (HTTP 200, `text/html; charset=utf-8`, checked 2026-10-30): `tdm-reservation: 1` and `tdm-policy: https://www.leprogres.fr/tdm-policy/tdm-policy.json`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/html; charset=utf-8",
     "attachment": "http-header",
     "tdm_reservation": "1",
     "tdm_policy": "https://www.leprogres.fr/tdm-policy/tdm-policy.json"
    },
    "source_url": "https://www.leprogres.fr/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.leprogres.fr/",
  "note": "Homepage response headers (HTTP 200, `text/html; charset=utf-8`, checked 2026-10-30): `tdm-reservation: 1` and `tdm-policy: https://www.leprogres.fr/tdm-policy/tdm-policy.json`."
 },
 {
  "id": "lg-ad-solutions",
  "org_id": "lg-ad-solutions",
  "name": "LG Ad Solutions",
  "url": "https://agenticadvertising.org/",
  "type": "origin",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LG Ad Solutions",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-12",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-12",
    "col4_md": "AgenticAdvertising.org says that on October 16, 2025 the first agent-to-agent media buy was executed with real inventory from LG Ads. The December 12, 2025 launch announcement lists LG Ad Solutions among companies giving wide-industry support. `datePublished` on that announcement is 2025-12-12.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://agenticadvertising.org/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://agenticadvertising.org/",
  "note": "AgenticAdvertising.org says that on October 16, 2025 the first agent-to-agent media buy was executed with real inventory from LG Ads. The December 12, 2025 launch announcement lists LG Ad Solutions among companies giving wide-industry support. `datePublished` on that announcement is 2025-12-12."
 },
 {
  "id": "lightning-aperture",
  "org_id": "lightning-labs",
  "name": "Lightning Labs Aperture",
  "url": "https://docs.lightning.engineering/lightning-network-tools/aperture",
  "type": "venue",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Lightning Labs (Aperture)",
    "role": "Reverse proxy",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Aperture reverse proxy implements `L402` and `MPP`, in production on Loop and Pool.",
    "full_detail_md": "Aperture is a reverse proxy that acts as a payment and authentication gateway for Lightning Network powered APIs. It implements L402 and MPP, and is currently used in production in Lightning Loop and Pool.",
    "facets": {
     "settlement_rail": "Lightning Network, through the Aperture reverse proxy",
     "challenge_or_scheme": "Aperture implements both the L402 and the MPP specifications",
     "headers_or_methods": "Payment and authentication gateway for Lightning Network powered APIs",
     "sdk_or_endpoint": "Production use in Lightning Loop and Pool"
    },
    "telemetry": null,
    "source_url": "https://docs.lightning.engineering/lightning-network-tools/aperture"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.lightning.engineering/lightning-network-tools/aperture",
  "note": "Aperture reverse proxy implements `L402` and `MPP`, in production on Loop and Pool."
 },
 {
  "id": "lightning-enable",
  "org_id": "refined-element",
  "name": "Lightning Enable",
  "url": "https://www.lightningenable.com",
  "type": "venue",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Lightning Enable",
    "role": "Seller & payment processor",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Wraps APIs with a 402 macaroon invoice; probed `amount_sats` 3919.",
    "full_detail_md": "Lightning Enable wraps existing HTTP APIs so an agent gets 402 Payment Required with a Lightning invoice and a macaroon, then retries with Authorization: L402, while merchants create and verify challenges and take payouts over Nostr Wallet Connect or a Strike or OpenNode account. The probed NWC document returns error Payment Required, amount_sats 3919, an lnbc invoice, and tells the client to send Authorization: L402.",
    "facets": {
     "settlement_rail": "Lightning Network invoice, with merchant payout over Nostr Wallet Connect, Strike, or OpenNode",
     "token_or_macaroon": "Macaroon carried in the L402 challenge",
     "headers_or_challenge": "402 Payment Required with WWW-Authenticate: L402 macaroon and invoice; retry Authorization: L402",
     "sdk_or_endpoint": "api.lightningenable.com NWC content path; probed amount_sats 3919 with an lnbc invoice"
    },
    "telemetry": {
     "snapshot_http_status": 200,
     "body_error": "Payment Required",
     "has_macaroon": true,
     "has_bolt11_invoice": true,
     "amount_sats": 3919
    },
    "source_url": "https://www.lightningenable.com/llms.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.lightningenable.com/llms.txt",
  "note": "Wraps APIs with a 402 macaroon invoice; probed `amount_sats` 3919."
 },
 {
  "id": "lightning-enable-mcp",
  "org_id": "refined-element",
  "name": "Lightning Enable",
  "url": "https://github.com/refined-element/lightning-enable-mcp",
  "type": "sdk",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Lightning Enable (lightning-enable-mcp)",
    "role": "Client MCP server",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Main-branch MCP server pays L402 via Strike, NWC, or LND preimage.",
    "full_detail_md": "The lightning-enable-mcp README on main describes an MCP server that automatically pays L402 challenges and needs a wallet that returns the payment preimage, naming Strike, NWC, and LND. That evidence is the floating main branch rather than a release tag, so the row is Partial.",
    "facets": {
     "settlement_rail": "Lightning BOLT11 invoice paid by the configured wallet",
     "token_or_macaroon": "L402 completion requires the payment preimage",
     "headers_or_challenge": "Automatically pays L402 challenges for API access",
     "sdk_or_endpoint": "refined-element/lightning-enable-mcp on main; wallets Strike, NWC, or LND"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/refined-element/lightning-enable-mcp/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/refined-element/lightning-enable-mcp/main/README.md",
  "note": "Main-branch MCP server pays L402 via Strike, NWC, or LND preimage."
 },
 {
  "id": "lightning-faucet",
  "org_id": "lightning-faucet",
  "name": "Lightning Faucet",
  "url": "https://lightningfaucet.com",
  "type": "venue",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Lightning Faucet",
    "role": "Seller",
    "status": "Live (HTTP 402)",
    "status_display": "Live (HTTP 402) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Pay-per-call seller; `onchain_fee` probe is `price_sats` 50.",
    "full_detail_md": "Lightning Faucet lists 25+ pay-per-call endpoints priced from 5 to 500 sats. Probing /api/l402/onchain_fee returns Payment required, price_sats 50, an lnbc invoice, a token and a macaroon, and tells the client to retry with Authorization: L402 using the token and preimage.",
    "facets": {
     "settlement_rail": "Lightning Network lnbc invoice priced in sats",
     "token_or_macaroon": "Challenge body includes both a token and a macaroon",
     "headers_or_challenge": "Payment required; retry with Authorization: L402 token:preimage",
     "sdk_or_endpoint": "/api/l402/onchain_fee at price_sats 50; llms.txt lists 25+ endpoints from 5 to 500 sats"
    },
    "telemetry": {
     "snapshot_http_status": 200,
     "body_error": "payment_required",
     "price_sats": 50,
     "has_macaroon": true,
     "has_bolt11_invoice": true,
     "has_token": true
    },
    "source_url": "https://lightningfaucet.com/llms.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://lightningfaucet.com/llms.txt",
  "note": "Pay-per-call seller; `onchain_fee` probe is `price_sats` 50."
 },
 {
  "id": "lightning-labs-aperture",
  "org_id": "lightning-labs",
  "name": "Lightning Labs",
  "url": "https://lightning.engineering",
  "type": "origin",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Lightning Labs (Lightning Loop & Aperture)",
    "role": "Seller & reverse proxy (Originator)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-25",
    "col4_md": "Aperture `v0.5.0` proxies L402 in Loop and Pool, merging LSAT and Payment on one 402.",
    "full_detail_md": "Aperture is a reverse HTTP proxy that obtains a macaroon, sends it with a Lightning invoice and HTTP status code 402, implements both the L402 and MPP specifications, and is used in production in Lightning Loop and Pool. Release v0.5.0, published 2026-03-25, merges WWW-Authenticate headers so one 402 can advertise LSAT, L402, and Payment challenges, and Loop's client delegates token acquisition and stream authentication to Aperture.",
    "facets": {
     "settlement_rail": "Lightning Network BOLT 11 invoice collected by the Aperture reverse proxy",
     "token_or_macaroon": "Macaroon sent together with the Lightning invoice; v0.5.0 also advertises the LSAT scheme name",
     "headers_or_challenge": "HTTP status code 402 with WWW-Authenticate; v0.5.0 merges LSAT, L402, and Payment challenges onto one 402",
     "sdk_or_endpoint": "lightninglabs/aperture v0.5.0; Loop delegates token acquisition and stream authentication to Aperture"
    },
    "telemetry": null,
    "source_url": "https://docs.lightning.engineering/lightning-network-tools/aperture"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.lightning.engineering/lightning-network-tools/aperture",
  "note": "Aperture `v0.5.0` proxies L402 in Loop and Pool, merging LSAT and Payment on one 402."
 },
 {
  "id": "lightning-labs-clients",
  "org_id": "lightning-labs",
  "name": "Lightning Labs",
  "url": "https://lightning.engineering",
  "type": "sdk",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Lightning Labs (lnget, L402sdk, LangChainBitcoin)",
    "role": "Client CLI & SDKs (Originator)",
    "status": "Partial",
    "status_display": "Partial · as of 2026-02",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02",
    "col4_md": "lnget handles HTTP 402; L402sdk and LangChainBitcoin are client libraries.",
    "full_detail_md": "The February 11, 2026 Lightning Labs post includes lnget, and the main-branch README says it pays an HTTP 402 L402 challenge after checking --max-cost, then stores the macaroon and preimage. L402sdk is a Rust client SDK with TypeScript and Python bindings, and LangChainBitcoin (pushed 2024-07-03) lets LangChain agents traverse L402 APIs; the lnget mechanism file is unreleased main, so this row stays Partial.",
    "facets": {
     "settlement_rail": "Lightning invoice paid by lnget's configured Lightning backend",
     "token_or_macaroon": "Stored token is the macaroon plus the payment preimage",
     "headers_or_challenge": "HTTP 402 with WWW-Authenticate: L402 macaroon and invoice, gated by --max-cost",
     "sdk_or_endpoint": "lnget CLI (announced 2026-02-11, mechanism on main); L402sdk; LangChainBitcoin pushed 2024-07-03"
    },
    "telemetry": null,
    "source_url": "https://lightning.engineering/posts/2026-02-11-ln-agent-tools/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://lightning.engineering/posts/2026-02-11-ln-agent-tools/",
  "note": "lnget handles HTTP 402; L402sdk and LangChainBitcoin are client libraries."
 },
 {
  "id": "lightning-wallet-mcp",
  "org_id": "lightning-faucet",
  "name": "Lightning Faucet",
  "url": "https://github.com/lightningfaucet/lightning-wallet-mcp",
  "type": "authority",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Lightning Faucet (lightning-wallet-mcp)",
    "role": "Custodial agent wallet",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Custodial main-branch wallet; `pay_invoice` returns a BOLT11 preimage.",
    "full_detail_md": "lightning-wallet-mcp is a custodial MCP wallet whose pay_invoice tool pays a BOLT11 invoice and returns the preimage, and the agent can pay L402 and X402 APIs through tool calls. The description lives on the repository main branch, so the row is Partial rather than a release-tag grade.",
    "facets": {
     "settlement_rail": "Custodial Lightning wallet paying BOLT11 invoices",
     "token_or_macaroon": "pay_invoice returns the preimage used to complete L402",
     "headers_or_challenge": "Pays L402 and X402 APIs, including endpoints that answer HTTP 402",
     "sdk_or_endpoint": "lightningfaucet/lightning-wallet-mcp on main; tool pay_invoice"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/lightningfaucet/lightning-wallet-mcp/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/lightningfaucet/lightning-wallet-mcp/main/README.md",
  "note": "Custodial main-branch wallet; `pay_invoice` returns a BOLT11 preimage."
 },
 {
  "id": "linear-as-meta",
  "org_id": "linear",
  "name": "Linear MCP authorization server",
  "url": "https://mcp.linear.app",
  "type": "authority",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Linear",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`issuer` `https://mcp.linear.app`; `S256`; `authorization_code`, `refresh_token`, `jwt-bearer` (`id-jag`); `client_id_metadata_document_supported` `true`; `resource_metadata`.",
    "full_detail_md": "GET https://mcp.linear.app/.well-known/oauth-authorization-server returned HTTP 200 `application/json`. `issuer` is `https://mcp.linear.app`. `client_id_metadata_document_supported` is `true`. `code_challenge_methods_supported` is `S256`. `grant_types_supported` includes `authorization_code`, `refresh_token`, and `urn:ietf:params:oauth:grant-type:jwt-bearer`, and `authorization_grant_profiles_supported` includes `urn:ietf:params:oauth:grant-profile:id-jag`. The document also sets `resource` to `https://mcp.linear.app/mcp` and `resource_metadata` to `https://mcp.linear.app/.well-known/oauth-protected-resource/mcp`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.linear.app/.well-known/oauth-authorization-server (issuer https://mcp.linear.app; resource https://mcp.linear.app/mcp; resource_metadata https://mcp.linear.app/.well-known/oauth-protected-resource/mcp)",
     "registration_or_client_id_modes": "registration_endpoint https://mcp.linear.app/register; client_id_metadata_document_supported true; token_endpoint_auth_methods client_secret_basic, client_secret_post, none",
     "pkce_or_grant_types": "PKCE S256; grants authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:jwt-bearer; authorization_grant_profiles_supported urn:ietf:params:oauth:grant-profile:id-jag",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://mcp.linear.app",
     "client_id_metadata_document_supported": true
    },
    "source_url": "https://mcp.linear.app/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.linear.app/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://mcp.linear.app`; `S256`; `authorization_code`, `refresh_token`, `jwt-bearer` (`id-jag`); `client_id_metadata_document_supported` `true`; `resource_metadata`."
 },
 {
  "id": "linear-mcp",
  "org_id": "linear",
  "name": "Linear MCP Server",
  "url": "https://mcp.linear.app/mcp",
  "type": "origin",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Linear",
    "role": "Remote MCP server",
    "status": "Live (HTTP 401)",
    "status_display": "Live (HTTP 401) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Streamable HTTP at `https://mcp.linear.app/mcp` with OAuth 2.1 `resource_metadata` challenge and `https://mcp.linear.app/mcp/readonly`.",
    "full_detail_md": "Linear provides a Streamable HTTP MCP server at `https://mcp.linear.app/mcp` (and read-only endpoint `https://mcp.linear.app/mcp/readonly`) that returns HTTP 401 with `WWW-Authenticate: Bearer realm=\"OAuth\", resource_metadata=\"https://mcp.linear.app/.well-known/oauth-protected-resource/mcp\", scope=\"read write\"` and also accepts Linear API keys.",
    "facets": {
     "transport": "Streamable HTTP",
     "auth_or_oauth": "OAuth 2.1 (read/write scopes), Linear API key (Bearer)",
     "primitives": "tools",
     "sdk_or_package": "https://mcp.linear.app/mcp"
    },
    "telemetry": {
     "http_status": 401,
     "www_authenticate_scheme": "Bearer",
     "scope": "read write"
    },
    "source_url": "https://mcp.linear.app/mcp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mcp.linear.app/mcp",
  "note": "Streamable HTTP at `https://mcp.linear.app/mcp` with OAuth 2.1 `resource_metadata` challenge and `https://mcp.linear.app/mcp/readonly`."
 },
 {
  "id": "linear-mcp-as",
  "org_id": "linear",
  "name": "Linear MCP",
  "url": "https://mcp.linear.app",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Linear",
    "role": "MCP authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`https://mcp.linear.app/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://mcp.linear.app`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. `client_id_metadata_document_supported` is true.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "issuer": "https://mcp.linear.app",
     "grant_profile": "urn:ietf:params:oauth:grant-profile:id-jag"
    },
    "source_url": "https://mcp.linear.app/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mcp.linear.app/.well-known/oauth-authorization-server",
  "note": "`https://mcp.linear.app/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://mcp.linear.app`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. `client_id_metadata_document_supported` is true."
 },
 {
  "id": "link-springer-com",
  "org_id": "springer-nature",
  "name": "Springer Nature",
  "url": "https://link.springer.com/.well-known/tdmrep.json",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Springer Nature",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Well-known `tdmrep.json` (HTTP 200, `application/json`, checked 2026-10-30) sets `location` `/`, `tdm-reservation` 1, and `tdm-policy` `https://dev.springernature.com/tdm/SNTDMPolicy.json`. The adopters list records Springer Nature (https://www.springernature.com/) as tdmrep.json, with a policy.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "attachment": "well-known",
     "location": "/",
     "tdm_reservation": 1,
     "tdm_policy": "https://dev.springernature.com/tdm/SNTDMPolicy.json"
    },
    "source_url": "https://link.springer.com/.well-known/tdmrep.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://link.springer.com/.well-known/tdmrep.json",
  "note": "Well-known `tdmrep.json` (HTTP 200, `application/json`, checked 2026-10-30) sets `location` `/`, `tdm-reservation` 1, and `tdm-policy` `https://dev.springernature.com/tdm/SNTDMPolicy.json`. The adopters list records Springer Nature (https://www.springernature.com/) as tdmrep.json, with a policy."
 },
 {
  "id": "linktree",
  "org_id": "linktree",
  "name": "Linktree",
  "url": "https://linktr.ee/robots.txt",
  "type": "origin",
  "implements": [
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Linktree",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "`https://linktr.ee/robots.txt` returned status 200 on 2026-10-29 with a Content Signals policy comment, then a two-signal line inside named-crawler groups. Example: `User-agent: GPTBot` / `Content-Signal: ai-train=no, search=yes`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://linktr.ee/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://linktr.ee/robots.txt",
  "note": "`https://linktr.ee/robots.txt` returned status 200 on 2026-10-29 with a Content Signals policy comment, then a two-signal line inside named-crawler groups. Example: `User-agent: GPTBot` / `Content-Signal: ai-train=no, search=yes`."
 },
 {
  "id": "llamaindex",
  "org_id": "llamaindex",
  "name": "LlamaIndex",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LlamaIndex",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists LlamaIndex as Supported under Agent Framework - 1st Party, with Docs and Demos.",
    "full_detail_md": "The AG-UI overview lists LlamaIndex as Supported under Agent Framework - 1st Party, with Docs and Demos. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "1st-party agent framework (directory listing)",
     "sdk_or_package": "Not named; Docs and Demos only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "Overview lists LlamaIndex as Supported under Agent Framework - 1st Party, with Docs and Demos."
 },
 {
  "id": "llm-wiki-compiler",
  "org_id": "atomicstrata",
  "name": "llm-wiki-compiler",
  "url": "https://github.com/atomicstrata/llm-wiki-compiler/releases/tag/v0.10.0",
  "type": "sdk",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "llm-wiki-compiler (atomicstrata)",
    "role": "Compiler",
    "status": "Supported",
    "status_display": "Supported · as of 2026-06-14",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-14",
    "col4_md": "Release `v0.10.0` adds an OKF export/import round-trip.",
    "full_detail_md": "GitHub release v0.10.0, with published_at 2026-06-14T23:58:57Z, adds a review-policy gate for generated knowledge, a full Open Knowledge Format (OKF) export/import round-trip, and a Mintlify documentation site.",
    "facets": {
     "artifact_or_endpoint": "https://github.com/atomicstrata/llm-wiki-compiler/releases/tag/v0.10.0",
     "content_type_or_schema": "OKF export/import round-trip of a knowledge directory",
     "discovery_mechanism": "GitHub release notes for tag v0.10.0",
     "version_or_posture": "Release tag v0.10.0 published 2026-06-14; the notes do not name spec version 0.2"
    },
    "telemetry": null,
    "source_url": "https://github.com/atomicstrata/llm-wiki-compiler/releases/tag/v0.10.0"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/atomicstrata/llm-wiki-compiler/releases/tag/v0.10.0",
  "note": "Release `v0.10.0` adds an OKF export/import round-trip."
 },
 {
  "id": "lm-studio",
  "org_id": "lmstudio",
  "name": "LM Studio",
  "url": "https://lmstudio.ai/blog/openresponses",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LM Studio",
    "role": "Local inference engine",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-15",
    "col4_md": "LM Studio `0.3.39` (`2026-01-15`) makes local `/v1/responses` match the specification.",
    "full_detail_md": "LM Studio 0.3.39 (datePublished 2026-01-15) makes the local /v1/responses endpoint compatible with the Open Responses specification. The post says LM Studio partnered with OpenAI for that support and tells readers to update to LM Studio 0.3.39.",
    "facets": {
     "endpoint_or_route": "local /v1/responses",
     "streaming_or_items": "The post describes streaming results in the Open Responses tooling layer",
     "tool_or_state_model": "Shared schema and tooling layer; the post does not name a conversation id",
     "sdk_or_version": "LM Studio 0.3.39, datePublished 2026-01-15"
    },
    "telemetry": null,
    "source_url": "https://lmstudio.ai/blog/openresponses"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://lmstudio.ai/blog/openresponses",
  "note": "LM Studio `0.3.39` (`2026-01-15`) makes local `/v1/responses` match the specification."
 },
 {
  "id": "lovable-oauth-as",
  "org_id": "lovable",
  "name": "Lovable OAuth",
  "url": "https://lovable.dev",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Lovable",
    "role": "OAuth authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`https://lovable.dev/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://lovable.dev/oauth`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. `client_id_metadata_document_supported` is true.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "issuer": "https://lovable.dev/oauth",
     "grant_profile": "urn:ietf:params:oauth:grant-profile:id-jag"
    },
    "source_url": "https://lovable.dev/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://lovable.dev/.well-known/oauth-authorization-server",
  "note": "`https://lovable.dev/.well-known/oauth-authorization-server` returned HTTP 200. Issuer `https://lovable.dev/oauth`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`. `client_id_metadata_document_supported` is true."
 },
 {
  "id": "lynx-genui",
  "org_id": "lynx",
  "name": "@lynx-js/genui",
  "url": "https://registry.npmjs.org/@lynx-js/genui",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Lynx GenUI",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Roadmap: Stable ReactLynx renderer for `v0.9`. npm `@lynx-js/genui` `0.7.2` depends on `@a2ui/web_core`. ByteDance's Lynx renderer supports A2UI 0.9 today and is adapting to 1.0.",
    "full_detail_md": "The roadmap marks Lynx Stable on mobile, web, and desktop and calls it a ReactLynx renderer for A2UI v0.9. The npm registry record for @lynx-js/genui lists latest 0.7.2 at 2026-10-30T15:19:31.225Z, described as Generative UI for Lynx, with dependency @a2ui/web_core 0.9.1.",
    "facets": {
     "transport_or_binding": "ReactLynx renderer for A2UI v0.9",
     "component_or_catalog": "Depends on published @a2ui/web_core 0.9.1",
     "spec_version": "Roadmap Stable for A2UI v0.9; npm 0.7.2 published 2026-10-30",
     "sdk_or_renderer": "@lynx-js/genui 0.7.2"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/roadmap/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2ui.org/roadmap/",
  "note": "Roadmap: Stable ReactLynx renderer for `v0.9`. npm `@lynx-js/genui` `0.7.2` depends on `@a2ui/web_core`. ByteDance's Lynx renderer supports A2UI 0.9 today and is adapting to 1.0."
 },
 {
  "id": "m365-copilot",
  "org_id": "microsoft",
  "name": "Microsoft 365 Copilot",
  "url": "https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-mcp-apps",
  "type": "harness",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Microsoft 365 Copilot",
    "role": "AI host",
    "status": "Partial",
    "status_display": "Partial · as of 2026-09-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-30",
    "col4_md": "Learn page updated 2026-09-30: widgets in Copilot, not every Apps SDK capability.",
    "full_detail_md": "Microsoft Learn, last updated 2026-09-30, says MCP apps are interactive UI widgets that run inside Microsoft 365 Copilot, powered by MCP servers. Copilot supports both the MCP Apps standard and the ChatGPT-specific Apps SDK additions, though not all capabilities are available, so the grade stays Partial.",
    "facets": {
     "transport_or_channel": "MCP apps run inside Microsoft 365 Copilot, powered by MCP servers",
     "ui_resource_or_primitive": "Interactive UI widgets; both the MCP Apps standard and ChatGPT Apps SDK additions",
     "sandbox_or_security": "Learn page does not claim every Apps SDK capability; unsupported extras stay out of a full grade",
     "sdk_or_version": "Microsoft Learn last updated 2026-09-30; partial coverage of Apps SDK additions"
    },
    "telemetry": null,
    "source_url": "https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-mcp-apps"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/plugin-mcp-apps",
  "note": "Learn page updated 2026-09-30: widgets in Copilot, not every Apps SDK capability."
 },
 {
  "id": "mailbox-bot",
  "org_id": "mailbox-bot",
  "name": "mailbox.bot",
  "url": "https://mailbox.bot/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "mailbox.bot",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://mailbox.bot/auth.md describes registration for the postal-mail API. Protected resources are under https://mailbox.bot/api. Authorization-server metadata sets current_flow user_claimed_email_required, identity_types_supported identity_assertion, and anonymous.enabled false, because an order spends prepaid credits. The agent can request a human-approved claim by email.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://mailbox.bot/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://mailbox.bot/auth.md",
  "note": "https://mailbox.bot/auth.md describes registration for the postal-mail API. Protected resources are under https://mailbox.bot/api. Authorization-server metadata sets current_flow user_claimed_email_required, identity_types_supported identity_assertion, and anonymous.enabled false, because an order spends prepaid credits. The agent can request a human-approved claim by email."
 },
 {
  "id": "makigas",
  "org_id": "makigas",
  "name": "makigas",
  "url": "https://www.makigas.es/ai.txt",
  "type": "origin",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "makigas",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, per-extension `Disallow:` list).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.makigas.es/ai.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.makigas.es/ai.txt",
  "note": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, per-extension `Disallow:` list)."
 },
 {
  "id": "mastercard",
  "org_id": "mastercard",
  "name": "Mastercard",
  "url": "https://www.mastercard.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Mastercard",
    "role": "Payment network (endorser)",
    "status": "Listed",
    "status_display": "Listed · as of 2026-01-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-11",
    "col4_md": "Launch-post endorser on 2026-01-11; no handler id in that sentence.",
    "full_detail_md": "Mastercard is named in the launch post (datePublished 2026-01-11) among more than 20 ecosystem endorsers: Adyen, American Express, Best Buy, Flipkart, Macy's Inc., Mastercard, Stripe, The Home Depot, Visa and Zalando. That sentence does not publish a Mastercard payment handler or a merchant profile.",
    "facets": {
     "commerce_surface": "Named ecosystem endorser in the 2026-01-11 launch post",
     "payment_handlers_or_rail": "No payment-handler id in the launch endorsement sentence",
     "transport_bindings": "No transport binding in the launch endorsement sentence",
     "spec_version": "Article datePublished 2026-01-11, not a ucp.version pin and not a registry Live grade"
    },
    "telemetry": null,
    "source_url": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/",
  "note": "Launch-post endorser on 2026-01-11; no handler id in that sentence."
 },
 {
  "id": "mastodon",
  "org_id": "mastodon",
  "name": "Mastodon",
  "url": "https://docs.joinmastodon.org/spec/security/",
  "type": "origin",
  "implements": [
   "http-message-signatures"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Mastodon",
    "role": "Fediverse verifier & fallback signer",
    "status": "Partial",
    "status_display": "Partial · as of 2026-08-20",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-20",
    "col4_md": "`v4.4.0` added experimental inbound verification behind `http_message_signatures`; `v4.5.0`+ enables it unconditionally; `v4.7.0` adds `Ed25519` validation and outgoing `RFC9421` signatures as a fallback to `draft-cavage-http-signatures`.",
    "full_detail_md": "Mastodon added experimental inbound RFC 9421 verification (`rsa-v1_5-sha256` covering `@method`, `@target-uri`, and RFC 9530 `Content-Digest` with `created` and `keyid`) behind the `http_message_signatures` feature flag in v4.4.0 (2025-07-08), enabled inbound RFC 9421 verification unconditionally in v4.5.0 (2025-11-06), and added `Ed25519` validation plus outgoing RFC 9421 signatures as a fallback to legacy `draft-cavage-http-signatures` in v4.7.0 (2026-08-20).",
    "facets": {
     "profile_or_spec_target": "ActivityPub / Fediverse profile of RFC 9421 alongside legacy `draft-cavage-http-signatures`",
     "signature_fields": "`Signature` and `Signature-Input` covering `@method`, `@target-uri`, and `Content-Digest` with `created` and `keyid`",
     "algorithms_or_keys": "`rsa-v1_5-sha256` (v4.4.0+) and `Ed25519` (v4.7.0+)",
     "verification_posture": "Fediverse server verifier (unconditional inbound verification in v4.5.0+; outgoing fallback signer in v4.7.0+)"
    },
    "telemetry": null,
    "source_url": "https://docs.joinmastodon.org/spec/security/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.joinmastodon.org/spec/security/",
  "note": "`v4.4.0` added experimental inbound verification behind `http_message_signatures`; `v4.5.0`+ enables it unconditionally; `v4.7.0` adds `Ed25519` validation and outgoing `RFC9421` signatures as a fallback to `draft-cavage-http-signatures`."
 },
 {
  "id": "mastra",
  "org_id": "mastra",
  "name": "Mastra",
  "url": "https://mastra.ai/integrations/agentic-ui/copilotkit",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Mastra",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`@ag-ui/mastra` exposes Mastra agents; `registerCopilotKit()` adds the CopilotKit route.",
    "full_detail_md": "CopilotKit talks to Mastra through the AG-UI protocol. The `@ag-ui/mastra` package exposes Mastra agents as an AG-UI endpoint, `registerCopilotKit()` adds the CopilotKit route, and the overview lists Mastra as Supported, with Docs and Demos.",
    "facets": {
     "transport": "AG-UI endpoint exposed for CopilotKit",
     "event_or_state_model": "AG-UI protocol between CopilotKit and Mastra agents",
     "integration_role": "Agent framework endpoint",
     "sdk_or_package": "@ag-ui/mastra and registerCopilotKit()"
    },
    "telemetry": null,
    "source_url": "https://mastra.ai/integrations/agentic-ui/copilotkit"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://mastra.ai/integrations/agentic-ui/copilotkit",
  "note": "`@ag-ui/mastra` exposes Mastra agents; `registerCopilotKit()` adds the CopilotKit route."
 },
 {
  "id": "mcp-census-compare",
  "org_id": "mcp-census",
  "name": "MCP Census registry comparison",
  "url": "https://mcpcensus.com/compare/mcp-registries",
  "type": "authority",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "MCP Census",
    "role": "Trust-layer census over registries",
    "status": "Listed",
    "status_display": "Listed · as of 2026-11-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-11-04",
    "col4_md": "Trust layer returning PASS, REVIEW, BLOCK, or UNKNOWN; `57,777` rows.",
    "full_detail_md": "The 4 November 2026 comparison reads Glama at 115,336 servers (Remote 45,340, Local 43,442), PulseMCP at 21,602, and the Docker MCP Catalog at 300+. Smithery's API, Connect, accounts, CLI, and proxy URLs stopped on 31 October 2026. MCP Census does not host the servers it scores.",
    "facets": {
     "transport": "Read-only comparison of public registry pages",
     "auth_or_oauth": "No hosting; trust decision PASS, REVIEW, BLOCK, or UNKNOWN",
     "primitives": "57,777 server rows on the 4 November 2026 read",
     "sdk_or_package": "https://mcpcensus.com/compare/mcp-registries"
    },
    "telemetry": null,
    "source_url": "https://mcpcensus.com/compare/mcp-registries"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://mcpcensus.com/compare/mcp-registries",
  "note": "Trust layer returning PASS, REVIEW, BLOCK, or UNKNOWN; `57,777` rows."
 },
 {
  "id": "mcp-csharp-sdk-cimd",
  "org_id": "modelcontextprotocol",
  "name": "MCP C# SDK",
  "url": "https://csharp.sdk.modelcontextprotocol.io/v2/api/ModelContextProtocol.Authentication.ClientOAuthOptions.html",
  "type": "sdk",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "MCP C# SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`ClientMetadataDocumentUri` is sent as the client identifier when the flag is true.",
    "full_detail_md": "`ClientMetadataDocumentUri` is the HTTPS URL of the client's metadata document. When it is set and authorization-server metadata reports `client_id_metadata_document_supported` true, the OAuth client sends that URL as the client identifier instead of performing dynamic client registration.",
    "facets": {
     "metadata_flag_or_profile": "ClientMetadataDocumentUri holds the HTTPS URL of this client's metadata document",
     "auth_method_or_pkce": "When client_id_metadata_document_supported is true, that URL is sent as the client identifier instead of dynamic client registration",
     "uri_or_ssrf_rules": "The property is documented as an HTTPS URL; the API page does not add a separate SSRF rule",
     "draft_or_spec_version": "Undated C# SDK API documentation, not a floating main-branch source file"
    },
    "telemetry": null,
    "source_url": "https://csharp.sdk.modelcontextprotocol.io/v2/api/ModelContextProtocol.Authentication.ClientOAuthOptions.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://csharp.sdk.modelcontextprotocol.io/v2/api/ModelContextProtocol.Authentication.ClientOAuthOptions.html",
  "note": "`ClientMetadataDocumentUri` is sent as the client identifier when the flag is true."
 },
 {
  "id": "mcp-inspector",
  "org_id": "modelcontextprotocol",
  "name": "MCP Inspector",
  "url": "https://modelcontextprotocol.io/docs/tools/inspector",
  "type": "harness",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "MCP Inspector",
    "role": "Developer testing client",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-28",
    "col4_md": "Reference `@modelcontextprotocol/inspector` package providing Web, `--cli`, and `--tui` clients across `stdio` and HTTP for `2026-07-28`.",
    "full_detail_md": "The official `@modelcontextprotocol/inspector` package (and experimental `mcpdo` persistent connection client) provides Web, `--cli`, and `--tui` debugging clients over a shared core supporting `stdio` and remote HTTP transports, OAuth state persistence, and both legacy handshake and modern `2026-07-28` protocol negotiation.",
    "facets": {
     "transport": "stdio, Streamable HTTP",
     "auth_or_oauth": "On-disk OAuth state and per-launch Web UI token",
     "primitives": "tools, resources, prompts",
     "sdk_or_package": "@modelcontextprotocol/inspector"
    },
    "telemetry": null,
    "source_url": "https://modelcontextprotocol.io/docs/tools/inspector"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://modelcontextprotocol.io/docs/tools/inspector",
  "note": "Reference `@modelcontextprotocol/inspector` package providing Web, `--cli`, and `--tui` clients across `stdio` and HTTP for `2026-07-28`."
 },
 {
  "id": "mcp-llms-txt",
  "org_id": "modelcontextprotocol",
  "name": "Model Context Protocol",
  "url": "https://modelcontextprotocol.io/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Model Context Protocol",
    "role": "Specification & docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://modelcontextprotocol.io/llms.txt` (`# Model Context Protocol`, `text/plain`), indexing versioned `2026-07-28` specification and SDK `.md` pages.",
    "full_detail_md": "Serves `https://modelcontextprotocol.io/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 51,627 bytes, fetched 2026-11-04) via Mintlify, opening `# Model Context Protocol` and indexing versioned `.md` specification, architecture, server/client concept, and agent-skills documentation under `/docs/2026-07-28/`.",
    "facets": {
     "artifact_path": "https://modelcontextprotocol.io/llms.txt",
     "companion_files": "Versioned .md documentation pages under /docs/2026-07-28/",
     "content_type_or_bytes": "text/plain; charset=utf-8 (51,627 bytes)",
     "generator_or_consumer_mode": "Mintlify-generated root specification and documentation index"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Model Context Protocol"
    },
    "source_url": "https://modelcontextprotocol.io/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://modelcontextprotocol.io/llms.txt",
  "note": "Serves `https://modelcontextprotocol.io/llms.txt` (`# Model Context Protocol`, `text/plain`), indexing versioned `2026-07-28` specification and SDK `.md` pages."
 },
 {
  "id": "mcp-official-registry",
  "org_id": "modelcontextprotocol",
  "name": "Official MCP Registry",
  "url": "https://modelcontextprotocol.io/registry/about",
  "type": "venue",
  "implements": [
   "mcp",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Official MCP Registry",
    "role": "Central metadata repository",
    "status": "Supported (preview)",
    "status_display": "Supported (preview) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Official `server.json` catalog (`GET /v0.1/servers`) at `https://registry.modelcontextprotocol.io` for downstream aggregators.",
    "full_detail_md": "Official centralized metadata repository for publicly accessible MCP servers (`https://registry.modelcontextprotocol.io`), storing `server.json` records and exposing an unauthenticated read-only REST API (`GET /v0.1/servers`, `GET /v0.1/servers/{serverName}/versions/latest`) intended primarily for downstream aggregators and marketplaces while in preview.",
    "facets": {
     "transport": "REST API (GET /v0.1/servers)",
     "auth_or_oauth": "Unauthenticated read-only REST API",
     "primitives": "server.json metadata records",
     "sdk_or_package": "https://registry.modelcontextprotocol.io"
    },
    "telemetry": null,
    "source_url": "https://modelcontextprotocol.io/registry/about"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Official MCP Registry",
    "role": "Upstream public registry",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-11",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-11",
    "as_of": "2026-11-10",
    "col4_md": "Live `/v0.1/version` endpoint reports `\"version\": \"1.8.9\"` built at `2026-11-10T11:14:06Z` from commit `ba94f65`; serves `/v0.1/servers` with `2025-12-11` schema entries.",
    "full_detail_md": "HTTP 200 `application/json` from `/v0.1/version` reports `1.8.9`, built `2026-11-10T11:14:06Z` from commit `ba94f657e1ecd4ddff11baa25ad84cda26c2b854`. The MCP Registry is currently in preview and is the official centralized metadata repository for publicly accessible MCP servers. The OpenAPI document is `3.1.0` and defines `/v0.1/servers` as a paginated list with one record per server version.",
    "facets": {
     "registry_or_namespace": "Official MCP Registry at registry.modelcontextprotocol.io",
     "api_or_schema_version": "Service 1.8.9; REST API /v0.1/; OpenAPI 3.1.0",
     "transport_or_package_types": "HTTPS unauthenticated read-only REST JSON",
     "verification_posture": "Live HTTP 200 probe of GET /v0.1/version (checked 2026-11-09, built 2026-11-06)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "version": "1.8.9"
    },
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/version"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://modelcontextprotocol.io/registry/about",
  "note": "Official `server.json` catalog (`GET /v0.1/servers`) at `https://registry.modelcontextprotocol.io` for downstream aggregators."
 },
 {
  "id": "mcp-official-sdks",
  "org_id": "modelcontextprotocol",
  "name": "Official MCP SDKs",
  "url": "https://modelcontextprotocol.io/docs/sdk",
  "type": "sdk",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Official MCP SDKs",
    "role": "Client & server SDKs",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Current `Tier 1` roster lists 6 official SDKs (`TypeScript`, `Python`, `C#`, `Go`, `Rust`, and `Ruby`), plus Tier 2 `Java` and Tier 3 `Kotlin`, `Swift`, and `PHP` (July 2026 release covered `TypeScript`, `Python`, `Go`, `C#`, and `Rust` beta). The official Ruby SDK reached Tier 1 on 2026-10-30, with full support for the 2026-07-28 specification and a 100% conformance pass rate across both scored spec versions.",
    "full_detail_md": "The 2026-07-28 specification release announcement named four Tier 1 SDKs supporting the stateless revision at launch (`TypeScript`, `Python`, `Go`, and `C#`, with `Rust` in beta). The current SDK documentation roster lists six Tier 1 SDKs (`TypeScript`, `Python`, `Go`, `C#`, `Rust`, and `Ruby`, plus Tier 2 `Java` and Tier 3 `Swift`, `PHP`, and `Kotlin`). On 2026-10-30 the maintainers promoted the official Ruby SDK to Tier 1, with full support for the 2026-07-28 specification and a 100% conformance pass rate across both scored spec versions.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1, CIMD, RFC 9207 issuer validation",
     "primitives": "tools, resources, prompts, server/discover, MRTR, subscriptions/listen",
     "sdk_or_package": "July 2026 `2026-07-28` release cohort: 4 Tier 1 SDKs (`TypeScript`, `Python`, `Go`, `C#`) + `Rust` (beta); current docs roster lists 6 Tier 1 SDKs (`TypeScript`, `Python`, `Go`, `C#`, `Rust`, `Ruby`); Ruby reached Tier 1 on 2026-10-30"
    },
    "telemetry": null,
    "source_url": "https://modelcontextprotocol.io/docs/sdk"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://modelcontextprotocol.io/docs/sdk",
  "note": "Current `Tier 1` roster lists 6 official SDKs (`TypeScript`, `Python`, `C#`, `Go`, `Rust`, and `Ruby`), plus Tier 2 `Java` and Tier 3 `Kotlin`, `Swift`, and `PHP` (July 2026 release covered `TypeScript`, `Python`, `Go`, `C#`, and `Rust` beta). The official Ruby SDK reached Tier 1 on 2026-10-30, with full support for the 2026-07-28 specification and a 100% conformance pass rate across both scored s"
 },
 {
  "id": "mcp-publisher",
  "org_id": "modelcontextprotocol",
  "name": "mcp-publisher",
  "url": "https://github.com/modelcontextprotocol/registry",
  "type": "sdk",
  "implements": [
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "mcp-publisher",
    "role": "Publisher CLI",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Official CLI (`brew install mcp-publisher`) authenticating via `mcp-publisher login github`, `github-oidc`, DNS, or `Ed25519`.",
    "full_detail_md": "Publishers install the CLI with `brew install mcp-publisher`. Login examples are `mcp-publisher login github`, `mcp-publisher login github-oidc`, and DNS login with `Ed25519`. GitHub Actions publishes with `./mcp-publisher login github-oidc` and no dedicated secret for GitHub OIDC authentication.",
    "facets": {
     "registry_or_namespace": "Official MCP Registry publisher CLI (modelcontextprotocol/registry)",
     "api_or_schema_version": "Publishes server.json to the official registry API",
     "transport_or_package_types": "CLI via brew install mcp-publisher; GitHub, GitHub OIDC, and Ed25519 DNS login",
     "verification_posture": "Document citation of the Nordic APIs guide, registry authentication docs, and GitHub Actions docs (checked 2026-10-30; docs undated)"
    },
    "telemetry": null,
    "source_url": "https://nordicapis.com/getting-started-with-the-official-mcp-registry-api/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://nordicapis.com/getting-started-with-the-official-mcp-registry-api/",
  "note": "Official CLI (`brew install mcp-publisher`) authenticating via `mcp-publisher login github`, `github-oidc`, DNS, or `Ed25519`."
 },
 {
  "id": "mcp-python-sdk-cimd",
  "org_id": "modelcontextprotocol",
  "name": "MCP Python SDK",
  "url": "https://py.sdk.modelcontextprotocol.io/client/oauth-clients/",
  "type": "sdk",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "MCP Python SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Passes `client_metadata_url`; skips `/register` when the flag is true.",
    "full_detail_md": "The MCP Python SDK documentation says to pass `client_metadata_url` when constructing the OAuth provider. When authorization-server metadata advertises `client_id_metadata_document_supported` true, the provider skips `/register` and sends that URL as `client_id`; when the flag is absent it falls back to dynamic registration.",
    "facets": {
     "metadata_flag_or_profile": "SDK option client_metadata_url; the URL is used as client_id when the server advertises the CIMD flag",
     "auth_method_or_pkce": "Skips /register when client_id_metadata_document_supported is true; otherwise falls back to dynamic registration. The page says there is no client_secret in the CIMD path",
     "uri_or_ssrf_rules": "The caller supplies the HTTPS metadata URL; this page does not add a separate SSRF rule",
     "draft_or_spec_version": "Undated Python SDK documentation page, not a raw main-branch source file, so it is not graded from floating main"
    },
    "telemetry": null,
    "source_url": "https://py.sdk.modelcontextprotocol.io/client/oauth-clients/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://py.sdk.modelcontextprotocol.io/client/oauth-clients/",
  "note": "Passes `client_metadata_url`; skips `/register` when the flag is true."
 },
 {
  "id": "mcp-ui",
  "org_id": "mcp-ui",
  "name": "mcp-ui",
  "url": "https://mcpui.dev/about",
  "type": "sdk",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "mcp-ui",
    "role": "Client and server SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Implements MCP Apps: `@mcp-ui/client` plus TypeScript, Python, and Ruby server SDKs.",
    "full_detail_md": "mcp-ui says it implements the MCP Apps standard, publishes a client SDK with React components (@mcp-ui/client), and publishes server SDKs for TypeScript, Python, and Ruby, under the Apache 2.0 License. The about page does not name a package version, so this row does not treat that undated page as a dated release snapshot.",
    "facets": {
     "transport_or_channel": "Client and server SDKs implementing the MCP Apps standard",
     "ui_resource_or_primitive": "React components in @mcp-ui/client for MCP Apps views",
     "sandbox_or_security": "About page does not restate CSP; it identifies mcp-ui as an implementation of the standard",
     "sdk_or_version": "Undated about page; @mcp-ui/client plus TypeScript, Python, and Ruby server SDKs; Apache 2.0"
    },
    "telemetry": null,
    "source_url": "https://mcpui.dev/about"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://mcpui.dev/about",
  "note": "Implements MCP Apps: `@mcp-ui/client` plus TypeScript, Python, and Ruby server SDKs."
 },
 {
  "id": "mcp2anp",
  "org_id": "mcp2anp",
  "name": "MCP2ANP",
  "url": "https://raw.githubusercontent.com/agent-network-protocol/mcp2anp/main/README.md",
  "type": "sdk",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "MCP2ANP",
    "role": "Messaging node / Server",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "MCP bridge exposing tools anp.fetchDoc and anp.invokeOpenRPC so an MCP host can discover and call remote ANP agents with did:wba credentials.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agent-network-protocol/mcp2anp/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/agent-network-protocol/mcp2anp/main/README.md",
  "note": "MCP bridge exposing tools anp.fetchDoc and anp.invokeOpenRPC so an MCP host can discover and call remote ANP agents with did:wba credentials."
 },
 {
  "id": "mcpb",
  "org_id": "modelcontextprotocol",
  "name": "MCP Bundles (MCPB)",
  "url": "https://raw.githubusercontent.com/modelcontextprotocol/mcpb/main/README.md",
  "type": "sdk",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "MCP Bundles (MCPB)",
    "role": "Local server bundle format",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Zip archive format (`.mcpb`, formerly `.dxt`) bundling a local MCP server with `manifest.json` via `@anthropic-ai/mcpb`.",
    "full_detail_md": "MCP Bundles (`.mcpb`, renamed from Desktop Extensions `.dxt`) package a local MCP server and `manifest.json` into a single-click installable zip archive built with the `@anthropic-ai/mcpb` CLI (`mcpb init` and `mcpb pack`) and loaded by Claude for macOS and Windows.",
    "facets": {
     "transport": "stdio (local bundled server)",
     "auth_or_oauth": "Host-managed environment variables and user configuration",
     "primitives": "tools, resources, prompts",
     "sdk_or_package": "@anthropic-ai/mcpb"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/modelcontextprotocol/mcpb/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/modelcontextprotocol/mcpb/main/README.md",
  "note": "Zip archive format (`.mcpb`, formerly `.dxt`) bundling a local MCP server with `manifest.json` via `@anthropic-ai/mcpb`."
 },
 {
  "id": "mcpjam",
  "org_id": "mcpjam",
  "name": "MCPJam",
  "url": "https://modelcontextprotocol.io/extensions/apps/overview",
  "type": "harness",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "MCPJam",
    "role": "AI host",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Named among supported MCP Apps hosts on the official MCP Apps overview.",
    "full_detail_md": "The MCP Apps overview page lists MCPJam among the clients that currently support MCP Apps alongside Claude, Claude Desktop, VS Code GitHub Copilot, Microsoft 365 Copilot, Goose, Postman, and Archestra.AI.",
    "facets": {
     "transport_or_channel": "Listed MCP Apps host on modelcontextprotocol.io",
     "ui_resource_or_primitive": "MCP Apps host support listed on the official overview page",
     "sandbox_or_security": "Overview listing does not specify host-specific sandbox flags",
     "sdk_or_version": "Undated MCP Apps overview page"
    },
    "telemetry": null,
    "source_url": "https://modelcontextprotocol.io/extensions/apps/overview"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://modelcontextprotocol.io/extensions/apps/overview",
  "note": "Named among supported MCP Apps hosts on the official MCP Apps overview."
 },
 {
  "id": "medium-rsl-robots",
  "org_id": "medium",
  "name": "Medium",
  "url": "https://medium.com/robots.txt",
  "type": "origin",
  "implements": [
   "rsl"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "rsl",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Medium",
    "role": "Publishing platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Publishes `License: https://medium.com/license.xml` in `text/plain` robots.txt.",
    "full_detail_md": "The robots.txt response is HTTP 200, content-type text/plain, content-length 884, and last-modified Wed, 04 Nov 2026 22:06:47 GMT. The body ends with Sitemap: https://medium.com/sitemap/sitemap.xml and License: https://medium.com/license.xml, and it does not include the license XML or a printed RSL spec version.",
    "facets": {
     "discovery_surface": "https://medium.com/robots.txt (text/plain, HTTP 200)",
     "xml_or_license_directive": "License: https://medium.com/license.xml",
     "usage_or_payment_terms": "Not stated in the robots.txt body; that body does not include the license XML",
     "spec_version": "Not printed in robots.txt. RSL 1.0's 2025-12-10 date is the spec publication date, not a date in this file"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain",
     "content_length": 884,
     "has_rsl_license_directive": true,
     "license_url": "https://medium.com/license.xml"
    },
    "source_url": "https://medium.com/robots.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://medium.com/robots.txt",
  "note": "Publishes `License: https://medium.com/license.xml` in `text/plain` robots.txt."
 },
 {
  "id": "memanto",
  "org_id": "memanto",
  "name": "Memanto",
  "url": "https://docs.memanto.ai/integrations/okf",
  "type": "origin",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Memanto",
    "role": "Agent memory",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-19",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-19",
    "col4_md": "Exports OKF v0.2; root `index.md` declares `okf_version: \"0.2\"`.",
    "full_detail_md": "Docs with dateModified 2026-10-19T20:26:14.549Z say Memanto exports OKF v0.2 bundles whose root index.md declares okf_version: \"0.2\", and that memanto migrate okf loads any OKF bundle into an agent. Unmapped fields stay in an x_memanto frontmatter block so a Memanto to OKF to Memanto round-trip keeps confidence, provenance, source, and the last-updated timestamp.",
    "facets": {
     "artifact_or_endpoint": "memanto memory export --okf and memanto migrate okf",
     "content_type_or_schema": "OKF v0.2 directory; root index.md okf_version 0.2; x_memanto extension block",
     "discovery_mechanism": "Memanto docs page modified 2026-10-19",
     "version_or_posture": "Documented OKF v0.2 export; dateModified 2026-10-19 is the page timestamp, not a schema date"
    },
    "telemetry": null,
    "source_url": "https://docs.memanto.ai/integrations/okf"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.memanto.ai/integrations/okf",
  "note": "Exports OKF v0.2; root `index.md` declares `okf_version: \"0.2\"`."
 },
 {
  "id": "meta-crawlers",
  "org_id": "meta",
  "name": "Meta web crawlers",
  "url": "https://web.archive.org/web/20260616005830id_/https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Meta",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-06-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-16",
    "col4_md": "`Meta-ExternalAgent` crawls for AI model training; `Meta-WebIndexer` indexes search; `Meta-ExternalFetcher` handles user fetches and may bypass `robots.txt`.",
    "full_detail_md": "`Meta-ExternalAgent` crawls for training foundation AI models or indexing content; the documented UA is `meta-externalagent/1.1`. `Meta-ExternalFetcher` fetches links at a user's request and may bypass robots.txt. `Meta-WebIndexer` improves Meta AI search. `FacebookExternalHit` crawls links shared on Meta's apps. The New York Times robots.txt also declares `User-agent: FacebookBot` with `Disallow: /`.",
    "facets": {
     "user_agent_token": [
      "Meta-ExternalAgent",
      "meta-externalagent/1.1",
      "Meta-ExternalFetcher",
      "Meta-WebIndexer",
      "FacebookExternalHit",
      "FacebookBot"
     ],
     "operator_purpose": "Meta-ExternalAgent: foundation AI training/indexing; Meta-WebIndexer: Meta AI search; Meta-ExternalFetcher: user-requested link fetches",
     "ip_verification_url": null,
     "robots_directives_honored": "Meta-ExternalAgent honors robots.txt; Meta-ExternalFetcher may bypass robots.txt"
    },
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20260616005830id_/https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://web.archive.org/web/20260616005830id_/https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/",
  "note": "`Meta-ExternalAgent` crawls for AI model training; `Meta-WebIndexer` indexes search; `Meta-ExternalFetcher` handles user fetches and may bypass `robots.txt`."
 },
 {
  "id": "metabind",
  "org_id": "metabind",
  "name": "Metabind",
  "url": "https://mcp.metabind.ai/ui",
  "type": "origin",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Metabind",
    "role": "MCP App server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Public `https://mcp.metabind.ai/ui` returned HTTP 200; use POST or `text/event-stream`.",
    "full_detail_md": "Metabind documents a public connector at https://mcp.metabind.ai/ui with the Metabind Component Kit built in (metrics, charts, tables, comparisons, lists, timelines, steps, and forms), needs no sign-in, and says drawing the views requires an MCP Apps host. That URL returned HTTP 200 telling the client to use POST for JSON-RPC or Accept text/event-stream for SSE, so the HTTP 200 grade is the transport probe rather than a rendered app or a registry record.",
    "facets": {
     "transport_or_channel": "Public connector https://mcp.metabind.ai/ui; HTTP 200 body asks for POST JSON-RPC or Accept text/event-stream",
     "ui_resource_or_primitive": "Metabind Component Kit views (metrics, charts, tables, comparisons, lists, timelines, steps, and forms)",
     "sandbox_or_security": "Public connector with no sign-in; drawing the views requires an MCP Apps host",
     "sdk_or_version": "Documented public connector; HTTP probe checked 2026-10-30"
    },
    "telemetry": {
     "http_status": 200,
     "accept_hint": "text/event-stream"
    },
    "source_url": "https://docs.metabind.ai/guides/getting-started/try-metabind"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.metabind.ai/guides/getting-started/try-metabind",
  "note": "Public `https://mcp.metabind.ai/ui` returned HTTP 200; use POST or `text/event-stream`."
 },
 {
  "id": "microsoft-agent-framework",
  "org_id": "microsoft",
  "name": "Microsoft Agent Framework",
  "url": "https://learn.microsoft.com/en-us/agent-framework/integrations/by-component/ui/ag-ui/",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Microsoft Agent Framework",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-25",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-25",
    "col4_md": "`MapAGUIServer` SSE adapter via `Microsoft.Agents.AI.Hosting.AGUI.AspNetCore` (`--prerelease`).",
    "full_detail_md": "The Agent Framework AG-UI integration connects agents to web clients and streams responses with Server-Sent Events (SSE): `MapAGUIServer` adapts the AG-UI request to MAF messages and converts the streaming response with the AG-UI.NET SDK, installed as `Microsoft.Agents.AI.Hosting.AGUI.AspNetCore` with `--prerelease`. The .NET 10 announcement on 2025-11-11 says Microsoft Agent Framework now supports the AG-UI protocol, the September 25th, 2026 SDK post says MAF AG-UI support for .NET is now based on the AG-UI.NET SDK, and the overview lists Microsoft Agent Framework as Supported.",
    "facets": {
     "transport": "Server-Sent Events (SSE)",
     "event_or_state_model": "AG-UI request mapped to MAF messages, then streamed back as AG-UI events",
     "integration_role": "Agent framework ASP.NET Core host",
     "sdk_or_package": "Microsoft.Agents.AI.Hosting.AGUI.AspNetCore (--prerelease), on the AG-UI.NET SDK"
    },
    "telemetry": null,
    "source_url": "https://learn.microsoft.com/en-us/agent-framework/integrations/by-component/ui/ag-ui/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://learn.microsoft.com/en-us/agent-framework/integrations/by-component/ui/ag-ui/",
  "note": "`MapAGUIServer` SSE adapter via `Microsoft.Agents.AI.Hosting.AGUI.AspNetCore` (`--prerelease`)."
 },
 {
  "id": "microsoft-copilot-accept",
  "org_id": "microsoft",
  "name": "Microsoft Copilot",
  "url": "https://acceptmarkdown.com/status",
  "type": "harness",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Microsoft Copilot",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-06-22",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-22",
    "col4_md": "Sends `Accept: text/markdown, text/html, */*` (verified 2026-06-22).",
    "full_detail_md": "AcceptMarkdown's client matrix, last updated 2026-06-22, records Microsoft Copilot as sending an Accept header that includes text/markdown. Verified date on that row is 2026-06-22.",
    "facets": {
     "negotiation_or_artifact": "Accept header includes text/markdown",
     "response_headers": "Accept: text/markdown, text/html, */*",
     "content_type_or_tokens": "Requests text/markdown",
     "verification_posture": "AcceptMarkdown matrix verified 2026-06-22; matrix last updated 2026-06-22"
    },
    "telemetry": null,
    "source_url": "https://acceptmarkdown.com/status"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://acceptmarkdown.com/status",
  "note": "Sends `Accept: text/markdown, text/html, */*` (verified 2026-06-22)."
 },
 {
  "id": "microsoft-copilot-studio",
  "org_id": "microsoft",
  "name": "Microsoft Copilot Studio",
  "url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-agent-to-agent",
  "type": "harness",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Microsoft (Copilot Studio)",
    "role": "Client orchestrator",
    "status": "Partial",
    "status_display": "Partial · as of 2026-08-26",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-26",
    "col4_md": "Delegates tasks via `message/send` (`contextId`) and auto-reads metadata from the legacy pre-v0.3 `/.well-known/agent.json` card path.",
    "full_detail_md": "Microsoft Copilot Studio (documentation updated 2026-08-26) delegates multi-turn tasks to external A2A agents using pre-v1.0 `message/send` payloads (carrying `contextId` and `copilotstudio.microsoft.com/a2a/chathistory` metadata) and automatically populates agent name and description from the endpoint's `.well-known` card, still referencing the pre-v0.3 `/.well-known/agent.json` path rather than the v0.3+ agent-card path.",
    "facets": {
     "transport_bindings": "HTTP JSON-RPC message/send and /v1/message:stream (pre-v1.0 operation naming)",
     "discovery_artifact": "Automatic metadata fetch from endpoint + /.well-known/agent.json (pre-v0.3 card path) or manual entry",
     "protocol_version": "Pre-v1.0 (uses message/send and /.well-known/agent.json path)",
     "auth_schemes": "None, API key (header or query parameter), or OAuth 2.0",
     "verification_posture": "Vendor technical documentation (updated 2026-08-26)"
    },
    "telemetry": null,
    "source_url": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-agent-to-agent"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://learn.microsoft.com/en-us/microsoft-copilot-studio/add-agent-agent-to-agent",
  "note": "Delegates tasks via `message/send` (`contextId`) and auto-reads metadata from the legacy pre-v0.3 `/.well-known/agent.json` card path."
 },
 {
  "id": "microsoft-entra-workload-id",
  "org_id": "microsoft",
  "name": "Entra Workload ID",
  "url": "https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-spiffe-spire",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Microsoft Entra Workload ID",
    "role": "Relying server / Gateway",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-13",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-13",
    "col4_md": "Exchanges a SPIFFE JWT-SVID for an Entra token without stored secrets or certificates.",
    "full_detail_md": "The workload exchanges its SPIFFE JWT-SVID for a Microsoft Entra access token and calls an Azure resource, such as Azure Blob Storage, without storing any secrets or certificates. The page was last updated on 2026-08-13.",
    "facets": {
     "svid_or_bundle_format": "Inbound SPIFFE JWT-SVID, exchanged for a Microsoft Entra access token.",
     "api_or_federation_surface": "Workload identity federation into Azure resources such as Azure Blob Storage.",
     "attestation_or_trust_domain": "Trusts the presented SPIFFE JWT-SVID. The workload stores no secrets or certificates.",
     "verification_posture": "Microsoft Learn documentation last updated on 2026-08-13."
    },
    "telemetry": null,
    "source_url": "https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-spiffe-spire"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-spiffe-spire",
  "note": "Exchanges a SPIFFE JWT-SVID for an Entra token without stored secrets or certificates."
 },
 {
  "id": "microsoft-foundry",
  "org_id": "microsoft",
  "name": "Microsoft Foundry",
  "url": "https://blog.modelcontextprotocol.io/posts/2026-07-28/",
  "type": "origin",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Microsoft Foundry",
    "role": "Enterprise agent platform",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-07-28",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-28",
    "col4_md": "Release announcement claims unified MCP endpoint with stateless `2026-07-28` and `Tasks`; no independent feature-matrix verification.",
    "full_detail_md": "Microsofts 2026-07-28 release announcement states that the Foundry toolbox exposes a unified MCP endpoint supporting stateless `2026-07-28` operations, the `Tasks` extension, and enterprise-managed identity; this reflects the vendors release-announcement statement rather than an independently tested feature matrix.",
    "facets": {
     "transport": "Streamable HTTP (vendor release-announcement claim)",
     "auth_or_oauth": "Enterprise-managed identity (vendor announcement)",
     "primitives": "tools, Tasks extension (announced; no independently tested feature matrix)",
     "sdk_or_package": "Microsoft Foundry toolbox (release announcement, 2026-07-28)"
    },
    "telemetry": null,
    "source_url": "https://blog.modelcontextprotocol.io/posts/2026-07-28/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.modelcontextprotocol.io/posts/2026-07-28/",
  "note": "Release announcement claims unified MCP endpoint with stateless `2026-07-28` and `Tasks`; no independent feature-matrix verification."
 },
 {
  "id": "microsoft-foundry-agent-service",
  "org_id": "microsoft",
  "name": "Foundry Agent Service",
  "url": "https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/agent-to-agent",
  "type": "origin",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Microsoft (Foundry Agent Service)",
    "role": "Client orchestrator & target",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-28",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-28",
    "col4_md": "GA `a2a` tool for `v1.0` `JSON-RPC` (text-only, no streaming) and preview `a2a_preview` tool for `v0.3`.",
    "full_detail_md": "Microsoft Foundry Agent Service (documentation updated 2026-10-28) provides the generally available `a2a` tool type (`A2ATool` or `A2AToolboxTool`) for A2A protocol version `1.0` over `JSON-RPC` alongside the preview `a2a_preview` tool type (`A2APreviewTool` or `A2APreviewToolboxTool`) for version `0.3`, resolving default Agent Cards anonymously or via `send_credentials_for_agent_card`; only text modality is supported, streaming responses are not supported, and `AgentOnBehalfOfUser` delegated authentication remains in preview.",
    "facets": {
     "transport_bindings": "JSON-RPC (text modality only; streaming responses not supported)",
     "discovery_artifact": "Automatic default Agent Card resolution (anonymous by default or authenticated via send_credentials_for_agent_card; /.well-known/agent-card.json for custom servers)",
     "protocol_version": "1.0 (GA via a2a / A2ATool) and 0.3 (Preview via a2a_preview / A2APreviewTool)",
     "auth_schemes": "None, custom-keys header (e.g. x-api-key), OAuth 2.0, calling agent identity, UserEntraToken, and preview AgentOnBehalfOfUser",
     "verification_posture": "Vendor technical documentation (updated 2026-10-28; text-only, no streaming, v0.3 and AgentOnBehalfOfUser in preview)"
    },
    "telemetry": null,
    "source_url": "https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/agent-to-agent"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://learn.microsoft.com/en-us/azure/foundry/agents/how-to/tools/agent-to-agent",
  "note": "GA `a2a` tool for `v1.0` `JSON-RPC` (text-only, no streaming) and preview `a2a_preview` tool for `v0.3`."
 },
 {
  "id": "microsoft-playwright-mcp",
  "org_id": "microsoft",
  "name": "Playwright MCP Server",
  "url": "https://github.com/microsoft/playwright-mcp",
  "type": "sdk",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Microsoft Playwright",
    "role": "Local MCP server",
    "status": "Listed",
    "status_display": "Listed · as of 2026-09-18",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-18",
    "col4_md": "Registry entry `io.github.microsoft/playwright-mcp` (`0.0.82`) distributing npm package `@playwright/mcp` over local `stdio`.",
    "full_detail_md": "Listed in the Official MCP Registry as `io.github.microsoft/playwright-mcp` v`0.0.82` (`Playwright Tools for MCP`), packaged on npm as `@playwright/mcp` v`0.0.82` using the local `stdio` transport for browser automation.",
    "facets": {
     "transport": "stdio",
     "auth_or_oauth": "Local process environment",
     "primitives": "tools, resources",
     "sdk_or_package": "@playwright/mcp v0.0.82"
    },
    "telemetry": null,
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.microsoft%2Fplaywright-mcp/versions/0.0.82"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.microsoft%2Fplaywright-mcp/versions/0.0.82",
  "note": "Registry entry `io.github.microsoft/playwright-mcp` (`0.0.82`) distributing npm package `@playwright/mcp` over local `stdio`."
 },
 {
  "id": "mindburn-labs",
  "org_id": "mindburn-labs",
  "name": "Mindburn Labs (helm-ai-kernel)",
  "url": "https://api.github.com/repos/Mindburn-Labs/helm-ai-kernel",
  "type": "sdk",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Mindburn Labs (helm-ai-kernel)",
    "role": "Audit emitter",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-22",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-22",
    "col4_md": "Mindburn-Labs/helm-ai-kernel describes a fail-closed execution firewall that quarantines MCP tools, proxies OpenAI-compatible requests, and emits signed receipts. Sharif's 2026-10-22 note to the IETF AUDIT list calls it an independent implementation of the AAT schema, JCS canonicalization, and the SHA-256 hash chain.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/repos/Mindburn-Labs/helm-ai-kernel"
   },
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Mindburn Labs (helm-ai-kernel)",
    "role": "Verifier / Audit parser",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-22",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-22",
    "col4_md": "The repository description says the firewall verifies EvidencePacks offline. Sharif's 2026-10-22 AUDIT list note calls the same tree an independent implementation of AAT JCS canonicalization and the SHA-256 hash chain, so the offline check is that chain.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/repos/Mindburn-Labs/helm-ai-kernel"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/repos/Mindburn-Labs/helm-ai-kernel",
  "note": "Mindburn-Labs/helm-ai-kernel describes a fail-closed execution firewall that quarantines MCP tools, proxies OpenAI-compatible requests, and emits signed receipts. Sharif's 2026-10-22 note to the IETF AUDIT list calls it an independent implementation of the AAT schema, JCS canonicalization, and the SHA-256 hash chain."
 },
 {
  "id": "mintlify",
  "org_id": "mintlify",
  "name": "Mintlify",
  "url": "https://mintlify.com/docs/llms.txt",
  "type": "origin",
  "implements": [
   "cloudflare-markdown-for-agents",
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Mintlify",
    "role": "Documentation engine",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Automatically generates `llms.txt`, `llms-full.txt`, and `.md` pages for hosted sites; serves `https://mintlify.com/docs/llms.txt` (`# Mintlify`, `text/plain`).",
    "full_detail_md": "Serves `https://mintlify.com/docs/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 26,385 bytes, fetched 2026-11-04) opening `# Mintlify` with `mint agent setup` instructions and localized OpenAPI specs (`/docs/openapi.json`, `/docs/admin-openapi.json`). Also documented on `llmstxt.org` as a documentation platform that automatically generates `llms.txt`, `llms-full.txt`, and Markdown page twins for every hosted site.",
    "facets": {
     "artifact_path": "https://mintlify.com/docs/llms.txt",
     "companion_files": "/llms-full.txt; /docs/openapi.json; /docs/admin-openapi.json; .md page twins",
     "content_type_or_bytes": "text/plain; charset=utf-8 (26,385 bytes)",
     "generator_or_consumer_mode": "Hosted documentation platform auto-generating /llms.txt and .md page twins"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Mintlify"
    },
    "source_url": "https://mintlify.com/docs/llms.txt"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Mintlify",
    "role": "Documentation platform",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Returns Markdown for `Accept: text/markdown` or `Accept: text/plain`.",
    "full_detail_md": "Mintlify documents that any page URL returns Markdown when the request sends Accept: text/markdown or Accept: text/plain, and that appending .md to a page URL shows the Markdown version. A missing Markdown page returns a 404 whose Markdown body links the documentation index (llms.txt) and llms-full.txt.",
    "facets": {
     "negotiation_or_artifact": "Accept: text/markdown or Accept: text/plain on any docs URL, plus a .md URL suffix",
     "response_headers": "Markdown body; missing pages return a Markdown 404 that links llms.txt",
     "content_type_or_tokens": "Markdown export of the page",
     "verification_posture": "Vendor documentation fetched 2026-11-06; live header not re-probed here"
    },
    "telemetry": null,
    "source_url": "https://www.mintlify.com/docs/ai/markdown-export"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://mintlify.com/docs/llms.txt",
  "note": "Automatically generates `llms.txt`, `llms-full.txt`, and `.md` pages for hosted sites; serves `https://mintlify.com/docs/llms.txt` (`# Mintlify`, `text/plain`)."
 },
 {
  "id": "mistral-crawlers",
  "org_id": "mistral",
  "name": "Mistral crawlers",
  "url": "https://docs.mistral.ai/robots",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Mistral",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`MistralAI-Training` crawls for generative model training; `MistralAI-Index` (search indexing) and `MistralAI-User` (Vibe user actions) do not train models.",
    "full_detail_md": "`MistralAI-User` is for user actions in Vibe and is not used to crawl content for generative AI training. `MistralAI-Index` crawls for indexing only and is not used for generative AI training. `MistralAI-Training` crawls web content to build datasets for training Mistral generative AI models, and webmasters can disallow that user agent in robots.txt.",
    "facets": {
     "user_agent_token": [
      "MistralAI-Training",
      "MistralAI-Index",
      "MistralAI-User"
     ],
     "operator_purpose": "MistralAI-Training: generative AI dataset training; MistralAI-Index: search indexing only; MistralAI-User: user actions in Vibe",
     "ip_verification_url": "https://docs.mistral.ai/robots",
     "robots_directives_honored": "Webmasters can disallow MistralAI-Training, MistralAI-Index, or MistralAI-User in robots.txt"
    },
    "telemetry": null,
    "source_url": "https://docs.mistral.ai/robots"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.mistral.ai/robots",
  "note": "`MistralAI-Training` crawls for generative model training; `MistralAI-Index` (search indexing) and `MistralAI-User` (Vibe user actions) do not train models."
 },
 {
  "id": "mltshp",
  "org_id": "mltshp",
  "name": "MLTSHP",
  "url": "https://mltshp.com/ai.txt",
  "type": "origin",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "MLTSHP",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, per-extension `Disallow:` list).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://mltshp.com/ai.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://mltshp.com/ai.txt",
  "note": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, per-extension `Disallow:` list)."
 },
 {
  "id": "mondadori",
  "org_id": "mondadori",
  "name": "Mondadori",
  "url": "https://www.mondadori.it/",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Mondadori",
    "role": "Publisher",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Adopters list: Mondadori (Italy): on its websites, [Mondadori](https://www.mondadori.it/) and [Oscar](https://www.oscarmondadori.it/).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md",
  "note": "Adopters list: Mondadori (Italy): on its websites, [Mondadori](https://www.mondadori.it/) and [Oscar](https://www.oscarmondadori.it/)."
 },
 {
  "id": "monos",
  "org_id": "monos",
  "name": "Monos",
  "url": "https://www.monos.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Monos",
    "role": "Seller (Shopify merchant)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`.",
    "full_detail_md": "The live profile declares protocol version 2026-08-25 (the ucp.version field, not a publication date) on monostravel.myshopify.com, where dev.ucp.shopping binds transports mcp and embedded and service dev.ucp.common is published. Payment handlers are com.google.pay at handler spec 2026-01-11, dev.shopify.card at handler spec 2026-01-15, and dev.shopify.shop_pay at handler spec 2026-04-08, and capabilities include dev.ucp.shopping.checkout plus dev.ucp.common.identity_linking.",
    "facets": {
     "commerce_surface": "Shopify storefront monostravel.myshopify.com",
     "payment_handlers_or_rail": "com.google.pay (handler spec 2026-01-11), dev.shopify.card (handler spec 2026-01-15), dev.shopify.shop_pay (handler spec 2026-04-08)",
     "transport_bindings": "dev.ucp.shopping over mcp and embedded; dev.ucp.common over mcp",
     "spec_version": "ucp.version 2026-08-25 (protocol version, not a publication date); supported_versions also lists 2026-04-08 and 2026-01-23"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8",
     "ucp_version": "2026-08-25",
     "transports": [
      "mcp",
      "embedded"
     ],
     "payment_handlers": [
      "com.google.pay",
      "dev.shopify.card",
      "dev.shopify.shop_pay"
     ],
     "merchant_host": "monostravel.myshopify.com",
     "publishes_dev_ucp_common_service": true
    },
    "source_url": "https://www.monos.com/.well-known/ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.monos.com/.well-known/ucp",
  "note": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`."
 },
 {
  "id": "mppx",
  "org_id": "tempo",
  "name": "mppx",
  "url": "https://mpp.dev/sdk.md",
  "type": "sdk",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "mppx (Tempo Labs & Wevm)",
    "role": "Client SDK & CLI (Co-author)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`mppx` is the Tempo Labs and Wevm reference SDK; `mppx validate` checks sandbox and live roundtrips.",
    "full_detail_md": "mppx is the reference implementation of the MPP SDKs, maintained by Tempo Labs and Wevm, and it can run x402-compatible EVM charges inline with an MPP route. mppx validate checks the flow end to end, including sandbox roundtrip test transactions and live-mode roundtrips with real funds.",
    "facets": {
     "settlement_rail": "Reference MPP SDK that can run x402-compatible EVM charges inline with an MPP route",
     "challenge_or_scheme": "MPP challenge and credential flow, with inline x402-compatible EVM charges on the same endpoint",
     "headers_or_methods": "Same endpoint can serve x402 and MPP clients",
     "sdk_or_endpoint": "mppx, maintained by Tempo Labs and Wevm; mppx validate covers sandbox and live roundtrips"
    },
    "telemetry": null,
    "source_url": "https://mpp.dev/sdk.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.dev/sdk.md",
  "note": "`mppx` is the Tempo Labs and Wevm reference SDK; `mppx validate` checks sandbox and live roundtrips."
 },
 {
  "id": "nanogpt",
  "org_id": "nanogpt",
  "name": "NanoGPT",
  "url": "https://nano-gpt.com/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "NanoGPT",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "https://nano-gpt.com/auth.md says access uses user-approved API keys. OAuth-aware clients use authorization-code with PKCE. Agents can use the browser-approved device login flow for a CLI handoff. Fetched HTTP 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://nano-gpt.com/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://nano-gpt.com/auth.md",
  "note": "https://nano-gpt.com/auth.md says access uses user-approved API keys. OAuth-aware clients use authorization-code with PKCE. Agents can use the browser-approved device login flow for a CLI handoff. Fetched HTTP 200 on 2026-10-29."
 },
 {
  "id": "neon-llms-txt",
  "org_id": "neon",
  "name": "Neon",
  "url": "https://neon.tech/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Neon",
    "role": "Database docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://neon.tech/llms.txt` (`# Neon Postgres`, `text/plain`), rewritten from `/docs/llms.txt` with `neon init` agent setup instructions.",
    "full_detail_md": "Serves `https://neon.tech/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 29,323 bytes, `x-nextjs-rewritten-path: /docs/llms.txt`, fetched 2026-11-04) opening `# Neon Postgres`, documenting `Claimable Neon` (`https://neon.com/auth.md`) and `neon init` CLI setup, and indexing `.md` documentation guides.",
    "facets": {
     "artifact_path": "https://neon.tech/llms.txt (rewritten to /docs/llms.txt)",
     "companion_files": "https://neon.com/auth.md; .md documentation guides",
     "content_type_or_bytes": "text/plain; charset=utf-8 (29,323 bytes)",
     "generator_or_consumer_mode": "Root-to-subpath Next.js rewritten documentation index"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Neon Postgres"
    },
    "source_url": "https://neon.tech/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://neon.tech/llms.txt",
  "note": "Serves `https://neon.tech/llms.txt` (`# Neon Postgres`, `text/plain`), rewritten from `/docs/llms.txt` with `neon init` agent setup instructions."
 },
 {
  "id": "newegg",
  "org_id": "newegg",
  "name": "Newegg",
  "url": "https://www.newegg.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Newegg",
    "role": "Retailer",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-12",
    "col4_md": "Integrated UCP for online checkout (2026-10-12) as merchant of record.",
    "full_detail_md": "On 2026-10-12, Digital Commerce 360 reported that Newegg integrated Google's Universal Commerce Protocol (UCP) for online checkout while remaining the merchant of record.",
    "facets": {
     "commerce_surface": "Newegg online checkout integration",
     "payment_handlers_or_rail": "UCP online checkout; Newegg remains the merchant of record",
     "transport_bindings": "Online checkout integration reported 2026-10-12",
     "spec_version": "Integration reported 2026-10-12"
    },
    "telemetry": null,
    "source_url": "https://www.digitalcommerce360.com/2026/10/12/newegg-adds-google-ucp-checkout-integration/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.digitalcommerce360.com/2026/10/12/newegg-adds-google-ucp-checkout-integration/",
  "note": "Integrated UCP for online checkout (2026-10-12) as merchant of record."
 },
 {
  "id": "next-js",
  "org_id": "vercel",
  "name": "Next.js",
  "url": "https://raw.githubusercontent.com/vercel/next.js/HEAD/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md",
   "vercel-agent-readability"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "vercel/next.js",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves root `AGENTS.md` (`# Next.js Development Guide`, `text/plain`) covering the pnpm monorepo and nested `test/AGENTS.md`.",
    "full_detail_md": "Serves root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 31,539 bytes, checked 2026-10-30) opening `# Next.js Development Guide` for the Next.js pnpm monorepo (`packages/`, `turbopack/`, `crates/`, `test/`). Instructs coding agents to read all `README.md` files along the directory path down to the edited target file and references nested `test/AGENTS.md` for test-suite rules.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/vercel/next.js/HEAD/AGENTS.md",
     "repo_scope": "Next.js pnpm monorepo root (31,539 bytes; packages/*, turbopack/, crates/, test/)",
     "heading_structure": "# Next.js Development Guide; ## Codebase structure; ## Build Commands; ## Fast Local Development; ## Bundler Selection; ## Testing; ## Writing Tests",
     "precedence_or_nested_files": "References nested test/AGENTS.md and requires reading all README.md files along the directory path down to the target file"
    },
    "telemetry": {
     "artifact_kind": "agents_md",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# Next.js Development Guide"
    },
    "source_url": "https://raw.githubusercontent.com/vercel/next.js/HEAD/AGENTS.md"
   },
   {
    "protocol_id": "vercel-agent-readability",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Next.js",
    "role": "Docs platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Next.js 16.2+ bundles version-matched documentation at `node_modules/next/dist/docs/`. The agent guide is `https://nextjs.org/docs/app/guides/ai-agents.md` (status 200 on 2026-10-29). The vercel agent CLI writes project guidance markers, and vercel/vercel-plugin ships the is-agentic skill.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://nextjs.org/docs/app/guides/ai-agents.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/vercel/next.js/HEAD/AGENTS.md",
  "note": "Serves root `AGENTS.md` (`# Next.js Development Guide`, `text/plain`) covering the pnpm monorepo and nested `test/AGENTS.md`."
 },
 {
  "id": "nlip-agents",
  "org_id": "nlip-project",
  "name": "nlip_agents",
  "url": "https://github.com/nlip-project/nlip_agents",
  "type": "sdk",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "nlip_agents",
    "role": "Agent library",
    "status": "Development",
    "status_display": "Development · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GitHub describes `nlip_agents` as a package for creating AI agents using NLIP as transport.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/orgs/nlip-project/repos?per_page=100"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://api.github.com/orgs/nlip-project/repos?per_page=100",
  "note": "GitHub describes `nlip_agents` as a package for creating AI agents using NLIP as transport."
 },
 {
  "id": "nlip-iam",
  "org_id": "nlip-project",
  "name": "nlip-iam",
  "url": "https://github.com/nlip-project/nlip-iam",
  "type": "authority",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "nlip-iam",
    "role": "Authentication server",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GitHub describes `nlip-iam` as a standard front-end authentication server for business applications. It sits in the nlip-project organization, whose profile says the organization contains reference implementations of the protocol and end-points.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/orgs/nlip-project/repos?per_page=100"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://api.github.com/orgs/nlip-project/repos?per_page=100",
  "note": "GitHub describes `nlip-iam` as a standard front-end authentication server for business applications. It sits in the nlip-project organization, whose profile says the organization contains reference implementations of the protocol and end-points."
 },
 {
  "id": "nlip-reference-demo-clients",
  "org_id": "nlip-project",
  "name": "NLIP Reference & Demo Clients",
  "url": "https://github.com/nlip-project/nlip_client",
  "type": "sdk",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "NLIP Reference & Demo Clients (nlip_client, text_client, kivy_client, kivy-chat-mach2)",
    "role": "Reference client & demo harnesses",
    "status": "Development",
    "status_display": "Development · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GitHub describes `nlip_client` as a python based client wrapper for nlip, `text_client` as a terminal based text-bot which talks using NLIP to a chat-bot, `kivy_client` as a simple client for NLIP written using Kivy, and `kivy-chat-mach2` as a Kivy chat client for NLIP with media upload support and rich text rendering. The nlip_server README says nlip_client simplifies sending NLIP messages, the current implementation uses `httpx` as the base transfer package, text_client provides a simple text based chatbot, and kivy_client provides a python kivy based visual client. Writing a client uses nlip_sdk and nlip_client.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/orgs/nlip-project/repos?per_page=100"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://api.github.com/orgs/nlip-project/repos?per_page=100",
  "note": "GitHub describes `nlip_client` as a python based client wrapper for nlip, `text_client` as a terminal based text-bot which talks using NLIP to a chat-bot, `kivy_client` as a simple client for NLIP written using Kivy, and `kivy-chat-mach2` as a Kivy chat client for NLIP with media upload support and rich text rendering. The nlip_server README says nlip_client simplifies sending NLIP messages, the c"
 },
 {
  "id": "nlip-sdk",
  "org_id": "nlip-project",
  "name": "nlip_sdk",
  "url": "https://pypi.org/project/nlip-sdk/",
  "type": "sdk",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "nlip_sdk",
    "role": "Client SDK",
    "status": "Development",
    "status_display": "Development · as of 2026-06-24",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-24",
    "col4_md": "GitHub describes `nlip_sdk` as a client-side SDK for nlip client development. PyPI `nlip_sdk` `0.1.3` requires `pydantic<3.0.0,>=2.9.2` and was uploaded on 2026-06-24. An earlier `0.1.0` wheel was uploaded on 2024-11-13. The package named nlip at `0.1.0` was yanked because other packages were published as nlip-sdk and nlip-server.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/nlip-sdk/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/nlip-sdk/json",
  "note": "GitHub describes `nlip_sdk` as a client-side SDK for nlip client development. PyPI `nlip_sdk` `0.1.3` requires `pydantic<3.0.0,>=2.9.2` and was uploaded on 2026-06-24. An earlier `0.1.0` wheel was uploaded on 2024-11-13. The package named nlip at `0.1.0` was yanked because other packages were published as nlip-sdk and nlip-server."
 },
 {
  "id": "nlip-server",
  "org_id": "nlip-project",
  "name": "nlip-server",
  "url": "https://github.com/nlip-project/nlip_server",
  "type": "sdk",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "nlip_server",
    "role": "Server library",
    "status": "Development",
    "status_display": "Development · as of 2026-06-24",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-24",
    "col4_md": "GitHub describes `nlip_server` as an initial implementation of a Python NLIP server built using fastapi. The README calls that repository one component of the Python repositories for an NLIP Proof of Concept implementation. It provides `NLIPApplication` and an echo server started with `poetry run fastapi dev nlip_server/echo.py`. PyPI `nlip-server` `0.1.3` was uploaded on 2026-06-24 and depends on `fastapi[standard]<1,>=0.115.0` and `nlip-sdk<0.2.0,>=0.1.2`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/nlip-project/nlip_server/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/nlip-project/nlip_server/main/README.md",
  "note": "GitHub describes `nlip_server` as an initial implementation of a Python NLIP server built using fastapi. The README calls that repository one component of the Python repositories for an NLIP Proof of Concept implementation. It provides `NLIPApplication` and an echo server started with `poetry run fastapi dev nlip_server/echo.py`. PyPI `nlip-server` `0.1.3` was uploaded on 2026-06-24 and depends on"
 },
 {
  "id": "nlip-soln",
  "org_id": "nlip-project",
  "name": "nlip_soln",
  "url": "https://github.com/nlip-project/nlip_soln",
  "type": "sdk",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "nlip_soln",
    "role": "Reference prototype",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GitHub describes `nlip_soln` as solutions for NLIP based on the nlip_server repository. The nlip_server README says nlip_soln provides a few simple prototype server side solutions using the nlip_server package.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/orgs/nlip-project/repos?per_page=100"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://api.github.com/orgs/nlip-project/repos?per_page=100",
  "note": "GitHub describes `nlip_soln` as solutions for NLIP based on the nlip_server repository. The nlip_server README says nlip_soln provides a few simple prototype server side solutions using the nlip_server package."
 },
 {
  "id": "nlip-web",
  "org_id": "nlip-project",
  "name": "nlip_web",
  "url": "https://github.com/nlip-project/nlip_web",
  "type": "sdk",
  "implements": [
   "nlip"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlip",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "nlip_web",
    "role": "Reference prototype",
    "status": "Experimental",
    "status_display": "Experimental · as of 2025-12-10",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-10",
    "col4_md": "GitHub describes `nlip_web` as a NLIP web server with a javascript client. Ecma's 10 December 2025 announcement says open-source reference implementations can be found on GitHub.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.github.com/orgs/nlip-project/repos?per_page=100"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/orgs/nlip-project/repos?per_page=100",
  "note": "GitHub describes `nlip_web` as a NLIP web server with a javascript client. Ecma's 10 December 2025 announcement says open-source reference implementations can be found on GitHub."
 },
 {
  "id": "notion-as-meta",
  "org_id": "notion",
  "name": "Notion MCP authorization server",
  "url": "https://mcp.notion.com",
  "type": "authority",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Notion",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`issuer` `https://mcp.notion.com`; `S256`; `jwt-bearer` (`id-jag`); `private_key_jwt`; `client_id_metadata_document_supported` `true`; `protected_resources`.",
    "full_detail_md": "GET https://mcp.notion.com/.well-known/oauth-authorization-server returned HTTP 200 `application/json`. `issuer` is `https://mcp.notion.com`. `protected_resources` lists `https://mcp.notion.com`, `https://mcp.notion.com/mcp`, and `https://mcp.notion.com/sse`. `client_id_metadata_document_supported` is `true`. `code_challenge_methods_supported` is `S256`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer`, and `authorization_grant_profiles_supported` includes `urn:ietf:params:oauth:grant-profile:id-jag`. `token_endpoint_auth_methods_supported` includes `private_key_jwt`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.notion.com/.well-known/oauth-authorization-server (issuer https://mcp.notion.com; protected_resources https://mcp.notion.com, https://mcp.notion.com/mcp, and https://mcp.notion.com/sse)",
     "registration_or_client_id_modes": "registration_endpoint https://mcp.notion.com/register; client_id_metadata_document_supported true; token_endpoint_auth_methods client_secret_basic, client_secret_post, none, private_key_jwt (RS256, ES256)",
     "pkce_or_grant_types": "PKCE S256; grants authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:jwt-bearer; profile urn:ietf:params:oauth:grant-profile:id-jag",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://mcp.notion.com",
     "client_id_metadata_document_supported": true
    },
    "source_url": "https://mcp.notion.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.notion.com/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://mcp.notion.com`; `S256`; `jwt-bearer` (`id-jag`); `private_key_jwt`; `client_id_metadata_document_supported` `true`; `protected_resources`."
 },
 {
  "id": "notion-mcp",
  "org_id": "notion",
  "name": "Official Notion MCP Server",
  "url": "https://mcp.notion.com/mcp",
  "type": "origin",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Notion",
    "role": "Remote MCP server",
    "status": "Listed",
    "status_display": "Listed · as of 2025-09-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-11",
    "col4_md": "Registry entry `com.notion/mcp` (`1.0.1`) advertising `streamable-http` (`https://mcp.notion.com/mcp`) and `sse` (`https://mcp.notion.com/sse`).",
    "full_detail_md": "Registered in the Official MCP Registry under `com.notion/mcp` v`1.0.1` (`Official Notion MCP server`), exposing remote `streamable-http` (`https://mcp.notion.com/mcp`) and `sse` (`https://mcp.notion.com/sse`) endpoints.",
    "facets": {
     "transport": "streamable-http, sse",
     "auth_or_oauth": "OAuth 2.1",
     "primitives": "tools, resources",
     "sdk_or_package": "com.notion/mcp v1.0.1"
    },
    "telemetry": null,
    "source_url": "https://registry.modelcontextprotocol.io/v0.1/servers/com.notion%2Fmcp/versions/1.0.1"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.modelcontextprotocol.io/v0.1/servers/com.notion%2Fmcp/versions/1.0.1",
  "note": "Registry entry `com.notion/mcp` (`1.0.1`) advertising `streamable-http` (`https://mcp.notion.com/mcp`) and `sse` (`https://mcp.notion.com/sse`)."
 },
 {
  "id": "nuxt-robots",
  "org_id": "nuxt-robots",
  "name": "Nuxt Robots",
  "url": "https://nuxtseo.com/docs/robots/guides/ai-directives",
  "type": "sdk",
  "implements": [
   "aipref-content-usage-attachment"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Nuxt Robots",
    "role": "Generator",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-16",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-16",
    "col4_md": "The AI Directives guide, last updated Jul 16, 2026, says two standards are supported and names `Content-Usage` as the IETF one. It says the Content-Usage directive follows the IETF AI Preferences specification. One documented example is `Content-Usage: bots=y, train-ai=n`, the same line follow.it serves inside `# START nuxt-robots (indexable)`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://nuxtseo.com/docs/robots/guides/ai-directives"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://nuxtseo.com/docs/robots/guides/ai-directives",
  "note": "The AI Directives guide, last updated Jul 16, 2026, says two standards are supported and names `Content-Usage` as the IETF one. It says the Content-Usage directive follows the IETF AI Preferences specification. One documented example is `Content-Usage: bots=y, train-ai=n`, the same line follow.it serves inside `# START nuxt-robots (indexable)`."
 },
 {
  "id": "nvidia-documentation",
  "org_id": "nvidia-documentation",
  "name": "NVIDIA Documentation",
  "url": "https://docs.nvidia.com/robots.txt",
  "type": "origin",
  "implements": [
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "NVIDIA Documentation",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "`https://docs.nvidia.com/robots.txt` returned status 200 on 2026-10-29 with `Content-Signal: ai-train=yes, search=yes, ai-input=yes` in the group for all user agents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.nvidia.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.nvidia.com/robots.txt",
  "note": "`https://docs.nvidia.com/robots.txt` returned status 200 on 2026-10-29 with `Content-Signal: ai-train=yes, search=yes, ai-input=yes` in the group for all user agents."
 },
 {
  "id": "nytimes-com-robots-txt",
  "org_id": "nyt",
  "name": "The New York Times",
  "url": "https://www.nytimes.com/robots.txt",
  "type": "origin",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "The New York Times",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Sets `Disallow: /` across 15 AI crawlers (`GPTBot`, `ClaudeBot`, `Google-Extended`, `PerplexityBot`, `CCBot`); allows `Google-CloudVertexBot` on `/wirecutter/` and `/athletic/`.",
    "full_detail_md": "Sets `Disallow: /` on named AI crawlers including `User-agent: GPTBot`, `User-agent: OAI-SearchBot`, `User-agent: ChatGPT-User`, `User-agent: ClaudeBot`, `User-agent: Claude-SearchBot`, `User-agent: Claude-User`, `User-agent: Google-Extended`, `User-agent: PerplexityBot`, `User-agent: Perplexity-User`, `User-agent: Applebot-Extended`, `User-agent: FacebookBot`, `User-agent: meta-externalagent`, `User-agent: CCBot`, `User-agent: cohere-ai`, and `User-agent: DuckAssistBot`. `User-agent: Google-CloudVertexBot` is `Disallow: /` with `Allow: /wirecutter/` and `Allow: /athletic/`, while `User-agent: Amazonbot` is `Disallow: /wirecutter/`.",
    "facets": {
     "scope_host": "https://www.nytimes.com/robots.txt",
     "policy_role": "Publisher robots.txt policy declaration (declares crawl policy, not crawler compliance)",
     "published_rules": [
      {
       "tokens": [
        "GPTBot",
        "OAI-SearchBot",
        "ChatGPT-User",
        "ClaudeBot",
        "Claude-SearchBot",
        "Claude-User",
        "Google-Extended",
        "PerplexityBot",
        "Perplexity-User",
        "Applebot-Extended",
        "FacebookBot",
        "meta-externalagent",
        "CCBot",
        "cohere-ai",
        "DuckAssistBot"
       ],
       "directives": [
        "Disallow: /"
       ]
      },
      {
       "tokens": [
        "Google-CloudVertexBot"
       ],
       "directives": [
        "Disallow: /",
        "Allow: /wirecutter/",
        "Allow: /athletic/"
       ]
      },
      {
       "tokens": [
        "Amazonbot"
       ],
       "directives": [
        "Disallow: /wirecutter/"
       ]
      }
     ],
     "content_signals": null
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "robots_txt",
     "marker": "User-agent: GPTBot"
    },
    "source_url": "https://www.nytimes.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.nytimes.com/robots.txt",
  "note": "Sets `Disallow: /` across 15 AI crawlers (`GPTBot`, `ClaudeBot`, `Google-Extended`, `PerplexityBot`, `CCBot`); allows `Google-CloudVertexBot` on `/wirecutter/` and `/athletic/`."
 },
 {
  "id": "official-acp-sdks",
  "org_id": "agentclientprotocol",
  "name": "Official ACP SDKs",
  "url": "https://github.com/agentclientprotocol/agent-client-protocol",
  "type": "sdk",
  "implements": [
   "agent-client-protocol"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Official ACP SDKs",
    "role": "Official client & agent SDKs",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-09",
    "as_of": "2026-11-02",
    "col4_md": "Official client and agent SDKs: Rust `agent-client-protocol` (`v1.15.1`), TypeScript `@agentclientprotocol/sdk`, Python `python-sdk`, Kotlin `acp-kotlin`, Java `java-sdk`.",
    "full_detail_md": "The agentclientprotocol organization maintains official client and agent libraries in Rust (`agent-client-protocol`, reaching `v1.0.0` on 2026-06-24, `v1.13.0` on 2026-10-27 alongside `schema-v1.27.0`, and `v1.15.1` on 2026-11-02 alongside `schema-v1.29.1` and `schema-v2.0.0-alpha.13`), TypeScript (`@agentclientprotocol/sdk`, reaching `1.0.0` on 2026-06-25), Python (`python-sdk`), Kotlin (`acp-kotlin`), and Java (`java-sdk`).",
    "facets": {
     "role_in_acp": "Client, agent, and schema SDKs",
     "integration_mode": "First-party libraries and JSON Schema artifacts (v1 stable and v2 alpha)",
     "transport": "JSON-RPC 2.0 over stdio and custom bidirectional streams",
     "verification_posture": "GitHub releases API (2026-11-02) & official ACP Updates log",
     "sdk_or_package": "agent-client-protocol v1.15.1 (schema-v1.29.1), @agentclientprotocol/sdk 1.0.0+, python-sdk, acp-kotlin, java-sdk"
    },
    "telemetry": null,
    "source_url": "https://github.com/agentclientprotocol/agent-client-protocol"
   }
  ],
  "observed": "2026-11-09",
  "date_basis": "source",
  "source": "https://github.com/agentclientprotocol/agent-client-protocol",
  "note": "Official client and agent SDKs: Rust `agent-client-protocol` (`v1.15.1`), TypeScript `@agentclientprotocol/sdk`, Python `python-sdk`, Kotlin `acp-kotlin`, Java `java-sdk`."
 },
 {
  "id": "okf-mcp",
  "org_id": "okfgem",
  "name": "okf-mcp",
  "url": "https://okfgem.com/blog/okf-mcp-1-0-0/",
  "type": "sdk",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "okf-mcp (Rodrigo Serradura)",
    "role": "MCP server",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-11",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-11",
    "col4_md": "`okf-mcp 1.0.0` serves bundles over MCP with ten read-only tools.",
    "full_detail_md": "okf-mcp 1.0.0, datePublished 2026-08-11, serves OKF bundles over the Model Context Protocol with ten read-only tools and rides the okf gem 1.13.0, which is a library version and not SPEC.md Version 0.2. The post says any host speaking the Model Context Protocol, including Claude Desktop and Claude Code, reads the bundles on the machine directly.",
    "facets": {
     "artifact_or_endpoint": "okf-mcp 1.0.0 Model Context Protocol read surface",
     "content_type_or_schema": "Local OKF bundles read from disk by ten read-only MCP tools",
     "discovery_mechanism": "okf-gem blog post dated 2026-08-11",
     "version_or_posture": "Tool release okf-mcp 1.0.0 on okf gem 1.13.0; gem version is not the spec Version 0.2 field"
    },
    "telemetry": null,
    "source_url": "https://okfgem.com/blog/okf-mcp-1-0-0/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://okfgem.com/blog/okf-mcp-1-0-0/",
  "note": "`okf-mcp 1.0.0` serves bundles over MCP with ten read-only tools."
 },
 {
  "id": "okta-cimd",
  "org_id": "okta",
  "name": "Okta",
  "url": "https://developer.okta.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Okta",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "API registration of a CIMD client, then that client ID on the token request.",
    "full_detail_md": "Okta documents CIMD-based registration for AI agents: register a CIMD OAuth client with the API, configure an existing agent as a CIMD client, and use that client ID on the token request. The guide requires an Okta org that has CIMD-based AI agent registration enabled.",
    "facets": {
     "metadata_flag_or_profile": "CIMD-based OAuth client registered through the API, or an existing agent configured as a CIMD client",
     "auth_method_or_pkce": "The CIMD client ID is used on the token request; the guide does not name a PKCE method",
     "uri_or_ssrf_rules": "Not specified beyond using the CIMD client ID; the guide requires the org feature to be enabled",
     "draft_or_spec_version": "Undated Okta guide; it does not name a CIMD draft revision"
    },
    "telemetry": null,
    "source_url": "https://developer.okta.com/docs/guides/ai-agent-cimd-registration/main/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://developer.okta.com/docs/guides/ai-agent-cimd-registration/main/",
  "note": "API registration of a CIMD client, then that client ID on the token request."
 },
 {
  "id": "okta-cross-app-access",
  "org_id": "okta",
  "name": "Okta Cross App Access / Agent SSO",
  "url": "https://www.okta.com",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Okta (Cross App Access / Workforce Identity)",
    "role": "Identity provider / ID-JAG issuer",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-24",
    "col4_md": "On August 24, 2026, Okta announced the general availability of Agent SSO, bringing the open Cross App Access (XAA / ID-JAG) standard into production as the first named identity provider for Anthropic's generally available Enterprise-Managed Authorization.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.okta.com/en-gb/newsroom/press-releases/okta-brings-first-class-identity-to-ai-agents-with-agent-sso/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.okta.com/en-gb/newsroom/press-releases/okta-brings-first-class-identity-to-ai-agents-with-agent-sso/",
  "note": "On August 24, 2026, Okta announced the general availability of Agent SSO, bringing the open Cross App Access (XAA / ID-JAG) standard into production as the first named identity provider for Anthropic's generally available Enterprise-Managed Authorization."
 },
 {
  "id": "okta-cross-app-access-mcp",
  "org_id": "okta",
  "name": "Okta",
  "url": "https://github.com/oktadev/okta-cross-app-access-mcp",
  "type": "sdk",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Okta Cross-App Access MCP",
    "role": "MCP client proof of concept",
    "status": "Development",
    "status_display": "Development · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Proof of concept showing how a Model Context Protocol (MCP) client can leverage the Identity Assertion Authorization Grant specification for secure and interoperable authorization of MCP clients within enterprise environments.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/oktadev/okta-cross-app-access-mcp/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/oktadev/okta-cross-app-access-mcp/",
  "note": "Proof of concept showing how a Model Context Protocol (MCP) client can leverage the Identity Assertion Authorization Grant specification for secure and interoperable authorization of MCP clients within enterprise environments."
 },
 {
  "id": "ollama",
  "org_id": "ollama",
  "name": "Ollama",
  "url": "https://docs.agno.com/reference/models/open-responses",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Ollama",
    "role": "Local inference engine",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Agno names Ollama (`v0.13.3+`); AWS and InfoQ also list it as serving the format. Devon Rifkin (Ollama) is an initial TSC voting member.",
    "full_detail_md": "Agno says providers that implement this spec include Ollama (v0.13.3+) and OpenRouter. AWS says Ollama is among the providers serving the format, in the same list as vLLM, OpenRouter, and Hugging Face, and InfoQ names Ollama with LM Studio and vLLM as local inference providers that adopted the specification. Devon Rifkin (Ollama) is an initial TSC voting member.",
    "facets": {
     "endpoint_or_route": "No route is published in the cited Agno, AWS, or InfoQ lines",
     "streaming_or_items": "Not stated in those provider lists",
     "tool_or_state_model": "Not stated in those provider lists",
     "sdk_or_version": "Agno names Ollama v0.13.3+"
    },
    "telemetry": null,
    "source_url": "https://docs.agno.com/reference/models/open-responses"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.agno.com/reference/models/open-responses",
  "note": "Agno names Ollama (`v0.13.3+`); AWS and InfoQ also list it as serving the format. Devon Rifkin (Ollama) is an initial TSC voting member."
 },
 {
  "id": "open-did-server",
  "org_id": "open-did-server",
  "name": "Open DID Server",
  "url": "https://raw.githubusercontent.com/agent-network-protocol/open-did-server/main/README.md",
  "type": "sdk",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Open DID Server",
    "role": "Messaging node / Server",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-01",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-01",
    "col4_md": "agent-network-protocol/open-did-server (created 2026-10-01) hosts did:wba (e1_) and did:web documents on standard DID paths, resolves WNS Handles, and accepts only a limited ANP HTTP Message Signature (RFC 9421 sig1) over the caller's authentication key.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agent-network-protocol/open-did-server/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/agent-network-protocol/open-did-server/main/README.md",
  "note": "agent-network-protocol/open-did-server (created 2026-10-01) hosts did:wba (e1_) and did:web documents on standard DID paths, resolves WNS Handles, and accepts only a limited ANP HTTP Message Signature (RFC 9421 sig1) over the caller's authentication key."
 },
 {
  "id": "openai-apps-sdk-examples",
  "org_id": "openai",
  "name": "openai-apps-sdk-examples",
  "url": "https://github.com/openai/openai-apps-sdk-examples/",
  "type": "sdk",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Apps SDK Examples Gallery",
    "role": "Official example MCP servers",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Official example MCP servers, including `kitchen_sink_server_node/` and `kitchen_sink_server_python/`, light up widgets with `_meta.ui.resourceUri`.",
    "full_detail_md": "The openai/openai-apps-sdk-examples repository ships example UI components and example MCP servers that expose those components as tools. The kitchen-sink Node and Python servers are in that gallery, and the README says each tool lights up widgets by combining structured payloads with `_meta.ui.resourceUri` metadata returned from the MCP servers.",
    "facets": {
     "transport_or_manifest": "MCP servers returning widget metadata in `_meta.ui.resourceUri`",
     "ui_or_widget_surface": "Example UI component gallery, including kitchen-sink-lite",
     "auth_or_permissions": "Includes `authenticated_server_python/` for authenticated tool calls",
     "sdk_or_version": "Apps SDK examples gallery"
    },
    "telemetry": null,
    "source_url": "https://github.com/openai/openai-apps-sdk-examples/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/openai/openai-apps-sdk-examples/",
  "note": "Official example MCP servers, including `kitchen_sink_server_node/` and `kitchen_sink_server_python/`, light up widgets with `_meta.ui.resourceUri`."
 },
 {
  "id": "openai-apps-sdk-ui",
  "org_id": "openai",
  "name": "@openai/apps-sdk-ui",
  "url": "https://developers.openai.com/plugins/build/chatgpt-ui",
  "type": "sdk",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "OpenAI Apps SDK UI",
    "role": "SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`@openai/apps-sdk-ui` controls match ChatGPT and use the MCP Apps `ui/*` bridge.",
    "full_detail_md": "`@openai/apps-sdk-ui` provides buttons, cards, input controls, and layout primitives that match ChatGPT's container. UI still declares `_meta.ui.resourceUri` and is rendered through the MCP Apps `ui/*` bridge over postMessage.",
    "facets": {
     "transport_or_manifest": "UI resource still declared with _meta.ui.resourceUri",
     "ui_or_widget_surface": "Buttons, cards, input controls, and layout primitives matching ChatGPT's container",
     "auth_or_permissions": "No separate auth handshake named in the cited component-library sentence",
     "sdk_or_version": "@openai/apps-sdk-ui on the MCP Apps ui/* bridge"
    },
    "telemetry": null,
    "source_url": "https://developers.openai.com/plugins/build/chatgpt-ui"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://developers.openai.com/plugins/build/chatgpt-ui",
  "note": "`@openai/apps-sdk-ui` controls match ChatGPT and use the MCP Apps `ui/*` bridge."
 },
 {
  "id": "openai-chatgpt-agent",
  "org_id": "openai",
  "name": "ChatGPT agent",
  "url": "https://chatgpt.com",
  "type": "origin",
  "implements": [
   "http-message-signatures",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "OpenAI (ChatGPT agent)",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Publishes `Ed25519` JWK (`purpose` `ai`) and directory-response signature headers; signature validation not established by HTTP observation.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` for `\"signature_agent\":\"https://chatgpt.com\"`, publishing one `Ed25519` JWK (`\"purpose\":\"ai\"`) and directory-response `signature`/`signature-input` headers (`tag=\"http-message-signatures-directory\"`); cryptographic signature validation is not established by the recorded HTTP observation.",
    "facets": {
     "signature_or_key_format": "Publishes 1 OKP Ed25519 JWK (`use: sig`, `purpose: ai`, `kid: ArwjqcCqtA5oxEWkzXGC-To_0A9whHmajCHtfe8I9aY`) and directory-response signature headers; signature validation not established by the recorded HTTP observation",
     "directory_or_header": "HTTP 200 `application/http-message-signatures-directory+json` (`signature_agent: https://chatgpt.com`)",
     "signing_algorithm": "Ed25519 (`alg=\"ed25519\"`, `tag=\"http-message-signatures-directory\"`)",
     "verification_role": "Bot / Agent signer (signs outbound ChatGPT operator requests)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 1,
     "use": "sig",
     "kid": "ArwjqcCqtA5oxEWkzXGC-To_0A9whHmajCHtfe8I9aY",
     "purpose": "ai",
     "signature_agent": "https://chatgpt.com",
     "alg": "ed25519"
    },
    "source_url": "https://chatgpt.com/.well-known/http-message-signatures-directory"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "OpenAI (ChatGPT agent)",
    "role": "Bot / Agent signer (Web Bot Auth profile)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Web Bot Auth profile: publishes `Ed25519` JWK (`purpose` `ai`) and directory-response signature headers (`tag=\"http-message-signatures-directory\"`).",
    "full_detail_md": "Implements the Web Bot Auth profile of RFC 9421 for ChatGPT operator requests and serves HTTP 200 `application/http-message-signatures-directory+json` from its key directory endpoint (`signature_agent`: `https://chatgpt.com`), publishing one `OKP` `Ed25519` JWK (`\"purpose\":\"ai\"`, `\"kid\":\"ArwjqcCqtA5oxEWkzXGC-To_0A9whHmajCHtfe8I9aY\"`) and directory-response `signature-input` headers (`alg=\"ed25519\"`, `tag=\"http-message-signatures-directory\"`); cryptographic signature validation is not established by the recorded HTTP observation.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth profile of RFC 9421 (`tag=\"http-message-signatures-directory\"`)",
     "signature_fields": "HTTP 200 `application/http-message-signatures-directory+json` (`signature_agent: https://chatgpt.com`)",
     "algorithms_or_keys": "Publishes 1 OKP `Ed25519` JWK (`alg=\"ed25519\"`, `use: sig`, `purpose: ai`, `kid: ArwjqcCqtA5oxEWkzXGC-To_0A9whHmajCHtfe8I9aY`) and directory-response signature headers",
     "verification_posture": "Bot / Agent signer (signs ChatGPT operator requests under Web Bot Auth; directory signature validation not established by HTTP observation)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 1,
     "use": "sig",
     "kid": "ArwjqcCqtA5oxEWkzXGC-To_0A9whHmajCHtfe8I9aY",
     "purpose": "ai",
     "signature_agent": "https://chatgpt.com",
     "alg": "ed25519"
    },
    "source_url": "https://chatgpt.com/.well-known/http-message-signatures-directory"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://chatgpt.com/.well-known/http-message-signatures-directory",
  "note": "Publishes `Ed25519` JWK (`purpose` `ai`) and directory-response signature headers; signature validation not established by HTTP observation."
 },
 {
  "id": "openai-chatgpt-instant-checkout",
  "org_id": "openai",
  "name": "ChatGPT Instant Checkout",
  "url": "https://chatgpt.com",
  "type": "agent",
  "implements": [
   "agentic-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "OpenAI (ChatGPT Instant Checkout)",
    "role": "Buying agent / AI surface (Co-author)",
    "status": "Partial",
    "status_display": "Partial · as of 2026-03-24",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-24",
    "col4_md": "U.S. Plus, Pro, and Free users: single-item Etsy checkout, then merchant checkout and discovery.",
    "full_detail_md": "Instant Checkout launched in ChatGPT on September 29, 2025, powered by the Agentic Commerce Protocol and built with Stripe. U.S. ChatGPT Plus, Pro, and Free users could buy directly from U.S. Etsy sellers, and Instant Checkout then supported single-item purchases. On March 24, 2026 OpenAI said that through ACP, merchants share product feeds and promotions, and that it is allowing merchants to use their own checkout experiences while focusing on product discovery. ChatGPT's merchants page says purchases are completed on merchant-owned websites or apps.",
    "facets": {
     "commerce_role_or_surface": "ChatGPT Instant Checkout buying surface",
     "payment_or_token_rail": "ACP built with Stripe; later merchant-owned checkout",
     "api_or_spec_version": "Instant Checkout, then product-feed discovery over ACP",
     "availability_or_eligibility_posture": "September 29, 2025 for U.S. Plus, Pro, and Free users buying single items from U.S. Etsy sellers; March 24, 2026 shift toward merchant checkout and discovery"
    },
    "telemetry": null,
    "source_url": "https://web.archive.org/web/20261022061422/https://openai.com/index/buy-it-in-chatgpt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://web.archive.org/web/20261022061422/https://openai.com/index/buy-it-in-chatgpt/",
  "note": "U.S. Plus, Pro, and Free users: single-item Etsy checkout, then merchant checkout and discovery."
 },
 {
  "id": "openai-crawlers",
  "org_id": "openai",
  "name": "OpenAI crawlers",
  "url": "https://developers.openai.com/api/docs/bots",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "OpenAI",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`GPTBot` crawls for model training; `OAI-SearchBot` indexes ChatGPT search; `ChatGPT-User` handles user actions; `OAI-AdsBot` checks ads.",
    "full_detail_md": "`GPTBot` is used to crawl content that may be used in training generative AI foundation models. `OAI-SearchBot` is for search and surfaces websites in ChatGPT search features. `ChatGPT-User` is for certain user actions in ChatGPT and Custom GPTs, is not used for automatic crawling, and robots.txt rules may not apply. `OAI-AdsBot` validates the safety of web pages submitted as ads on ChatGPT. Each robots.txt setting is independent.",
    "facets": {
     "user_agent_token": [
      "GPTBot",
      "OAI-SearchBot",
      "ChatGPT-User",
      "OAI-AdsBot"
     ],
     "operator_purpose": "GPTBot: foundation model training; OAI-SearchBot: ChatGPT search results; ChatGPT-User: user actions in ChatGPT and Custom GPTs",
     "ip_verification_url": "https://developers.openai.com/api/docs/bots",
     "robots_directives_honored": "Independent per-token robots.txt controls; robots.txt rules may not apply to user-initiated ChatGPT-User actions"
    },
    "telemetry": null,
    "source_url": "https://developers.openai.com/api/docs/bots"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://developers.openai.com/api/docs/bots",
  "note": "`GPTBot` crawls for model training; `OAI-SearchBot` indexes ChatGPT search; `ChatGPT-User` handles user actions; `OAI-AdsBot` checks ads."
 },
 {
  "id": "openai-responses",
  "org_id": "openai",
  "name": "OpenAI Responses API",
  "url": "https://api.openai.com/v1",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "OpenAI",
    "role": "Inference API",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-04-24",
    "col4_md": "Baseline `POST /v1/responses` endpoint (`https://api.openai.com/v1`, HTTP JSON and `text/event-stream`) on which Open Responses is built. Steve Coffey and Ji Huang (OpenAI) are initial TSC voting members.",
    "full_detail_md": "OpenAI built Open Responses on top of its original OpenAI Responses API (announced January 15, 2026), and the Open Responses OpenAPI `3.1.0` specification (`2026-04-24`) defines `https://api.openai.com/v1` with `post` on `/responses` (returning `application/json` or `text/event-stream`) as the baseline server endpoint. Steve Coffey and Ji Huang (OpenAI) are initial TSC voting members.",
    "facets": {
     "endpoint_or_route": "https://api.openai.com/v1 path /responses (inferred from OpenAPI servers field)",
     "streaming_or_items": "HTTP POST JSON and text/event-stream on /responses",
     "tool_or_state_model": "OpenAPI item and tool schemas; the changelog says the spec is built on the original Responses API",
     "sdk_or_version": "OpenAPI info.version 2026-04-24, the dated spec release label, not a live HTTP grade"
    },
    "telemetry": null,
    "source_url": "https://www.openresponses.org/openapi/2026-04-24/openapi.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.openresponses.org/openapi/2026-04-24/openapi.json",
  "note": "Baseline `POST /v1/responses` endpoint (`https://api.openai.com/v1`, HTTP JSON and `text/event-stream`) on which Open Responses is built. Steve Coffey and Ji Huang (OpenAI) are initial TSC voting members."
 },
 {
  "id": "openai-sdk",
  "org_id": "openai",
  "name": "OpenAI SDK",
  "url": "https://developers.openai.com/api/docs/changelog",
  "type": "sdk",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "OpenAI SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Official OpenAI SDK for the Responses API; targets compliant third-party endpoints (such as Amazon Bedrock) by overriding the base URL and API key.",
    "full_detail_md": "OpenAI provides the official OpenAI SDK for the original OpenAI Responses API (announced January 15, 2026), and developers can use the OpenAI SDK to call compliant third-party Open Responses endpoints such as Amazon Bedrock by changing the base URL and API key.",
    "facets": {
     "endpoint_or_route": "Caller-supplied Bedrock base URL; the AWS post does not print that URL",
     "streaming_or_items": "Not named in the SDK sentence",
     "tool_or_state_model": "Calls models hosted on Bedrock's Responses API",
     "sdk_or_version": "OpenAI SDK; the Jan 15 changelog says the spec is built on the original Responses API"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/",
  "note": "Official OpenAI SDK for the Responses API; targets compliant third-party endpoints (such as Amazon Bedrock) by overriding the base URL and API key."
 },
 {
  "id": "openanp",
  "org_id": "openanp",
  "name": "OpenANP (AgentConnect)",
  "url": "https://raw.githubusercontent.com/agent-network-protocol/anp/main/README.md",
  "type": "sdk",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "OpenANP (AgentConnect)",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "OpenANP, in agent-network-protocol/anp, turns Python methods into discoverable ANP interfaces and exposes the standard agent documents and a JSON-RPC endpoint. The repo is the multi-language reference implementation (Python package anp; Go, Rust, Dart, TypeScript, and Java workspaces). Coordinated release tag release-20260912.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/agent-network-protocol/anp/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/agent-network-protocol/anp/main/README.md",
  "note": "OpenANP, in agent-network-protocol/anp, turns Python methods into discoverable ANP interfaces and exposes the standard agent documents and a JSON-RPC endpoint. The repo is the multi-language reference implementation (Python package anp; Go, Rust, Dart, TypeScript, and Java workspaces). Coordinated release tag release-20260912."
 },
 {
  "id": "openclaw-accept",
  "org_id": "openclaw",
  "name": "OpenClaw",
  "url": "https://acceptmarkdown.com/status",
  "type": "harness",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "OpenClaw",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · as of 2026-05-04",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-05-04",
    "col4_md": "Sends `Accept: text/markdown` (verified 2026-05-04).",
    "full_detail_md": "AcceptMarkdown's client matrix, last updated 2026-06-22, records OpenClaw as sending an Accept header that includes text/markdown. Verified date on that row is 2026-05-04.",
    "facets": {
     "negotiation_or_artifact": "Accept header includes text/markdown",
     "response_headers": "Accept: text/markdown, text/html;q=0.9, */*;q=0.1",
     "content_type_or_tokens": "Requests text/markdown",
     "verification_posture": "AcceptMarkdown matrix verified 2026-05-04; matrix last updated 2026-06-22"
    },
    "telemetry": null,
    "source_url": "https://acceptmarkdown.com/status"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://acceptmarkdown.com/status",
  "note": "Sends `Accept: text/markdown` (verified 2026-05-04)."
 },
 {
  "id": "opencode",
  "org_id": "opencode",
  "name": "OpenCode",
  "url": "https://opencode.ai/",
  "type": "harness",
  "implements": [
   "agents-md",
   "anthropic-agent-skills-format",
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "OpenCode",
    "role": "Agent harness",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-10-22",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-22",
    "col4_md": "Listed on the `agentskills.io` client directory, which links to `https://opencode.ai/` (docs: `https://opencode.ai/docs/skills/`), and cited by Anthropic as having a community loader.",
    "full_detail_md": "Anthropic's `2026-10-22` AAIF donation post notes that developers wrote community skill loaders for Codex, Cursor, and OpenCode within weeks of the October 2025 launch, and the `agentskills.io` client directory lists OpenCode (`https://opencode.ai/`, linking to `https://opencode.ai/docs/skills/`).",
    "facets": {
     "transport_or_packaging": "Community skill loader and directory-listed client integration",
     "manifest_or_entry": "SKILL.md loader referenced in AAIF donation announcement and agentskills.io showcase",
     "execution_or_sandbox": "Terminal, IDE, and desktop coding agent",
     "verification_posture": "Directory listing on agentskills.io and Anthropic announcement mention (2026-10-22); not first-party runtime verified"
    },
    "telemetry": null,
    "source_url": "https://www.anthropic.com/news/donating-agent-skills-to-the-agentic-ai-foundation"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "opencode",
    "role": "Coding agent / CLI",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Named in the compatible coding-agent roster on `agents.md`.",
    "full_detail_md": "Listed on `agents.md` under compatible AI coding agents and tools (`opencode`); runtime `AGENTS.md` discovery and hierarchy precedence are not independently verified in the cited documentation snapshots.",
    "facets": {
     "discovery_behavior": "Listed on agents.md — implementation behavior not independently verified",
     "hierarchy_precedence": "Not independently verified in cited documentation",
     "fallback_files": "Not independently verified in cited documentation",
     "verification_posture": "Listed on agents.md — implementation behavior not independently verified"
    },
    "telemetry": null,
    "source_url": "https://agents.md/"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "OpenCode",
    "role": "Coding agent",
    "status": "Observed fetching",
    "status_display": "Observed fetching · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`webfetch` defaults to Markdown with `text/markdown;q=1.0` above `text/html;q=0.7`.",
    "full_detail_md": "The `webfetch` tool retrieves one HTTP or HTTPS URL as Markdown, text, or HTML, and Markdown is the default. Its Markdown Accept header is `text/markdown;q=1.0, text/x-markdown;q=0.9, text/plain;q=0.8, text/html;q=0.7, */*;q=0.1`.",
    "facets": {
     "negotiation_or_artifact": "webfetch retrieves one HTTP or HTTPS URL; Markdown is the default format",
     "response_headers": "Accept: text/markdown;q=1.0, text/x-markdown;q=0.9, text/plain;q=0.8, text/html;q=0.7, */*;q=0.1",
     "content_type_or_tokens": "text/markdown;q=1.0 ranked above text/html;q=0.7",
     "verification_posture": "OpenCode tools documentation and webfetch.ts on the dev branch (undated source; checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://opencode.ai/v2/docs/tools/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.anthropic.com/news/donating-agent-skills-to-the-agentic-ai-foundation",
  "note": "Listed on the `agentskills.io` client directory, which links to `https://opencode.ai/` (docs: `https://opencode.ai/docs/skills/`), and cited by Anthropic as having a community loader."
 },
 {
  "id": "openlit-platform",
  "org_id": "openlit",
  "name": "OpenLIT Platform",
  "url": "https://raw.githubusercontent.com/openlit/openlit/main/README.md",
  "type": "origin",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "OpenLIT Platform",
    "role": "OTLP receiver and evaluation platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Same README as the SDK row (fetched 2026-11-04). OpenLIT is described as an open-source agent harness engineering platform. Traces and metrics follow OpenTelemetry GenAI semantic conventions (`gen_ai.*`). The diagram sends OTLP from an AI app or agent to an OpenLIT OTLP receiver, with an optional OpenTelemetry Collector. The quickstart shows the local dashboard at `http://127.0.0.1:3000` and the OTLP endpoint `http://127.0.0.1:4318`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/openlit/openlit/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/openlit/openlit/main/README.md",
  "note": "Same README as the SDK row (fetched 2026-11-04). OpenLIT is described as an open-source agent harness engineering platform. Traces and metrics follow OpenTelemetry GenAI semantic conventions (`gen_ai.*`). The diagram sends OTLP from an AI app or agent to an OpenLIT OTLP receiver, with an optional OpenTelemetry Collector. The quickstart shows the local dashboard at `http://127.0.0.1:3000` and the O"
 },
 {
  "id": "openlit-sdk",
  "org_id": "openlit",
  "name": "OpenLIT",
  "url": "https://raw.githubusercontent.com/openlit/openlit/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenLIT",
    "role": "OpenTelemetry-native GenAI and MCP SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Python and TypeScript SDK (`openlit.init()`, README fetched 2026-11-04). The README says OpenLIT automatically instruments supported LLM providers, frameworks, vector databases, and other AI infrastructure and exports OpenTelemetry traces and metrics, and that traces and metrics follow OpenTelemetry GenAI semantic conventions (`gen_ai.*`). The harness table includes observing every LLM call, tool call, and MCP request. Default export shown is OTLP at `http://127.0.0.1:4318`. The platform receiver is a separate row.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/openlit/openlit/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/openlit/openlit/main/README.md",
  "note": "Python and TypeScript SDK (`openlit.init()`, README fetched 2026-11-04). The README says OpenLIT automatically instruments supported LLM providers, frameworks, vector databases, and other AI infrastructure and exports OpenTelemetry traces and metrics, and that traces and metrics follow OpenTelemetry GenAI semantic conventions (`gen_ai.*`). The harness table includes observing every LLM call, tool "
 },
 {
  "id": "openllmetry",
  "org_id": "traceloop",
  "name": "OpenLLMetry (Traceloop)",
  "url": "https://raw.githubusercontent.com/traceloop/openllmetry/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenLLMetry (Traceloop)",
    "role": "OpenTelemetry instrumentation set",
    "status": "Supported",
    "status_display": "Supported · as of 2025-03-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2025-03-06",
    "col4_md": "OpenLLMetry, maintained by Traceloop, is a set of extensions built on OpenTelemetry. The README says their semantic conventions are now part of OpenTelemetry and that the repo contains standard OpenTelemetry instrumentations for LLM providers and vector databases. Package `opentelemetry-instrumentation-mcp` 0.62.4 is described as OpenTelemetry mcp instrumentation, registers `opentelemetry.instrumentation.mcp:McpInstrumentor`, and depends on `opentelemetry-semantic-conventions-ai`. The README checklist marks MCP, CrewAI, and LangGraph, and marks AWS Strands as built-in OTEL support. Those lines do not name GenAI or MCP attribute keys. The 2025-03-06 OpenTelemetry post lists Traceloop OpenTelemetry Instrumentation as an external package and says Traceloop is trying to donate the instrumentation code to OpenTelemetry.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/traceloop/openllmetry/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/traceloop/openllmetry/main/README.md",
  "note": "OpenLLMetry, maintained by Traceloop, is a set of extensions built on OpenTelemetry. The README says their semantic conventions are now part of OpenTelemetry and that the repo contains standard OpenTelemetry instrumentations for LLM providers and vector databases. Package `opentelemetry-instrumentation-mcp` 0.62.4 is described as OpenTelemetry mcp instrumentation, registers `opentelemetry.instrume"
 },
 {
  "id": "openmanus-anp",
  "org_id": "openmanus-anp",
  "name": "OpenManus-ANP",
  "url": "https://github.com/agent-network-protocol/OpenManus-ANP",
  "type": "harness",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "OpenManus-ANP",
    "role": "AI host / assistant",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-03",
    "as_of": null,
    "col4_md": "Fork agent-network-protocol/OpenManus-ANP adds ANP through anp_tool.py: one prompt and one HTTP function so the agent can call other ANP agents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/agent-network-protocol/OpenManus-ANP"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "recorded",
  "source": "https://github.com/agent-network-protocol/OpenManus-ANP",
  "note": "Fork agent-network-protocol/OpenManus-ANP adds ANP through anp_tool.py: one prompt and one HTTP function so the agent can call other ANP agents."
 },
 {
  "id": "openresponses-compliance",
  "org_id": "openresponses",
  "name": "openresponses/openresponses compliance suite",
  "url": "https://www.openresponses.org/compliance",
  "type": "sdk",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "openresponses/openresponses",
    "role": "Compliance suite",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Published suite: Browser Runnable 10 tests and CLI Only 7 tests against the OpenAPI schema.",
    "full_detail_md": "The acceptance-test page says to test any API endpoint for Open Responses specification compliance and validate responses against the OpenAPI schema, listing Browser Runnable 10 tests and CLI Only 7 tests. The repository README on main places the CLI runner at bin/compliance-test.ts; that path is the working tree, and the published page is what grades the suite.",
    "facets": {
     "endpoint_or_route": "Any API endpoint supplied to the published acceptance-test page",
     "streaming_or_items": "CLI WebSocket group creates a response over WebSocket and validates returned streaming events",
     "tool_or_state_model": "Validates responses against the OpenAPI schema",
     "sdk_or_version": "Browser Runnable 10 tests and CLI Only 7 tests; bin/compliance-test.ts is the main-branch runner path, distinct from the dated OpenAPI release"
    },
    "telemetry": null,
    "source_url": "https://www.openresponses.org/compliance"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.openresponses.org/compliance",
  "note": "Published suite: Browser Runnable 10 tests and CLI Only 7 tests against the OpenAPI schema."
 },
 {
  "id": "openresponses-python-examples",
  "org_id": "udapy",
  "name": "openresponses-python examples",
  "url": "https://udapy.github.io/openresponses-python/examples/",
  "type": "sdk",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "openresponses-python examples",
    "role": "Example proxy roster",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Example proxies listen on `8001` (OpenRouter), `8002` (OpenAI), `8003` (Ollama), `8004` (LM Studio), and `8005` (Hugging Face).",
    "full_detail_md": "The examples page says the `openresponses-python` repository includes proxy implementations that adapt providers to Open Responses. OpenRouter uses `OPENROUTER_API_KEY` on port `8001`, OpenAI uses `OPENAI_API_KEY` on `8002`, Ollama proxies `localhost:11434` on `8003`, LM Studio proxies `localhost:1234` on `8004`, and Hugging Face uses `HF_API_KEY` and `HF_BASE_URL` on `8005`.",
    "facets": {
     "endpoint_or_route": "Local proxy ports 8001 OpenRouter, 8002 OpenAI, 8003 Ollama, 8004 LM Studio, 8005 Hugging Face",
     "streaming_or_items": "The examples page does not name a streaming flag",
     "tool_or_state_model": "Provider proxies in the examples directory",
     "sdk_or_version": "openresponses-python examples page"
    },
    "telemetry": null,
    "source_url": "https://udapy.github.io/openresponses-python/examples/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://udapy.github.io/openresponses-python/examples/",
  "note": "Example proxies listen on `8001` (OpenRouter), `8002` (OpenAI), `8003` (Ollama), `8004` (LM Studio), and `8005` (Hugging Face)."
 },
 {
  "id": "openrouter",
  "org_id": "openrouter",
  "name": "OpenRouter",
  "url": "https://openrouter.ai/api/v1/responses",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "OpenRouter",
    "role": "Model router",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "POST `https://openrouter.ai/api/v1/responses` for streaming or non-streaming OpenResponses. Matt Apperson (OpenRouter) is an initial TSC voting member.",
    "full_detail_md": "OpenRouter's create-a-response reference documents POST https://openrouter.ai/api/v1/responses and says it creates a streaming or non-streaming response using the OpenResponses API format, and that previous_response_id is not supported on this proxy because each request is independent. Agno lists OpenRouter among providers that implement the spec. Matt Apperson (OpenRouter) is an initial TSC voting member.",
    "facets": {
     "endpoint_or_route": "POST https://openrouter.ai/api/v1/responses",
     "streaming_or_items": "streaming or non-streaming response in the OpenResponses API format",
     "tool_or_state_model": "previous_response_id is not supported; each response request is independent",
     "sdk_or_version": "Agno lists OpenRouter as an implementer; the reference page prints no release version"
    },
    "telemetry": null,
    "source_url": "https://openrouter.ai/docs/api/api-reference/responses/create-a-response"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://openrouter.ai/docs/api/api-reference/responses/create-a-response",
  "note": "POST `https://openrouter.ai/api/v1/responses` for streaming or non-streaming OpenResponses. Matt Apperson (OpenRouter) is an initial TSC voting member."
 },
 {
  "id": "opg-optica-org",
  "org_id": "optica-publishing-group",
  "name": "Optica Publishing Group",
  "url": "https://opg.optica.org/.well-known/tdmrep.json",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Optica Publishing Group",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Well-known `tdmrep.json` (HTTP 200, `application/json`, checked 2026-10-30) sets `location` `/`, `tdm-reservation` 1, and `tdm-policy` `https://opg.optica.org/policies/opg-tdm-policy.json`. The adopters list also records Crossref metadata and PDF XMP Metadata, with a policy.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "attachment": "well-known",
     "location": "/",
     "tdm_reservation": 1,
     "tdm_policy": "https://opg.optica.org/policies/opg-tdm-policy.json"
    },
    "source_url": "https://opg.optica.org/.well-known/tdmrep.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://opg.optica.org/.well-known/tdmrep.json",
  "note": "Well-known `tdmrep.json` (HTTP 200, `application/json`, checked 2026-10-30) sets `location` `/`, `tdm-reservation` 1, and `tdm-policy` `https://opg.optica.org/policies/opg-tdm-policy.json`. The adopters list also records Crossref metadata and PDF XMP Metadata, with a policy."
 },
 {
  "id": "ora-is-agentic-com",
  "org_id": "ora-is-agentic-com",
  "name": "Ora is-agentic.com",
  "url": "https://is-agentic.com/",
  "type": "authority",
  "implements": [
   "vercel-agent-readability"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "vercel-agent-readability",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Ora is-agentic.com",
    "role": "Validator / CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-28",
    "col4_md": "Scores the public parts of a site that agents can discover, retrieve, understand, and use. Essential checks cover server-rendered content, HTTP behavior, document structure, recoverable errors, usable controls, and citation metadata. A live probe of `https://is-agentic.com/api/v1/report?url=vercel.com` on 2026-10-28 scored vercel.com 96/100 (33 eligible checks).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://is-agentic.com/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://is-agentic.com/",
  "note": "Scores the public parts of a site that agents can discover, retrieve, understand, and use. Essential checks cover server-rendered content, HTTP behavior, document structure, recoverable errors, usable controls, and citation metadata. A live probe of `https://is-agentic.com/api/v1/report?url=vercel.com` on 2026-10-28 scored vercel.com 96/100 (33 eligible checks)."
 },
 {
  "id": "oracle-agent-spec",
  "org_id": "oracle",
  "name": "Oracle Agent Spec",
  "url": "https://oracle.github.io/agent-spec/development/howtoguides/howto_ag_ui.html",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Oracle Agent Spec",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · as of 2025-12-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-12-18",
    "col4_md": "JSON Agent Spec config keeps `LangGraph` or `WayFlow`; adapter maps tracing to AG-UI events.",
    "full_detail_md": "A portable Agent Spec configuration (JSON) can be used from AG-UI frontends while keeping the runtime (`LangGraph` or `WayFlow`), and the adapter bridges Agent Spec Tracing and AG-UI events so frontends receive standardized messages, tool activity, and UI state. On 2025-12-18 CopilotKit wrote that Oracle's Open Agent Specification (Agent Spec) and AG-UI now work together, and the overview lists Oracle Agent Spec as Supported.",
    "facets": {
     "transport": "AG-UI frontend events bridged from Agent Spec tracing",
     "event_or_state_model": "Standardized messages, tool activity, and UI state",
     "integration_role": "Portable agent-spec adapter",
     "sdk_or_package": "Agent Spec JSON on LangGraph or WayFlow"
    },
    "telemetry": null,
    "source_url": "https://oracle.github.io/agent-spec/development/howtoguides/howto_ag_ui.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://oracle.github.io/agent-spec/development/howtoguides/howto_ag_ui.html",
  "note": "JSON Agent Spec config keeps `LangGraph` or `WayFlow`; adapter maps tracing to AG-UI events."
 },
 {
  "id": "otel-py-genai-agent-frameworks",
  "org_id": "open-telemetry",
  "name": "OpenTelemetry Python GenAI Agent Framework Instrumentations",
  "url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenTelemetry Python GenAI — LlamaIndex, Agno, DSPy, Smolagents & Qwen-Agent",
    "role": "Official OTel agent framework instrumentations",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Released packages in `open-telemetry/opentelemetry-python-genai`: `opentelemetry-instrumentation-genai-llama-index` (`1.3b0`), `opentelemetry-instrumentation-genai-agno` (`1.3b0`), `opentelemetry-instrumentation-genai-dspy` (`1.3b0`), `opentelemetry-instrumentation-genai-smolagents` (`1.2b0`), and `opentelemetry-instrumentation-genai-qwen-agent` (`1.3b0`)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "version": "1.3b0"
    },
    "source_url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "note": "Released packages in `open-telemetry/opentelemetry-python-genai`: `opentelemetry-instrumentation-genai-llama-index` (`1.3b0`), `opentelemetry-instrumentation-genai-agno` (`1.3b0`), `opentelemetry-instrumentation-genai-dspy` (`1.3b0`), `opentelemetry-instrumentation-genai-smolagents` (`1.2b0`), and `opentelemetry-instrumentation-genai-qwen-agent` (`1.3b0`)"
 },
 {
  "id": "otel-py-genai-langchain",
  "org_id": "open-telemetry",
  "name": "opentelemetry-instrumentation-genai-langchain",
  "url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenTelemetry Python GenAI — LangChain (`opentelemetry-instrumentation-genai-langchain`)",
    "role": "Official OTel framework instrumentation (`langchain >= 0.3.22, < 2`)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Released package `1.3b0` in `open-telemetry/opentelemetry-python-genai` (`langchain >= 0.3.22, < 2`, `Semconv status` `development`); emits spans, metrics, and logs according to `semantic-conventions-genai`",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "version": "1.3b0",
     "target_package": "langchain >= 0.3.22, < 2"
    },
    "source_url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "note": "Released package `1.3b0` in `open-telemetry/opentelemetry-python-genai` (`langchain >= 0.3.22, < 2`, `Semconv status` `development`); emits spans, metrics, and logs according to `semantic-conventions-genai`"
 },
 {
  "id": "otel-py-genai-openai-agents",
  "org_id": "open-telemetry",
  "name": "opentelemetry-instrumentation-genai-openai-agents",
  "url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenTelemetry Python GenAI — OpenAI Agents (`opentelemetry-instrumentation-genai-openai-agents`)",
    "role": "Official OTel agent instrumentation (`openai-agents >= 0.3.3, < 1`)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Released package `1.3b0` in `open-telemetry/opentelemetry-python-genai` (superseding deprecated `opentelemetry-instrumentation-openai-agents-v2`); emits spans, metrics, and logs according to `semantic-conventions-genai` via `opentelemetry-util-genai`",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "version": "1.3b0",
     "target_package": "openai-agents >= 0.3.3, < 1"
    },
    "source_url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "note": "Released package `1.3b0` in `open-telemetry/opentelemetry-python-genai` (superseding deprecated `opentelemetry-instrumentation-openai-agents-v2`); emits spans, metrics, and logs according to `semantic-conventions-genai` via `opentelemetry-util-genai`"
 },
 {
  "id": "otel-py-genai-providers",
  "org_id": "open-telemetry",
  "name": "OpenTelemetry Python GenAI Provider Instrumentations",
  "url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenTelemetry Python GenAI — OpenAI, Anthropic, Bedrock & Google GenAI",
    "role": "Official OTel model provider instrumentations",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Released `1.3b0` packages in `open-telemetry/opentelemetry-python-genai` (`opentelemetry-instrumentation-genai-openai`, `opentelemetry-instrumentation-genai-anthropic`, `opentelemetry-instrumentation-genai-bedrock`, `opentelemetry-instrumentation-google-genai`)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "version": "1.3b0"
    },
    "source_url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "note": "Released `1.3b0` packages in `open-telemetry/opentelemetry-python-genai` (`opentelemetry-instrumentation-genai-openai`, `opentelemetry-instrumentation-genai-anthropic`, `opentelemetry-instrumentation-genai-bedrock`, `opentelemetry-instrumentation-google-genai`)"
 },
 {
  "id": "otel-py-genai-skeleton-agents",
  "org_id": "open-telemetry",
  "name": "OpenTelemetry Python GenAI Skeleton Agent Instrumentations",
  "url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "OpenTelemetry Python GenAI — Claude Agent SDK & CrewAI (`1.4b0.dev`)",
    "role": "Official OTel skeleton instrumentations (`claude-agent-sdk`, `crewai`)",
    "status": "Development",
    "status_display": "Development · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Listed under `Unreleased Instrumentations` (`skeleton`, version `1.4b0.dev`) in `open-telemetry/opentelemetry-python-genai` for `claude-agent-sdk >= 0.1.14, < 1` and `crewai >= 1.10.1, < 2`",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "version": "1.4b0.dev",
     "status": "skeleton"
    },
    "source_url": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/open-telemetry/opentelemetry-python-genai/main/README.md",
  "note": "Listed under `Unreleased Instrumentations` (`skeleton`, version `1.4b0.dev`) in `open-telemetry/opentelemetry-python-genai` for `claude-agent-sdk >= 0.1.14, < 1` and `crewai >= 1.10.1, < 2`"
 },
 {
  "id": "owl-anp",
  "org_id": "owl-anp",
  "name": "OWL-ANP",
  "url": "https://github.com/agent-network-protocol/owl_anp",
  "type": "harness",
  "implements": [
   "anp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "OWL-ANP",
    "role": "AI host / assistant",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-03",
    "as_of": null,
    "col4_md": "agent-network-protocol/owl_anp is the matching OWL integration, using the same anp_tool.py HTTP adapter described in the community release note.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/agent-network-protocol/owl_anp"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "recorded",
  "source": "https://github.com/agent-network-protocol/owl_anp",
  "note": "agent-network-protocol/owl_anp is the matching OWL integration, using the same anp_tool.py HTTP adapter described in the community release note."
 },
 {
  "id": "palo-alto-idira",
  "org_id": "palo-alto-networks",
  "name": "Idira Secure AI Agent",
  "url": "https://www.paloaltonetworks.com/blog/identity-security/ai-agent-security-spiffe-machine-identity/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Palo Alto Networks Idira",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2026-07-20",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-07-20",
    "col4_md": "Issues every AI agent a unique SPIFFE Verifiable Identity Document (SVID).",
    "full_detail_md": "On Jul 20, 2026, Palo Alto Networks wrote that the Idira Secure AI Agent solution leverages SPIFFE to issue every AI agent a unique, verifiable cryptographic identity, a SPIFFE Verifiable Identity Document (SVID).",
    "facets": {
     "svid_or_bundle_format": "A SPIFFE Verifiable Identity Document (SVID) for each AI agent.",
     "api_or_federation_surface": "Idira Secure AI Agent solution.",
     "attestation_or_trust_domain": "Each AI agent receives a unique, verifiable cryptographic identity.",
     "verification_posture": "Palo Alto Networks post dated July 20, 2026."
    },
    "telemetry": null,
    "source_url": "https://www.paloaltonetworks.com/blog/identity-security/ai-agent-security-spiffe-machine-identity/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.paloaltonetworks.com/blog/identity-security/ai-agent-security-spiffe-machine-identity/",
  "note": "Issues every AI agent a unique SPIFFE Verifiable Identity Document (SVID)."
 },
 {
  "id": "pangram",
  "org_id": "pangram",
  "name": "Pangram",
  "url": "https://www.pangram.com/.well-known/agent-card.json",
  "type": "agent",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Pangram",
    "role": "Public A2A agent",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Live Agent Card binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.pangram.com/a2a` for `detect-ai-text` and `detect-ai-image` with `x-api-key`.",
    "full_detail_md": "Pangram serves a live HTTP 200 Agent Card at https://www.pangram.com/.well-known/agent-card.json (v`1.0.0`, checked 2026-10-30) whose `supportedInterfaces` array binds `JSONRPC` (`protocolVersion` `1.0`) at `https://www.pangram.com/a2a` (`streaming`: `false`, `pushNotifications`: `false`, `extendedAgentCard`: `false`) for `detect-ai-text` and `detect-ai-image` classification skills authenticated with a user-supplied `x-api-key`.",
    "facets": {
     "transport_bindings": "JSONRPC at https://www.pangram.com/a2a (supportedInterfaces, streaming: false)",
     "discovery_artifact": "GET https://www.pangram.com/.well-known/agent-card.json (v1.0.0, A2A 1.0 card schema)",
     "protocol_version": "1.0",
     "auth_schemes": "API key header (x-api-key; see /auth.md and /apikey)",
     "verification_posture": "Live HTTP 200 Agent Card probe (checked 2026-10-30)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "protocol_version": "1.0",
     "agent_version": "1.0.0"
    },
    "source_url": "https://www.pangram.com/.well-known/agent-card.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.pangram.com/.well-known/agent-card.json",
  "note": "Live Agent Card binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.pangram.com/a2a` for `detect-ai-text` and `detect-ai-image` with `x-api-key`."
 },
 {
  "id": "particle-pro",
  "org_id": "particle-pro",
  "name": "Particle Pro",
  "url": "https://api.particle.pro/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Particle Pro",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "https://api.particle.pro/auth.md says there is no anonymous agent self-registration. Every credential is tied to a human-owned paid account. A headless agent uses an API key from https://platform.particle.pro/tokens. An agent with no operator can pay per request with x402. Fetched status 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.particle.pro/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.particle.pro/auth.md",
  "note": "https://api.particle.pro/auth.md says there is no anonymous agent self-registration. Every credential is tied to a human-owned paid account. A headless agent uses an API key from https://platform.particle.pro/tokens. An agent with no operator can pay per request with x402. Fetched status 200 on 2026-10-29."
 },
 {
  "id": "pax-ai",
  "org_id": "pax-ai",
  "name": "PAX AI (ax-platform-mcp)",
  "url": "https://raw.githubusercontent.com/ax-platform/ax-platform-mcp/main/README.md",
  "type": "sdk",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "PAX AI (ax-platform-mcp)",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "A Hermes agent, or another shell-capable harness, is pointed at https://paxai.app/auth.md. It learns the device-code flow from that file, shows the approval code, stores refreshable credentials, and joins the aX network on a named MCP route.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/ax-platform/ax-platform-mcp/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/ax-platform/ax-platform-mcp/main/README.md",
  "note": "A Hermes agent, or another shell-capable harness, is pointed at https://paxai.app/auth.md. It learns the device-code flow from that file, shows the approval code, stores refreshable credentials, and joins the aX network on a named MCP route."
 },
 {
  "id": "paypal",
  "org_id": "paypal",
  "name": "PayPal",
  "url": "https://www.paypal.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "PayPal",
    "role": "Payment processor (Payments TC)",
    "status": "Listed",
    "status_display": "Listed · as of 2026-09-02",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-02",
    "col4_md": "Inaugural member of the UCP Payments Technical Council (formed September 2, 2026).",
    "full_detail_md": "PayPal is named on the UCP announcements page as an inaugural member of the Payments Technical Council formed on September 2, 2026 alongside Adyen NV, Ant International, Coinbase, Global Payments, Google, Shopify, and Stripe.",
    "facets": {
     "commerce_surface": "Payments Technical Council inaugural member",
     "payment_handlers_or_rail": "Inaugural member of the UCP Payments Technical Council",
     "transport_bindings": "Governance and technical council participation",
     "spec_version": "Payments Technical Council formed September 2, 2026"
    },
    "telemetry": null,
    "source_url": "https://ucp.dev/documentation/announcements/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://ucp.dev/documentation/announcements/",
  "note": "Inaugural member of the UCP Payments Technical Council (formed September 2, 2026)."
 },
 {
  "id": "paypal-as-meta",
  "org_id": "paypal",
  "name": "PayPal MCP authorization server",
  "url": "https://mcp.paypal.com",
  "type": "authority",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "PayPal",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`issuer` `https://mcp.paypal.com`; `S256`; `authorization_code`, `refresh_token`; `registration_endpoint`; `client_id_metadata_document_supported` `false`.",
    "full_detail_md": "GET https://mcp.paypal.com/.well-known/oauth-authorization-server returned HTTP 200 `application/json`. `issuer` is `https://mcp.paypal.com`. `authorization_endpoint`, `token_endpoint`, and `registration_endpoint` are on that host. `grant_types_supported` are `authorization_code` and `refresh_token`. `code_challenge_methods_supported` is `S256`. `client_id_metadata_document_supported` is `false`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.paypal.com/.well-known/oauth-authorization-server (issuer https://mcp.paypal.com; authorization, token, and registration endpoints on that host)",
     "registration_or_client_id_modes": "registration_endpoint https://mcp.paypal.com/register; client_id_metadata_document_supported false; token_endpoint_auth_methods client_secret_basic, client_secret_post, none",
     "pkce_or_grant_types": "PKCE S256; grant_types_supported authorization_code and refresh_token",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://mcp.paypal.com",
     "client_id_metadata_document_supported": false
    },
    "source_url": "https://mcp.paypal.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.paypal.com/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://mcp.paypal.com`; `S256`; `authorization_code`, `refresh_token`; `registration_endpoint`; `client_id_metadata_document_supported` `false`."
 },
 {
  "id": "peac",
  "org_id": "peac",
  "name": "PEAC Protocol",
  "url": "https://www.peacprotocol.org/integrations/content-signals",
  "type": "sdk",
  "implements": [
   "aipref-content-usage-attachment"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "PEAC Protocol",
    "role": "Parser",
    "status": "Partial",
    "status_display": "Partial · as of 2026-06-01",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-01",
    "col4_md": "Coverage is the Content-Usage HTTP header, identified on the page with `draft-ietf-aipref-attach-04` and Structured Fields per `RFC 9651`. The page says the `Content-Usage` header is parsed as an RFC 9651 Structured Fields Dictionary, and that PEAC records these signals as evidence but does not enforce them. Page `dateModified` is 2026-06-01.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.peacprotocol.org/integrations/content-signals"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.peacprotocol.org/integrations/content-signals",
  "note": "Coverage is the Content-Usage HTTP header, identified on the page with `draft-ietf-aipref-attach-04` and Structured Fields per `RFC 9651`. The page says the `Content-Usage` header is parsed as an RFC 9651 Structured Fields Dictionary, and that PEAC records these signals as evidence but does not enforce them. Page `dateModified` is 2026-06-01."
 },
 {
  "id": "penguin-random-house-germany",
  "org_id": "penguin-random-house-germany",
  "name": "Penguin Random House Germany",
  "url": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md",
  "type": "origin",
  "implements": [
   "tdmrep"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "tdmrep",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Penguin Random House Germany",
    "role": "Publisher",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Adopters list: Penguin Random House Germany: in its ONIX records.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/w3c-cg/tdm-reservation-protocol/main/docs/adopters.md",
  "note": "Adopters list: Penguin Random House Germany: in its ONIX records."
 },
 {
  "id": "perplexity-crawlers",
  "org_id": "perplexity",
  "name": "Perplexity crawlers",
  "url": "https://docs.perplexity.ai/docs/resources/perplexity-crawlers",
  "type": "agent",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Perplexity",
    "role": "Crawler operator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`PerplexityBot` indexes search results (no foundation model training); `Perplexity-User` handles user fetches and generally ignores `robots.txt`.",
    "full_detail_md": "`PerplexityBot` surfaces and links websites in search results and is not used to crawl content for AI foundation models. `Perplexity-User` supports user actions, is not used to collect content for training AI foundation models, and generally ignores robots.txt rules because a user requested the fetch.",
    "facets": {
     "user_agent_token": [
      "PerplexityBot",
      "Perplexity-User"
     ],
     "operator_purpose": "PerplexityBot: search result indexing (no foundation model training); Perplexity-User: user-initiated fetches",
     "ip_verification_url": "https://docs.perplexity.ai/docs/resources/perplexity-crawlers",
     "robots_directives_honored": "PerplexityBot honors robots.txt; Perplexity-User generally ignores robots.txt rules"
    },
    "telemetry": null,
    "source_url": "https://docs.perplexity.ai/docs/resources/perplexity-crawlers"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.perplexity.ai/docs/resources/perplexity-crawlers",
  "note": "`PerplexityBot` indexes search results (no foundation model training); `Perplexity-User` handles user fetches and generally ignores `robots.txt`."
 },
 {
  "id": "pg-ddx-io",
  "org_id": "pg-ddx-io",
  "name": "pg.ddx.io",
  "url": "https://pg.ddx.io/agents.txt",
  "type": "origin",
  "implements": [
   "agents-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "pg.ddx.io",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring an MCP server and a list of Skills files",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "/agents.txt"
    },
    "source_url": "https://pg.ddx.io/agents.txt"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://pg.ddx.io/agents.txt",
  "note": "Serves `/agents.txt` (fetched 2026-10-29) opening with `# Standard: https://agents-txt.com`, declaring an MCP server and a list of Skills files"
 },
 {
  "id": "pingfederate-id-jag",
  "org_id": "ping-identity",
  "name": "PingFederate 13.1.4",
  "url": "https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_refresh_token_to_idjag_exchange.html",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Ping Identity",
    "role": "ID-JAG issuer (PingFederate)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "PingFederate Server Version 13.1.4 (Latest) documents a refresh token-to-ID-JAG token exchange. Issued ID-JAG tokens use the typ header value `oauth-id-jag+jwt`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_refresh_token_to_idjag_exchange.html"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_configuring_refresh_token_to_idjag_exchange.html",
  "note": "PingFederate Server Version 13.1.4 (Latest) documents a refresh token-to-ID-JAG token exchange. Issued ID-JAG tokens use the typ header value `oauth-id-jag+jwt`."
 },
 {
  "id": "pingone-aic-cimd",
  "org_id": "ping-identity",
  "name": "PingOne Advanced Identity Cloud",
  "url": "https://www.pingidentity.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "PingOne Advanced Identity Cloud",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Fetches the JSON document at the HTTPS `client_id` and configures the client at runtime, with no prior registration required.",
    "full_detail_md": "PingOne Advanced Identity Cloud lets OAuth 2.0 clients identify themselves with an HTTPS URL as their `client_id`. It fetches that JSON metadata document and configures the client at runtime. The page says this is suited to large numbers of clients such as AI agents in Model Context Protocol (MCP) flows, and that the support aligns with the IETF OAuth Client ID Metadata Document draft.",
    "facets": {
     "metadata_flag_or_profile": "HTTPS URL used as client_id; JSON metadata document fetched at runtime",
     "auth_method_or_pkce": "The overview does not name a PKCE method",
     "uri_or_ssrf_rules": "No prior registration; the server fetches the document at the client_id URL",
     "draft_or_spec_version": "Aligns with the IETF OAuth Client ID Metadata Document draft; the page does not name a revision number"
    },
    "telemetry": null,
    "source_url": "https://docs.pingidentity.com/pingone/applications_overview/p1_client_id_metadata_document.html"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://docs.pingidentity.com/pingone/applications_overview/p1_client_id_metadata_document.html",
  "note": "Fetches the JSON document at the HTTPS `client_id` and configures the client at runtime, with no prior registration required."
 },
 {
  "id": "planetscale-com",
  "org_id": "planetscale",
  "name": "PlanetScale",
  "url": "https://planetscale.com/.well-known/api-catalog",
  "type": "origin",
  "implements": [
   "api-catalog-rfc9727",
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "PlanetScale",
    "role": "Database platform API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`application/linkset+json` anchors `https://api.planetscale.com/v1` with `service-desc` `openapi.yaml`, not an `item` array.",
    "full_detail_md": "On 2026-11-04, `https://planetscale.com/.well-known/api-catalog` returned HTTP 200 (`content-type: application/linkset+json`, `content-length: 347`) with no RFC 9727 profile parameter, no `Link` response header, and no `item` array. The anchor `https://api.planetscale.com/v1` links `service-desc` to `https://planetscale.com/docs/openapi.yaml` (`text/yaml`) and `service-doc` to `https://planetscale.com/docs/api/openapi-spec`.",
    "facets": {
     "well_known_endpoint": "https://planetscale.com/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json (no profile parameter)",
     "link_relations": "service-desc (https://planetscale.com/docs/openapi.yaml, text/yaml); service-doc; no item array",
     "http_or_link_header": "HTTP 200; no Link rel=api-catalog response header"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json",
     "link_header_rel_api_catalog": false,
     "has_item_array": false
    },
    "source_url": "https://planetscale.com/.well-known/api-catalog"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "PlanetScale",
    "role": "Product site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`HTTP/2 200` `text/markdown; charset=utf-8` with `vary: accept-encoding, accept` via `server: cloudflare`.",
    "full_detail_md": "Fetched with Markdown content negotiation on 2026-11-03, PlanetScale returned `HTTP/2 200` with `content-type: text/markdown; charset=utf-8`, `vary: accept-encoding, accept`, `content-signal: ai-train=yes, search=yes, ai-input=yes`, and `server: cloudflare`. The page title is PlanetScale's cloud hosting line for Vitess, Neki, and Postgres.",
    "facets": {
     "negotiation_or_artifact": "Live Accept negotiation of https://planetscale.com/",
     "response_headers": "HTTP/2 200; vary: accept-encoding, accept; content-signal ai-train=yes, search=yes, ai-input=yes; server: cloudflare",
     "content_type_or_tokens": "text/markdown; charset=utf-8",
     "verification_posture": "Live HTTP probe checked 2026-11-03 (response date Tue, 03 Nov 2026 21:03:57 GMT)"
    },
    "telemetry": {
     "artifact_kind": "negotiated_markdown",
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "content_signal": "ai-train=yes, search=yes, ai-input=yes",
     "vary": "accept-encoding, accept",
     "server": "cloudflare",
     "marker": "content-type: text/markdown; charset=utf-8"
    },
    "source_url": "https://planetscale.com/"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://planetscale.com/.well-known/api-catalog",
  "note": "`application/linkset+json` anchors `https://api.planetscale.com/v1` with `service-desc` `openapi.yaml`, not an `item` array."
 },
 {
  "id": "platform-claude-com-llms-txt",
  "org_id": "anthropic",
  "name": "Anthropic Developer Documentation",
  "url": "https://platform.claude.com/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Anthropic (Claude API docs)",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `https://platform.claude.com/llms.txt` as `text/plain` (`# Anthropic Developer Documentation`), indexing 826 `/docs` pages, `llms-full.txt`, and `https://platform.claude.com/docs/mcp`.",
    "full_detail_md": "Serves `https://platform.claude.com/llms.txt` as `text/plain; charset=utf-8` (144,969 bytes, fetched 2026-10-30). The file opens `# Anthropic Developer Documentation`, indexes 826 English documentation pages under `/docs`, points MCP clients to `https://platform.claude.com/docs/mcp` (Streamable HTTP transport), and links `llms-full.txt` and `https://platform.claude.com/docs/sdk-versions.json`.",
    "facets": {
     "artifact_path": "https://platform.claude.com/llms.txt",
     "companion_files": "https://platform.claude.com/llms-full.txt; https://platform.claude.com/docs/mcp; https://platform.claude.com/docs/sdk-versions.json",
     "content_type_or_bytes": "text/plain; charset=utf-8 (144,969 bytes)",
     "generator_or_consumer_mode": "Origin documentation index (826 English pages under /docs)"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "marker": "# Anthropic Developer Documentation",
     "content_type": "text/plain; charset=utf-8"
    },
    "source_url": "https://platform.claude.com/llms.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://platform.claude.com/llms.txt",
  "note": "Serves `https://platform.claude.com/llms.txt` as `text/plain` (`# Anthropic Developer Documentation`), indexing 826 `/docs` pages, `llms-full.txt`, and `https://platform.claude.com/docs/mcp`."
 },
 {
  "id": "postalform",
  "org_id": "postalform",
  "name": "PostalForm",
  "url": "https://postalform.com",
  "type": "origin",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "PostalForm",
    "role": "Seller",
    "status": "Listed",
    "status_display": "Listed · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Catalog active: `tempo` and `stripe` `charge`; POST `/api/machine/mpp/orders` pays print-and-mail.",
    "full_detail_md": "The catalog lists PostalForm as active, with methods tempo and stripe, intent charge, and assets 0x20c000000000000000000000b9537d11c60e8b50 and usd. POST /api/machine/mpp/orders creates and pays for a print-and-mail order.",
    "facets": {
     "settlement_rail": "tempo and stripe charge; assets 0x20c000000000000000000000b9537d11c60e8b50 and usd",
     "challenge_or_scheme": "Catalog status active (a directory record, not a live execution probe)",
     "headers_or_methods": "Payment method tempo and stripe, intent charge",
     "sdk_or_endpoint": "POST /api/machine/mpp/orders creates and pays for a print-and-mail order"
    },
    "telemetry": null,
    "source_url": "https://mpp.dev/api/services"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.dev/api/services",
  "note": "Catalog active: `tempo` and `stripe` `charge`; POST `/api/machine/mpp/orders` pays print-and-mail."
 },
 {
  "id": "posthog",
  "org_id": "posthog",
  "name": "PostHog",
  "url": "https://us.posthog.com/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "PostHog",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://us.posthog.com/auth.md documents npx @posthog/wizard@latest --signup, the Provisioning API, OAuth 2.0, and personal API keys. Enterprise ID-JAG registration is marked beta and XAA-only: the agent presents an identity_assertion to the token endpoint with the JWT-bearer grant. PostHog's docs say agents should use the published metadata and not a PostHog-specific SDK.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://us.posthog.com/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://us.posthog.com/auth.md",
  "note": "https://us.posthog.com/auth.md documents npx @posthog/wizard@latest --signup, the Provisioning API, OAuth 2.0, and personal API keys. Enterprise ID-JAG registration is marked beta and XAA-only: the agent presents an identity_assertion to the token endpoint with the JWT-bearer grant. PostHog's docs say agents should use the published metadata and not a PostHog-specific SDK."
 },
 {
  "id": "postman",
  "org_id": "postman",
  "name": "Postman",
  "url": "https://learning.postman.com/docs/use/send-requests/protocols/mcp-requests/interact/",
  "type": "harness",
  "implements": [
   "mcp-apps"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Postman",
    "role": "API client",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Response pane can preview interactive UI from MCP Apps Extension servers.",
    "full_detail_md": "Postman documents that servers supporting the MCP Apps Extension can return interactive user interfaces on an MCP request, and that the response pane can preview that interface. The page does not publish a dated host version, so the row stays a documentation citation with no as-of date.",
    "facets": {
     "transport_or_channel": "MCP request whose response can include an MCP Apps Extension UI",
     "ui_resource_or_primitive": "Interactive user interface previewed in the response pane",
     "sandbox_or_security": "Docs do not restate CSP or iframe sandbox flags",
     "sdk_or_version": "Undated Postman MCP interaction docs; no package version printed"
    },
    "telemetry": null,
    "source_url": "https://learning.postman.com/docs/use/send-requests/protocols/mcp-requests/interact/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://learning.postman.com/docs/use/send-requests/protocols/mcp-requests/interact/",
  "note": "Response pane can preview interactive UI from MCP Apps Extension servers."
 },
 {
  "id": "prebid-sales-agent",
  "org_id": "prebid",
  "name": "Prebid Sales Agent",
  "url": "https://github.com/prebid/salesagent",
  "type": "sdk",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Prebid Sales Agent",
    "role": "Sales agent",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-28",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-28",
    "col4_md": "Open-source AdCP sales-agent role maintained under Prebid.org, with MCP and A2A interfaces. The README says Status: alpha, a pre-1.0 implementation of AdCP `3.1.1` via the `adcp==6.6.0` Python SDK. The AdCP introduction calls it a community example, not a maintained reference implementation, and a full-stack seller agent with a Python backend, a TypeScript protocol layer, and GAM integration. AdExchanger says the Prebid Sales Agent is now available to all publishers. Last pushed on 2026-10-28.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/prebid/salesagent/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/prebid/salesagent/main/README.md",
  "note": "Open-source AdCP sales-agent role maintained under Prebid.org, with MCP and A2A interfaces. The README says Status: alpha, a pre-1.0 implementation of AdCP `3.1.1` via the `adcp==6.6.0` Python SDK. The AdCP introduction calls it a community example, not a maintained reference implementation, and a full-stack seller agent with a Python backend, a TypeScript protocol layer, and GAM integration. AdEx"
 },
 {
  "id": "print-with-poppy",
  "org_id": "print-with-poppy",
  "name": "Print with Poppy",
  "url": "https://printwithpoppy.com/.well-known/poppy.json",
  "type": "origin",
  "implements": [
   "personal-agent-protocol"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "personal-agent-protocol",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Print with Poppy",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-29",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-29",
    "as_of": "2026-10-29",
    "col4_md": "https://printwithpoppy.com/.well-known/poppy.json, seen 2026-10-29, is protocol_version 0.3 with organization.name Print with Poppy and organization.domain printwithpoppy.com. The project demo page describes it as a photo-printing store where the personal agent places the order, and says live orders are charged, printed, and shipped.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json"
    },
    "source_url": "https://printwithpoppy.com/.well-known/poppy.json"
   }
  ],
  "observed": "2026-10-29",
  "date_basis": "source",
  "source": "https://printwithpoppy.com/.well-known/poppy.json",
  "note": "https://printwithpoppy.com/.well-known/poppy.json, seen 2026-10-29, is protocol_version 0.3 with organization.name Print with Poppy and organization.domain printwithpoppy.com. The project demo page describes it as a photo-printing store where the personal agent places the order, and says live orders are charged, printed, and shipped."
 },
 {
  "id": "proof",
  "org_id": "proof",
  "name": "Proof",
  "url": "https://www.proof.com/x401",
  "type": "authority",
  "implements": [
   "x401"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "x401",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Proof",
    "role": "Identity issuer / Signer",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Credential issuer for an x401 challenge. The product page states x401 v0.1.0, OpenID4VP, DCQL, and credential format `jwt_vc_json`, with the challenge carried as `PROOF-REQUIRED: <base64url-x401-payload>`. The current editor's draft is 0.2.0.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.proof.com/x401"
   },
   {
    "protocol_id": "x401",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Proof (@proof.com/x401-workers)",
    "role": "Relying server / Verifier",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-17",
    "col4_md": "Cloudflare Worker verifier: a request without a verified Digital ID gets status 401 carrying a presentation request in `PROOF-REQUEST` (without a `WWW-Authenticate` header), and the handler runs only after the presentation is verified. npm package `@proof.com/x401-workers` was created 2026-10-17 (Apache-2.0).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://dev.proof.com/docs/x401-cloudflare"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.proof.com/x401",
  "note": "Credential issuer for an x401 challenge. The product page states x401 v0.1.0, OpenID4VP, DCQL, and credential format `jwt_vc_json`, with the challenge carried as `PROOF-REQUIRED: <base64url-x401-payload>`. The current editor's draft is 0.2.0."
 },
 {
  "id": "pubmatic-agenticos",
  "org_id": "pubmatic",
  "name": "PubMatic AgenticOS",
  "url": "https://pubmatic.com/news/pubmatic-launches-agenticos-the-operating-system-for-agent-to-agent-advertising/",
  "type": "origin",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "PubMatic AgenticOS",
    "role": "Ad-tech platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-05",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-05",
    "col4_md": "On 2026-01-05 PubMatic announced PubMatic AgenticOS. The announcement says agentic capabilities embedded across the platform interpret intent expressed through the Ad Context Protocol (AdCP) and Model Context Protocol (MCP).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pubmatic.com/news/pubmatic-launches-agenticos-the-operating-system-for-agent-to-agent-advertising/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pubmatic.com/news/pubmatic-launches-agenticos-the-operating-system-for-agent-to-agent-advertising/",
  "note": "On 2026-01-05 PubMatic announced PubMatic AgenticOS. The announcement says agentic capabilities embedded across the platform interpret intent expressed through the Ad Context Protocol (AdCP) and Model Context Protocol (MCP)."
 },
 {
  "id": "pulsemcp",
  "org_id": "pulsemcp",
  "name": "PulseMCP",
  "url": "https://www.pulsemcp.com/work-with-us",
  "type": "venue",
  "implements": [
   "mcp",
   "mcp-registry"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "PulseMCP",
    "role": "Sub-registry & directory",
    "status": "Partial",
    "status_display": "Partial · as of 2025-09-09",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-09",
    "col4_md": "Ingests the Official MCP Registry as a downstream sub-registry supplemented with web indexing; live directory temporarily pauses new submissions.",
    "full_detail_md": "Operates as a downstream sub-registry of the Official MCP Registry while supplementing official entries with web-wide server indexing, standardized names and descriptions, and estimated download metrics for marketplace curation; the live server directory homepage notes that new server submissions and listing changes stay paused while ingestion is reworked.",
    "facets": {
     "transport": "HTTPS sub-registry & directory",
     "auth_or_oauth": "Public catalog",
     "primitives": "Sub-registry metadata, estimated downloads",
     "sdk_or_package": "Official MCP Registry sub-registry"
    },
    "telemetry": null,
    "source_url": "https://www.pulsemcp.com/work-with-us"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "PulseMCP",
    "role": "Directory and sub-registry",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Ingests the official registry and is setting itself up as a downstream sub-registry for marketplace curation.",
    "full_detail_md": "PulseMCP says it ingests from the official registry and supplements that with its own indexing across the web. Its launch newsletter says it is setting PulseMCP up as a sub-registry of the official registry so marketplace operators can use Pulse data to curate MCP marketplaces.",
    "facets": {
     "registry_or_namespace": "PulseMCP sub-registry of the official registry",
     "api_or_schema_version": "Official-registry ingest plus PulseMCP's own web index",
     "transport_or_package_types": "Directory metadata used to curate MCP marketplaces",
     "verification_posture": "Document citation of the PulseMCP work-with-us page and launch newsletter (checked 2026-10-30; pages undated)"
    },
    "telemetry": null,
    "source_url": "https://www.pulsemcp.com/work-with-us"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.pulsemcp.com/work-with-us",
  "note": "Ingests the Official MCP Registry as a downstream sub-registry supplemented with web indexing; live directory temporarily pauses new submissions."
 },
 {
  "id": "pydantic-ai",
  "org_id": "pydantic",
  "name": "Pydantic AI",
  "url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "type": "sdk",
  "implements": [
   "a2a",
   "ag-ui",
   "llms-txt"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Pydantic AI",
    "role": "Agent framework",
    "status": "Listed",
    "status_display": "Listed · as of 2026-08-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-27",
    "col4_md": "AAIF proposal lists native `FastA2A` library integration exposing `Pydantic AI` agents as `ASGI` A2A applications.",
    "full_detail_md": "The A2A project blog (2026-08-27) names `Pydantic AI` among supporting frameworks, and the AAIF Growth Stage proposal (#37) states that `Pydantic AI` provides native A2A support through the `FastA2A` library using `.to_a2a()` to convert a Pydantic AI agent into an `ASGI` A2A application.",
    "facets": {
     "transport_bindings": "ASGI HTTP A2A application via FastA2A (.to_a2a())",
     "discovery_artifact": "FastA2A ASGI Agent Card endpoint",
     "protocol_version": "Not specified in AAIF proposal (2026-08-27 blog / proposal #37)",
     "auth_schemes": "ASGI middleware configuration",
     "verification_posture": "Listed in A2A blog (2026-08-27) and AAIF proposal #37"
    },
    "telemetry": null,
    "source_url": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/"
   },
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Pydantic AI",
    "role": "Framework docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://ai.pydantic.dev/llms.txt` (`# Pydantic AI`, `text/plain`), requesting `intent`, `stack`, and `harness` query parameters on fetches.",
    "full_detail_md": "Serves `https://ai.pydantic.dev/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 70,916 bytes, fetched 2026-11-04) via a Cloudflare Worker (`x-pydantic-site-worker: 1`), opening with a `## Querying This Documentation` section asking agents to pass `?intent=<intent>&stack=<stack>&harness=<harness>` query parameters before indexing `# Pydantic AI` `.md` documentation pages.",
    "facets": {
     "artifact_path": "https://ai.pydantic.dev/llms.txt",
     "companion_files": ".md documentation twins under /docs/ai/; agent telemetry query parameters (?intent=&stack=&harness=)",
     "content_type_or_bytes": "text/plain; charset=utf-8 (70,916 bytes)",
     "generator_or_consumer_mode": "Worker-served documentation index with agent telemetry query parameters"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Pydantic AI"
    },
    "source_url": "https://ai.pydantic.dev/llms.txt"
   },
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Pydantic AI",
    "role": "Agent framework",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`AGUIAdapter.dispatch_request()` and `run_stream()` return a stream of AG-UI events.",
    "full_detail_md": "Pydantic AI documents AG-UI as an open standard introduced by the CopilotKit team, with support for streaming, frontend tools, shared state, and custom events, contributed with the Pydantic AI and CopilotKit teams. `AGUIAdapter.dispatch_request()` takes a Starlette request from an AG-UI frontend and returns a streaming response, `AGUIAdapter.run_stream()` runs the agent and returns a stream of AG-UI events, and the overview lists Pydantic AI as Supported.",
    "facets": {
     "transport": "Starlette streaming HTTP response (binding not further named)",
     "event_or_state_model": "Streaming AG-UI events, frontend tools, shared state, and custom events",
     "integration_role": "Agent framework adapter",
     "sdk_or_package": "AGUIAdapter (dispatch_request and run_stream)"
    },
    "telemetry": null,
    "source_url": "https://pydantic.dev/docs/ai/integrations/ui/ag-ui/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://a2a-protocol.org/latest/blog/2026/08/27/a-new-chapter-for-a2a-joining-the-agentic-ai-foundation/",
  "note": "AAIF proposal lists native `FastA2A` library integration exposing `Pydantic AI` agents as `ASGI` A2A applications."
 },
 {
  "id": "pydantic-ai-agents-md",
  "org_id": "pydantic",
  "name": "pydantic/pydantic-ai",
  "url": "https://raw.githubusercontent.com/pydantic/pydantic-ai/main/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "pydantic/pydantic-ai",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves root `AGENTS.md` (`text/plain`, 19,537 bytes) linking 18 nested `AGENTS.md` files across `docs/`, `pydantic_ai_slim/`, and `tests/`.",
    "full_detail_md": "Serves root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 19,537 bytes, checked 2026-11-04) opening with `# Your primary responsibility is to the project and its users`, requiring 100% test coverage and in-process test execution, and indexing 18 nested subdirectory `AGENTS.md` files across `docs/`, `pydantic_ai_slim/pydantic_ai/`, `src/pydantic_ai_harness/`, and `tests/`.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/pydantic/pydantic-ai/main/AGENTS.md",
     "repo_scope": "Pydantic AI workspace root (19,537 bytes) plus 18 linked nested subdirectory AGENTS.md files",
     "heading_structure": "# Your primary responsibility is to the project and its users; # Gathering context on the task; # Philosophy; # Requirements of all contributions; # Coding Guidelines",
     "precedence_or_nested_files": "Links 18 nested AGENTS.md files (docs/*, pydantic_ai_slim/pydantic_ai/*, src/pydantic_ai_harness/AGENTS.md, tests/AGENTS.md, tests/harness/AGENTS.md)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Your primary responsibility is to the project and its users"
    },
    "source_url": "https://raw.githubusercontent.com/pydantic/pydantic-ai/main/AGENTS.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/pydantic/pydantic-ai/main/AGENTS.md",
  "note": "Serves root `AGENTS.md` (`text/plain`, 19,537 bytes) linking 18 nested `AGENTS.md` files across `docs/`, `pydantic_ai_slim/`, and `tests/`."
 },
 {
  "id": "pydantic-logfire",
  "org_id": "pydantic",
  "name": "Pydantic Logfire / Pydantic AI",
  "url": "https://ai.pydantic.dev/logfire/",
  "type": "sdk",
  "implements": [
   "otel-genai-semconv"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "otel-genai-semconv",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "Pydantic Logfire / Pydantic AI",
    "role": "Agent framework instrumentation",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`logfire.instrument_pydantic_ai()` enables instrumentation of Pydantic AI (fetched `2026-11-04`), following the OpenTelemetry Semantic Conventions for Generative AI systems (`gen_ai.operation.name`, `gen_ai.provider.name`, `gen_ai.request.model`, `gen_ai.response.model`, `gen_ai.client.token.usage`).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://ai.pydantic.dev/logfire/"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://ai.pydantic.dev/logfire/",
  "note": "`logfire.instrument_pydantic_ai()` enables instrumentation of Pydantic AI (fetched `2026-11-04`), following the OpenTelemetry Semantic Conventions for Generative AI systems (`gen_ai.operation.name`, `gen_ai.provider.name`, `gen_ai.request.model`, `gen_ai.response.model`, `gen_ai.client.token.usage`)."
 },
 {
  "id": "quicknode-erc-8004-explorer",
  "org_id": "quicknode",
  "name": "Quicknode ERC-8004 Explorer",
  "url": "https://erc-8004.quicknode.com/",
  "type": "authority",
  "implements": [
   "erc-8004"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Quicknode ERC-8004 Explorer",
    "role": "Explorer / Scanner",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "One JSON-RPC endpoint covers 32 EVM networks; REST bills per request in USDC.",
    "full_detail_md": "Quicknode's ERC-8004 Explorer queries registrations, reputation, feedback, and validations across 32 EVM networks through one JSON-RPC endpoint, sells public REST pay-per-request in USDC over x402, and publishes the composite score formula so a score can be replayed against on-chain events.",
    "facets": {
     "registry_or_contract": "Reads ERC-8004 registrations, reputation, feedback, and validations; not a registry deployment",
     "chains_or_networks": "32 EVM networks through one JSON-RPC endpoint",
     "standards_profile": "ERC-8004 explorer with a public composite score formula",
     "sdk_or_deployment": "Public REST pay-per-request in USDC over x402, plus the Quicknode JSON-RPC API"
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "explorer"
    },
    "source_url": "https://erc-8004.quicknode.com/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://erc-8004.quicknode.com/",
  "note": "One JSON-RPC endpoint covers 32 EVM networks; REST bills per request in USDC."
 },
 {
  "id": "railway",
  "org_id": "railway",
  "name": "Railway",
  "url": "https://railway.com/.well-known/ard.json",
  "type": "origin",
  "implements": [
   "ard"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Railway",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"0.91\"`) with 8 entries, first `urn:air:railway.com:server:railway-mcp` type `application/mcp-server-card+json` at https://railway.com/.well-known/mcp/server-card.json, plus the site's RFC 9727 API catalog (`application/linkset+json`)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://railway.com/.well-known/ard.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://railway.com/.well-known/ard.json",
  "note": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"0.91\"`) with 8 entries, first `urn:air:railway.com:server:railway-mcp` type `application/mcp-server-card+json` at https://railway.com/.well-known/mcp/server-card.json, plus the site's RFC 9727 API catalog (`application/linkset+json`)"
 },
 {
  "id": "raw-githubusercontent-com-fastendpoints-fastendpoints-main-okf-index-md",
  "org_id": "fastendpoints",
  "name": "FastEndpoints",
  "url": "https://raw.githubusercontent.com/FastEndpoints/FastEndpoints/main/.okf/index.md",
  "type": "origin",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "FastEndpoints",
    "role": "Repository publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`okf_version: \"0.1\"` at `.okf/index.md` (`text/plain`, HTTP 200) on main.",
    "full_detail_md": "Serves https://raw.githubusercontent.com/FastEndpoints/FastEndpoints/main/.okf/index.md as text/plain; charset=utf-8 (content-length 1430, HTTP 200, response Date Wed, 04 Nov 2026 22:09:04 GMT). Frontmatter declares okf_version: \"0.1\" under the heading OKF Knowledge Set, which calls the file compact operational knowledge for agents working in the FastEndpoints repository and links ../AGENTS.md; the probed URL is the repository main branch, observed as HTTP 200.",
    "facets": {
     "artifact_or_endpoint": "https://raw.githubusercontent.com/FastEndpoints/FastEndpoints/main/.okf/index.md",
     "content_type_or_schema": "text/plain; charset=utf-8; YAML frontmatter okf_version 0.1",
     "discovery_mechanism": "Repository path .okf/index.md on the main branch",
     "version_or_posture": "HTTP 200 observation of the main-branch index declaring okf_version 0.1, not a tagged release"
    },
    "telemetry": {
     "artifact_kind": "okf_index_md",
     "http_status": 200,
     "marker": "okf_version: \"0.1\""
    },
    "source_url": "https://raw.githubusercontent.com/FastEndpoints/FastEndpoints/main/.okf/index.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/FastEndpoints/FastEndpoints/main/.okf/index.md",
  "note": "`okf_version: \"0.1\"` at `.okf/index.md` (`text/plain`, HTTP 200) on main."
 },
 {
  "id": "raw-githubusercontent-com-floegence-floret-main-okf-index-md",
  "org_id": "floret",
  "name": "Floret",
  "url": "https://raw.githubusercontent.com/floegence/floret/main/okf/index.md",
  "type": "origin",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Floret",
    "role": "Repository publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`okf_version: \"0.1\"` at `okf/index.md` (`text/plain`, HTTP 200) on main.",
    "full_detail_md": "Serves https://raw.githubusercontent.com/floegence/floret/main/okf/index.md as text/plain; charset=utf-8 (content-length 818, HTTP 200, response Date Wed, 04 Nov 2026 22:09:04 GMT). Frontmatter declares okf_version: \"0.1\" under the heading Floret Knowledge Bundle, which says the bundle gives humans and agents a compact map of Floret's purpose, public surface, internal architecture, and maintenance rules; the probed URL is the repository main branch, observed as HTTP 200.",
    "facets": {
     "artifact_or_endpoint": "https://raw.githubusercontent.com/floegence/floret/main/okf/index.md",
     "content_type_or_schema": "text/plain; charset=utf-8; YAML frontmatter okf_version 0.1",
     "discovery_mechanism": "Repository path okf/index.md on the main branch",
     "version_or_posture": "HTTP 200 observation of the main-branch index declaring okf_version 0.1, not a tagged release"
    },
    "telemetry": {
     "artifact_kind": "okf_index_md",
     "http_status": 200,
     "marker": "okf_version: \"0.1\""
    },
    "source_url": "https://raw.githubusercontent.com/floegence/floret/main/okf/index.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/floegence/floret/main/okf/index.md",
  "note": "`okf_version: \"0.1\"` at `okf/index.md` (`text/plain`, HTTP 200) on main."
 },
 {
  "id": "raycast-cimd",
  "org_id": "raycast",
  "name": "Raycast",
  "url": "https://www.raycast.com",
  "type": "harness",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Raycast",
    "role": "OAuth client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `client_name` Raycast; `token_endpoint_auth_method` `none`.",
    "full_detail_md": "`https://www.raycast.com/.well-known/oauth-client-metadata/raycast.json` returned HTTP 200 `application/json`, with `client_id` equal to that URL, `client_name` Raycast, and `token_endpoint_auth_method` `none`. `redirect_uris` include Raycast custom schemes `com.raycast:/oauth` and `raycast://mcp-oauth-callback`, plus `http://127.0.0.1/callback`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "Published client metadata JSON; client_name Raycast; client_id equals the well-known document URL",
     "auth_method_or_pkce": "token_endpoint_auth_method none; grant_types authorization_code and refresh_token; no code_challenge_methods_supported field in this document",
     "uri_or_ssrf_rules": "redirect_uris include com.raycast:/oauth, raycast://mcp-oauth-callback, and http://127.0.0.1/callback; client_id is an https URL on www.raycast.com",
     "draft_or_spec_version": "Live client metadata JSON checked 2026-10-30; the document does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_name": "Raycast",
     "token_endpoint_auth_method": "none"
    },
    "source_url": "https://www.raycast.com/.well-known/oauth-client-metadata/raycast.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.raycast.com/.well-known/oauth-client-metadata/raycast.json",
  "note": "HTTP 200; `client_name` Raycast; `token_endpoint_auth_method` `none`."
 },
 {
  "id": "react-native",
  "org_id": "copilotkit",
  "name": "React Native",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "React Native",
    "role": "Mobile client",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists React Native as Supported, with an Example, and marks it 1st Party.",
    "full_detail_md": "The AG-UI overview lists React Native as Supported, with an Example, and marks it 1st Party. That directory row does not name a transport, event model, or package.",
    "facets": {
     "transport": "Not stated on the directory row",
     "event_or_state_model": "Not stated on the directory row",
     "integration_role": "1st-party mobile client",
     "sdk_or_package": "Not named; Example link only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "Overview lists React Native as Supported, with an Example, and marks it 1st Party."
 },
 {
  "id": "readthedocs",
  "org_id": "readthedocs",
  "name": "Read the Docs",
  "url": "https://docs.readthedocs.com/platform/stable/",
  "type": "origin",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Read the Docs",
    "role": "Docs platform & host",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "Enabled automatically across hosted docs; live `Accept: text/markdown` probe returns `text/markdown; charset=utf-8` (`vary: Accept-Encoding, accept`).",
    "full_detail_md": "Enabled automatically on all documentation domains hosted on Read the Docs via Cloudflare, with no configuration required. Documentation shows `Accept: text/markdown` against `https://docs.readthedocs.com/platform/stable/` returning `HTTP/2 200`, `content-type: text/markdown; charset=utf-8`, `vary: accept`, `x-markdown-tokens: 1496`, and `content-signal: ai-train=yes, search=yes, ai-input=yes` (Cloudflare's 2026-10-09 changelog notes converted responses no longer generate `x-markdown-tokens` or `x-original-tokens`). Live probe on 2026-11-03 returned `HTTP/2 200` with `content-type: text/markdown; charset=utf-8`, `vary: Accept-Encoding, accept`, `content-signal: ai-train=yes, search=yes, ai-input=yes`, and `server: cloudflare`.",
    "facets": {
     "negotiation_or_artifact": "Automatic Markdown negotiation on Read the Docs documentation domains via Cloudflare, verified by live Accept probe of https://docs.readthedocs.com/platform/stable/",
     "response_headers": "HTTP/2 200; content-type: text/markdown; charset=utf-8; vary: Accept-Encoding, accept; content-signal: ai-train=yes, search=yes, ai-input=yes; server: cloudflare",
     "content_type_or_tokens": "text/markdown; charset=utf-8 (docs example prints x-markdown-tokens: 1496; 2026-10-09 Cloudflare changelog notes token headers are no longer generated)",
     "verification_posture": "Live HTTP probe checked 2026-11-03 plus Read the Docs platform documentation and 2026-10-09 Cloudflare changelog"
    },
    "telemetry": {
     "artifact_kind": "negotiated_markdown",
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "content_signal": "ai-train=yes, search=yes, ai-input=yes",
     "vary": "Accept-Encoding, accept",
     "server": "cloudflare",
     "marker": "content-type: text/markdown; charset=utf-8"
    },
    "source_url": "https://docs.readthedocs.com/platform/latest/reference/markdown-for-agents.html"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://docs.readthedocs.com/platform/latest/reference/markdown-for-agents.html",
  "note": "Enabled automatically across hosted docs; live `Accept: text/markdown` probe returns `text/markdown; charset=utf-8` (`vary: Accept-Encoding, accept`)."
 },
 {
  "id": "redhat-openshift-ztwim",
  "org_id": "redhat",
  "name": "Zero Trust Workload Identity Manager",
  "url": "https://www.redhat.com/en/blog/zero-trust-workload-identity-manager-generally-available-red-hat-openshift",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Red Hat OpenShift Zero Trust Workload Identity Manager",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-23",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-23",
    "col4_md": "Generally available on OpenShift, based on upstream SPIRE, the SPIFFE reference implementation.",
    "full_detail_md": "On January 23, 2026, Red Hat announced the general availability of zero trust workload identity manager on Red Hat OpenShift. Zero trust workload identity manager is based on the upstream SPIRE project, the reference implementation of the SPIFFE standard for workload identity.",
    "facets": {
     "svid_or_bundle_format": "SVIDs from upstream SPIRE. The announcement does not split X.509-SVID from JWT-SVID.",
     "api_or_federation_surface": "Zero Trust Workload Identity Manager on Red Hat OpenShift, generally available January 23, 2026.",
     "attestation_or_trust_domain": "Based on upstream SPIRE, which Red Hat calls the reference implementation of the SPIFFE standard for workload identity.",
     "verification_posture": "Red Hat general-availability announcement dated January 23, 2026."
    },
    "telemetry": null,
    "source_url": "https://www.redhat.com/en/blog/zero-trust-workload-identity-manager-generally-available-red-hat-openshift"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.redhat.com/en/blog/zero-trust-workload-identity-manager-generally-available-red-hat-openshift",
  "note": "Generally available on OpenShift, based on upstream SPIRE, the SPIFFE reference implementation."
 },
 {
  "id": "redocly",
  "org_id": "redocly",
  "name": "Redocly",
  "url": "https://redocly.com/.well-known/agent-card.json",
  "type": "agent",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Redocly",
    "role": "Public A2A agent",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Live Agent Card advertising `protocolVersion` `0.3.0` (`preferredTransport` `HTTP+JSON`) at `https://redocly.com/a2a` and MCP extension `https://redocly.com/mcp`.",
    "full_detail_md": "Redocly serves a live HTTP 200 Agent Card at https://redocly.com/.well-known/agent-card.json (v`0.0.1`, checked 2026-10-30) using pre-v1.0 schema fields (`protocolVersion` `0.3.0` and `preferredTransport` `HTTP+JSON` at `https://redocly.com/a2a`, `streaming`: `false`, `pushNotifications`: `false`), exposing seven documentation and linting skills (`recheck-config`, `recheck-lint`, `redocly`, `redocly-api-docs`, `redocly-authoring`, `redocly-cli`, and `redocly-lint-rules`) and an extension linking its Model Context Protocol server at `https://redocly.com/mcp`.",
    "facets": {
     "transport_bindings": "HTTP+JSON at https://redocly.com/a2a (pre-v1.0 preferredTransport field; streaming: false)",
     "discovery_artifact": "GET https://redocly.com/.well-known/agent-card.json (v0.0.1, A2A 0.3.0 card schema)",
     "protocol_version": "0.3.0",
     "auth_schemes": "None declared in public Agent Card",
     "verification_posture": "Live HTTP 200 Agent Card probe (checked 2026-10-30)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "protocol_version": "0.3.0",
     "agent_version": "0.0.1"
    },
    "source_url": "https://redocly.com/.well-known/agent-card.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://redocly.com/.well-known/agent-card.json",
  "note": "Live Agent Card advertising `protocolVersion` `0.3.0` (`preferredTransport` `HTTP+JSON`) at `https://redocly.com/a2a` and MCP extension `https://redocly.com/mcp`."
 },
 {
  "id": "registry-agent-example",
  "org_id": "iab-tech-lab",
  "name": "Registry Agent example",
  "url": "https://github.com/IABTechLab/registry-agent-example",
  "type": "sdk",
  "implements": [
   "aamp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "aamp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Registry Agent example",
    "role": "Registry client",
    "status": "Development",
    "status_display": "Development · checked 2026-10-31",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "The hub README says the Registry Agent example demonstrates agent discovery, registration, and coordination patterns. The README describes an ADK TypeScript agent for the Tech Lab agent registry MCP server. It reads `REGISTRY_MCP_TOKEN` as a bearer token. The web interface is development only, not for production.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/IABTechLab/registry-agent-example/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/IABTechLab/registry-agent-example/main/README.md",
  "note": "The hub README says the Registry Agent example demonstrates agent discovery, registration, and coordination patterns. The README describes an ADK TypeScript agent for the Tech Lab agent registry MCP server. It reads `REGISTRY_MCP_TOKEN` as a bearer token. The web interface is development only, not for production."
 },
 {
  "id": "render",
  "org_id": "render",
  "name": "Render",
  "url": "https://render.com/robots.txt",
  "type": "origin",
  "implements": [
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Render",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "`https://render.com/robots.txt` returned status 200 on 2026-10-29 with `Content-Signal: ai-train=yes, search=yes, ai-input=yes` in the group for all user agents and again in a group that names AI crawlers.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://render.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://render.com/robots.txt",
  "note": "`https://render.com/robots.txt` returned status 200 on 2026-10-29 with `Content-Signal: ai-train=yes, search=yes, ai-input=yes` in the group for all user agents and again in a group that names AI crawlers."
 },
 {
  "id": "replicate-com",
  "org_id": "replicate",
  "name": "Replicate",
  "url": "https://replicate.com/",
  "type": "origin",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Replicate",
    "role": "Product site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`HTTP/2 200` `text/markdown; charset=utf-8` with `vary: Accept-Encoding, accept` via `server: cloudflare`.",
    "full_detail_md": "Fetched with Markdown content negotiation on 2026-11-03, Replicate returned `HTTP/2 200` with `content-type: text/markdown; charset=utf-8`, `server: cloudflare`, `vary: Accept-Encoding, accept`, and `content-signal: ai-train=yes, search=yes, ai-input=yes`. The page describes running open-source machine learning models with a cloud API.",
    "facets": {
     "negotiation_or_artifact": "Live Accept negotiation of https://replicate.com/",
     "response_headers": "HTTP/2 200; server: cloudflare; vary: Accept-Encoding, accept; content-signal ai-train=yes, search=yes, ai-input=yes",
     "content_type_or_tokens": "text/markdown; charset=utf-8",
     "verification_posture": "Live HTTP probe checked 2026-11-03 (response date Tue, 03 Nov 2026 21:03:57 GMT)"
    },
    "telemetry": {
     "artifact_kind": "negotiated_markdown",
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "content_signal": "ai-train=yes, search=yes, ai-input=yes",
     "vary": "Accept-Encoding, accept",
     "server": "cloudflare",
     "marker": "content-type: text/markdown; charset=utf-8"
    },
    "source_url": "https://replicate.com/"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://replicate.com/",
  "note": "`HTTP/2 200` `text/markdown; charset=utf-8` with `vary: Accept-Encoding, accept` via `server: cloudflare`."
 },
 {
  "id": "republik",
  "org_id": "republik",
  "name": "Republik",
  "url": "https://www.republik.ch/ai.txt",
  "type": "origin",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Republik",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, `Disallow: /`, `Disallow: *`).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.republik.ch/ai.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.republik.ch/ai.txt",
  "note": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, `Disallow: /`, `Disallow: *`)."
 },
 {
  "id": "resend",
  "org_id": "resend",
  "name": "Resend",
  "url": "https://resend.com/.well-known/ai-catalog.json",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Resend",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-26",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-26",
    "col4_md": "Catalog announced 2026-10-26 and served with `Content-Type: application/ai-catalog+json`. Entry `urn:air:resend.com:mcp:mcp` points at `https://mcp.resend.com/mcp/server-card`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://resend.com/.well-known/ai-catalog.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://resend.com/.well-known/ai-catalog.json",
  "note": "Catalog announced 2026-10-26 and served with `Content-Type: application/ai-catalog+json`. Entry `urn:air:resend.com:mcp:mcp` points at `https://mcp.resend.com/mcp/server-card`."
 },
 {
  "id": "rnwy",
  "org_id": "ai-rights-institute",
  "name": "RNWY",
  "url": "https://rnwy.com/skill.md",
  "type": "authority",
  "implements": [
   "erc-8004"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "RNWY",
    "role": "Verifier SDK / Runtime",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Skill `7.5.0` posts to `https://rnwy.com/api/mcp` and covers ERC-8004.",
    "full_detail_md": "RNWY skill.md version 7.5.0 documents an MCP endpoint at POST https://rnwy.com/api/mcp, covers the ERC-8004, Olas, Virtuals, and SATI registries across 11 EVM chains plus Solana, and uses reviewer_analysis to check each reviewer's wallet age and funding source.",
    "facets": {
     "registry_or_contract": "Covers ERC-8004, Olas, Virtuals, and SATI registries",
     "chains_or_networks": "11 EVM chains plus Solana",
     "standards_profile": "Trust scoring with reviewer_analysis of reviewer wallet age and funding source",
     "sdk_or_deployment": "skill.md version 7.5.0; MCP POST https://rnwy.com/api/mcp"
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "skill_md"
    },
    "source_url": "https://rnwy.com/skill.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://rnwy.com/skill.md",
  "note": "Skill `7.5.0` posts to `https://rnwy.com/api/mcp` and covers ERC-8004."
 },
 {
  "id": "rslstandard-robots",
  "org_id": "rsl-collective",
  "name": "RSL Standard (rslstandard.org)",
  "url": "https://rslstandard.org/robots.txt",
  "type": "origin",
  "implements": [
   "rsl"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "rsl",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "RSL Standard (rslstandard.org)",
    "role": "Specification site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Publishes `License: https://internetcollective.org/license.xml` above `User-agent: *`.",
    "full_detail_md": "The robots.txt response is HTTP 200 with Content-Type text/plain; charset=utf-8, and a comment says AI training without the RSL standard royalty license is prohibited. The next line is License: https://internetcollective.org/license.xml, followed by User-agent: * and an empty Disallow, and the file does not name RSL-SPEC-1.0 or the 2025-12-10 publication date.",
    "facets": {
     "discovery_surface": "https://rslstandard.org/robots.txt (text/plain; charset=utf-8, HTTP 200)",
     "xml_or_license_directive": "License: https://internetcollective.org/license.xml",
     "usage_or_payment_terms": "Comment prohibits AI training without the RSL standard royalty license; the license XML is not in this robots.txt body",
     "spec_version": "Directive does not name RSL 1.0 or RSL-SPEC-1.0; those labels belong to the separate specification page"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "has_rsl_license_directive": true,
     "license_url": "https://internetcollective.org/license.xml"
    },
    "source_url": "https://rslstandard.org/robots.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://rslstandard.org/robots.txt",
  "note": "Publishes `License: https://internetcollective.org/license.xml` above `User-agent: *`."
 },
 {
  "id": "salesforce",
  "org_id": "salesforce",
  "name": "Salesforce",
  "url": "https://www.salesforce.com/news/press-releases/2025/10/14/stripe-openai-agentic-commerce-protocol-announcement/?bc=OTH",
  "type": "venue",
  "implements": [
   "agentic-commerce-protocol"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Salesforce (Agentforce Commerce)",
    "role": "Commerce platform",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-14",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-14",
    "col4_md": "Collaborated with Stripe and OpenAI to build an Instant Checkout integration guided by ACP (announced October 14, 2025).",
    "full_detail_md": "Salesforce announced on October 14, 2025 a collaboration with Stripe and OpenAI to build an Instant Checkout integration guided by the Agentic Commerce Protocol (ACP).",
    "facets": {
     "commerce_role_or_surface": "Enterprise commerce platform integration for Instant Checkout",
     "payment_or_token_rail": "Stripe and OpenAI ACP checkout integration",
     "api_or_spec_version": "Agentic Commerce Protocol (ACP)",
     "availability_or_eligibility_posture": "Announced October 14, 2025"
    },
    "telemetry": null,
    "source_url": "https://www.salesforce.com/news/press-releases/2025/10/14/stripe-openai-agentic-commerce-protocol-announcement/?bc=OTH"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.salesforce.com/news/press-releases/2025/10/14/stripe-openai-agentic-commerce-protocol-announcement/?bc=OTH",
  "note": "Collaborated with Stripe and OpenAI to build an Instant Checkout integration guided by ACP (announced October 14, 2025)."
 },
 {
  "id": "salesforce-mulesoft-agent-fabric",
  "org_id": "salesforce-mulesoft-agent-fabric",
  "name": "Salesforce MuleSoft Agent Fabric",
  "url": "https://aboutus.godaddy.net/newsroom/news-releases/press-release-details/2026/GoDaddy-ANS-Integrates-with-Salesforces-MuleSoft-Agent-Fabric/default.aspx",
  "type": "authority",
  "implements": [
   "ans"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "ans",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Salesforce MuleSoft Agent Fabric",
    "role": "Explorer / Scanner",
    "status": "Supported",
    "status_display": "Supported · as of 2026-02-19",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02-19",
    "col4_md": "GoDaddy's 2026-02-19 release says MuleSoft Agent Scanners pull verified agents from ANS into the MuleSoft Agent Registry, where they are reviewed and approved before they can reach enterprise systems. The Nov. 10, 2026 Linux Foundation release lists Salesforce among 11 organizations that have contributed to or adopted ANS.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://aboutus.godaddy.net/newsroom/news-releases/press-release-details/2026/GoDaddy-ANS-Integrates-with-Salesforces-MuleSoft-Agent-Fabric/default.aspx"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://aboutus.godaddy.net/newsroom/news-releases/press-release-details/2026/GoDaddy-ANS-Integrates-with-Salesforces-MuleSoft-Agent-Fabric/default.aspx",
  "note": "GoDaddy's 2026-02-19 release says MuleSoft Agent Scanners pull verified agents from ANS into the MuleSoft Agent Registry, where they are reviewed and approved before they can reach enterprise systems. The Nov. 10, 2026 Linux Foundation release lists Salesforce among 11 organizations that have contributed to or adopted ANS."
 },
 {
  "id": "sap-agent-gateway",
  "org_id": "sap",
  "name": "SAP Agent Gateway",
  "url": "https://architecture.learning.sap.com/news/2026/10/27/a2a-agent-gateway-interoperability",
  "type": "origin",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "SAP (Agent Gateway)",
    "role": "Enterprise agent gateway",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-10-27",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-27",
    "col4_md": "October 2026 announcement of inbound A2A gateway combining `AgentCard` URLs with Agentic Resource Discovery (`ARD`).",
    "full_detail_md": "SAP's 27 October 2026 Architecture Center announcement states that the SAP Agent Gateway reached general availability for inbound A2A interoperability, combining tenant-scoped Agentic Resource Discovery (`ARD`) catalogs and `AgentCard` URLs with single-tenant OpenID Connect (`OIDC`) Agent Identity, user-bound token validation, and access control lists (`ACL`s) before routing external A2A requests to SAP Agents (whereas SAP's outbound Joule reference architecture ae6821 updated 2026-10-26 notes that bidirectional third-party Agent Gateway communication is not yet supported).",
    "facets": {
     "transport_bindings": "Inbound A2A request routing through SAP Business AI Platform Agent Gateway",
     "discovery_artifact": "Tenant-scoped Agentic Resource Discovery (ARD) catalog returning AgentCard URLs",
     "protocol_version": "Not specified in announcement (published 2026-10-27)",
     "auth_schemes": "SAP Cloud Identity Services OIDC Agent Identity (client credentials for ARD discovery; user-bound token and ACL check for A2A invocation)",
     "verification_posture": "Vendor GA release announcement (2026-10-27; companion SAP ref-arch ae6821 dated 2026-10-26 notes bidirectional third-party Agent Gateway support is not yet GA)"
    },
    "telemetry": null,
    "source_url": "https://architecture.learning.sap.com/news/2026/10/27/a2a-agent-gateway-interoperability"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://architecture.learning.sap.com/news/2026/10/27/a2a-agent-gateway-interoperability",
  "note": "October 2026 announcement of inbound A2A gateway combining `AgentCard` URLs with Agentic Resource Discovery (`ARD`)."
 },
 {
  "id": "sap-joule",
  "org_id": "sap",
  "name": "SAP Joule",
  "url": "https://architecture.learning.sap.com/docs/ref-arch/ae6821",
  "type": "harness",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "SAP (Joule)",
    "role": "Outbound A2A client",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-26",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-26",
    "col4_md": "Outbound `agent-request` client with webhook push notifications; bidirectional third-party `Agent Gateway` communication not yet GA.",
    "full_detail_md": "SAP's Outbound A2A Reference Architecture (ref-arch ae6821, updated 2026-10-26) documents SAP Joule acting as an A2A client via Dialog Function `agent-request` actions (60-second synchronous timeout, webhook push notifications for asynchronous tasks, and server-generated context and task IDs secured by SAP Cloud Identity Services IAS App2App trust), while noting that bidirectional communication with third-party and self-hosted agents through `Agent Gateway` is not yet supported and some components are not yet generally available.",
    "facets": {
     "transport_bindings": "Outbound HTTP A2A request (60s synchronous timeout) and asynchronous webhook push notifications",
     "discovery_artifact": "Manual endpoint configuration in Joule Scenario Dialog Function (agent-request)",
     "protocol_version": "Not specified in reference architecture (updated 2026-10-26)",
     "auth_schemes": "SAP Cloud Identity Services (IAS) App2App trust relationship",
     "verification_posture": "Vendor reference architecture (updated 2026-10-26; explicitly notes some components are not yet GA)"
    },
    "telemetry": null,
    "source_url": "https://architecture.learning.sap.com/docs/ref-arch/ae6821"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://architecture.learning.sap.com/docs/ref-arch/ae6821",
  "note": "Outbound `agent-request` client with webhook push notifications; bidirectional third-party `Agent Gateway` communication not yet GA."
 },
 {
  "id": "scalekit-cimd",
  "org_id": "scalekit",
  "name": "Scalekit",
  "url": "https://scalekit.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Scalekit",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Enable CIMD so the server fetches MCP-host metadata; keep DCR enabled too.",
    "full_detail_md": "Scalekit's MCP quickstart says to enable Client ID Metadata Document so the authorization server fetches client metadata from MCP hosts and authorizes them. For public MCP clients such as Claude, Cursor, or VS Code, it recommends leaving both DCR and CIMD enabled.",
    "facets": {
     "metadata_flag_or_profile": "Operator enables CIMD so the authorization server fetches client metadata from MCP hosts",
     "auth_method_or_pkce": "Recommends leaving both dynamic client registration and CIMD enabled for public MCP clients",
     "uri_or_ssrf_rules": "The server fetches client metadata from MCP hosts; the quickstart does not state a separate SSRF rule",
     "draft_or_spec_version": "Undated Scalekit quickstart; it does not name a CIMD draft revision"
    },
    "telemetry": null,
    "source_url": "https://docs.scalekit.com/authenticate/mcp/quickstart/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.scalekit.com/authenticate/mcp/quickstart/",
  "note": "Enable CIMD so the server fetches MCP-host metadata; keep DCR enabled too."
 },
 {
  "id": "scoretail-com",
  "org_id": "scoretail",
  "name": "ScoreTail",
  "url": "https://scoretail.com/en/sheet-music/canon-in-d-pachelbel-johann/view",
  "type": "origin",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "ScoreTail",
    "role": "In-page caller",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Calls `registerTools`, which calls `registerTool` on `document.modelContext`.",
    "full_detail_md": "The HTTP 200 page fetched 2026-10-30 calls `registerTools`, and that helper calls `registerTool` on each tool while `getModelContext` returns `document.modelContext`. The page logs `WebMCP: tools registered` and defines `enableOriginTrial`, which looks for a meta origin-trial tag.",
    "facets": {
     "engine_or_runtime": "In-page script on the ScoreTail score view",
     "api_surface_or_flag": "registerTools helper calling registerTool; getModelContext returns document.modelContext",
     "position_or_status": "Live HTTP 200 (fetched 2026-10-30); script also defines enableOriginTrial",
     "package_or_version": "No package version; looks for a meta http-equiv origin-trial tag"
    },
    "telemetry": {
     "http_status": 200,
     "observed_member": "registerTools",
     "inner_call": "registerTool",
     "model_context": "document.modelContext",
     "spec_member": "document.modelContext.registerTool"
    },
    "source_url": "https://scoretail.com/en/sheet-music/canon-in-d-pachelbel-johann/view"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://scoretail.com/en/sheet-music/canon-in-d-pachelbel-johann/view",
  "note": "Calls `registerTools`, which calls `registerTool` on `document.modelContext`."
 },
 {
  "id": "seller-agent",
  "org_id": "iab-tech-lab",
  "name": "IAB Tech Lab Seller Agent",
  "url": "https://github.com/IABTechLab/seller-agent",
  "type": "sdk",
  "implements": [
   "aamp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "aamp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "IAB Tech Lab Seller Agent",
    "role": "Reference seller runtime",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-31",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "The standards page says IAB Tech Lab included an open-source reference implementation for Ad Seller Systems, and that companies can download the Seller Agent SDK. The Seller Agent README marks the repo `V2 - Feature Complete`. It is an inventory system for publishers and SSPs using OpenDirect 2.1, Deals API v1.0, and sellers.json, with `46 MCP tools`. It distributes deals through PubMatic (MCP), Index Exchange (REST), and Magnite (REST), and connects to GAM, FreeWheel, and CSV for demo and testing.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/IABTechLab/seller-agent/main/README.md"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/IABTechLab/seller-agent/main/README.md",
  "note": "The standards page says IAB Tech Lab included an open-source reference implementation for Ad Seller Systems, and that companies can download the Seller Agent SDK. The Seller Agent README marks the repo `V2 - Feature Complete`. It is an inventory system for publishers and SSPs using OpenDirect 2.1, Deals API v1.0, and sellers.json, with `46 MCP tools`. It distributes deals through PubMatic (MCP), I"
 },
 {
  "id": "sentry-as-cimd",
  "org_id": "sentry",
  "name": "Sentry MCP authorization server",
  "url": "https://mcp.sentry.dev",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Sentry",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `client_id_metadata_document_supported` true; PKCE `S256`.",
    "full_detail_md": "`https://mcp.sentry.dev/.well-known/oauth-authorization-server` returned HTTP 200 `application/json`, with `issuer` `https://mcp.sentry.dev` and `client_id_metadata_document_supported` true. Endpoints `authorization_endpoint`, `token_endpoint`, and `registration_endpoint` are under `/oauth/` on that host, `grant_types_supported` are `authorization_code` and `refresh_token`, and `code_challenge_methods_supported` is `S256`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "client_id_metadata_document_supported true; issuer https://mcp.sentry.dev matches the metadata host",
     "auth_method_or_pkce": "code_challenge_methods_supported S256; grant_types_supported authorization_code and refresh_token",
     "uri_or_ssrf_rules": "authorization, token, and registration endpoints are on https://mcp.sentry.dev/oauth/; this row is the server metadata document, not a client_id fetch",
     "draft_or_spec_version": "Live authorization-server metadata checked 2026-10-30; the JSON does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_id_metadata_document_supported": true,
     "issuer": "https://mcp.sentry.dev"
    },
    "source_url": "https://mcp.sentry.dev/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mcp.sentry.dev/.well-known/oauth-authorization-server",
  "note": "HTTP 200; `client_id_metadata_document_supported` true; PKCE `S256`."
 },
 {
  "id": "sequentum-checkout-agent",
  "org_id": "sequentum-checkout-agent",
  "name": "Sequentum Checkout Agent",
  "url": "https://www.sequentum.com/news/sequentum-launches-checkout-agent-with-skyfire-integration-for-secure-compliant-agentic-commerce",
  "type": "agent",
  "implements": [
   "kyapay-token"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Sequentum Checkout Agent",
    "role": "Buying agent",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Browser-automation checkout agent delivering signed Skyfire KYA/payment tokens in the `skyfire-pay-id` HTTP header on every merchant request inside a SOC 2 Type 2 environment",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.sequentum.com/news/sequentum-launches-checkout-agent-with-skyfire-integration-for-secure-compliant-agentic-commerce"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.sequentum.com/news/sequentum-launches-checkout-agent-with-skyfire-integration-for-secure-compliant-agentic-commerce",
  "note": "Browser-automation checkout agent delivering signed Skyfire KYA/payment tokens in the `skyfire-pay-id` HTTP header on every merchant request inside a SOC 2 Type 2 environment"
 },
 {
  "id": "server-llm-txt",
  "org_id": "community",
  "name": "server-llm-txt",
  "url": "https://llmstxt.org",
  "type": "sdk",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "server-llm-txt",
    "role": "MCP server / harness",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-08-10",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-10",
    "col4_md": "Listed integration on `llmstxt.org` exposing `llms.txt` over MCP; implementation behavior not independently verified.",
    "full_detail_md": "Listed integration on `llmstxt.org` as an MCP server allowing LLMs to search and fetch `llms.txt` files across MCP hosts; implementation behavior is not independently verified.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "Linked Markdown documentation pages",
     "content_type_or_bytes": "Markdown fetched and searched via MCP tools",
     "generator_or_consumer_mode": "Listed integration on `llmstxt.org` (`server-llm-txt` MCP server; implementation behavior not independently verified)"
    },
    "telemetry": null,
    "source_url": "https://llmstxt.org"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://llmstxt.org",
  "note": "Listed integration on `llmstxt.org` exposing `llms.txt` over MCP; implementation behavior not independently verified."
 },
 {
  "id": "shopify",
  "org_id": "shopify",
  "name": "Shopify",
  "url": "https://www.shopify.com",
  "type": "venue",
  "implements": [
   "agentic-commerce-protocol",
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Shopify",
    "role": "Platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-24",
    "col4_md": "Instant Checkout for Shopify merchants (rolling out from November 20, 2025); on March 24, 2026 OpenAI shifted to merchant checkout experiences while focusing on product discovery, and Shopify states buyers finish in-app on mobile or in a separate browser tab on desktop while merchants stay merchant of record.",
    "full_detail_md": "Shopify announced on September 29, 2025 that Shopify merchants will be able to sell directly through ChatGPT conversations. OpenAI's November 20, 2025 release notes say Instant Checkout was rolling out to Shopify merchants, starting with Spanx, Skims, and Glossier. On March 24, 2026, OpenAI announced that the initial version of Instant Checkout did not offer the level of flexibility it aspired to provide, so it was allowing merchants to use their own checkout experiences while focusing its efforts on product discovery; Shopify's March 24, 2026 post says buyers complete purchases via an in-app browser (while on desktop ChatGPT links out directly to the merchant's store in a separate browser tab) and that merchants remain the merchant of record.",
    "facets": {
     "commerce_role_or_surface": "Shopify merchant catalog sold through ChatGPT",
     "payment_or_token_rail": "In-app browser checkout (mobile) or separate browser tab (desktop); merchant remains merchant of record",
     "api_or_spec_version": "Agentic Commerce Protocol Instant Checkout (2025) and merchant checkout via Agentic Storefronts (March 24, 2026)",
     "availability_or_eligibility_posture": "Announced September 29, 2025; Instant Checkout rolling out from November 20, 2025; March 24, 2026 transition to merchant checkout experiences"
    },
    "telemetry": null,
    "source_url": "https://www.shopify.com/news/shopify-open-ai-commerce"
   },
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Shopify",
    "role": "Platform (Co-author)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-24",
    "col4_md": "Select brands sell in AI Mode and Gemini on co-developed UCP.",
    "full_detail_md": "On 2026-03-24 Shopify said select brands have started selling in AI Mode in Google Search and the Gemini app, powered by the Universal Commerce Protocol, the open standard Shopify co-developed with Google. The engineering post says UCP was co-developed with Google and is supported by Etsy, Target, Walmart, Wayfair, and millions of Shopify merchants.",
    "facets": {
     "commerce_surface": "Shopify platform selling in AI Mode in Google Search and the Gemini app",
     "payment_handlers_or_rail": "UCP checkout co-developed with Google; engineering post names Etsy, Target, Walmart, Wayfair, and Shopify merchants",
     "transport_bindings": "Platform announcement, not a single probed merchant /.well-known/ucp host",
     "spec_version": "Open standard co-developed with Google; news post datePublished 2026-03-24 (article date, not a ucp.version pin)"
    },
    "telemetry": null,
    "source_url": "https://www.shopify.com/news/agentic-commerce-momentum"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.shopify.com/news/shopify-open-ai-commerce",
  "note": "Instant Checkout for Shopify merchants (rolling out from November 20, 2025); on March 24, 2026 OpenAI shifted to merchant checkout experiences while focusing on product discovery, and Shopify states buyers finish in-app on mobile or in a separate browser tab on desktop while merchants stay merchant of record."
 },
 {
  "id": "shopify-cloudsurf",
  "org_id": "shopify",
  "name": "Cloudsurf",
  "url": "https://cloudsurf.shopify.io",
  "type": "origin",
  "implements": [
   "http-message-signatures",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Shopify (Cloudsurf)",
    "role": "Bot / Agent signer",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Publishes `Ed25519` JWK (header `keyid` only) and directory-response signature headers; signature validation not established by HTTP observation.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` at Cloudsurf's key directory, publishing one `Ed25519` JWK (whose JWK object omits a key ID while `signature-input` sets `keyid=\"ytpCrk8u74NJ08SQepVrOmovFBEXUZPq7Nv8FCg_Qdw\"`) and directory-response signature headers (`tag=\"http-message-signatures-directory\"`); cryptographic signature validation is not established by the recorded HTTP observation.",
    "facets": {
     "signature_or_key_format": "Publishes 1 OKP Ed25519 JWK (JWK object omits key ID; header sets `keyid`) and directory-response signature headers; signature validation not established by the recorded HTTP observation",
     "directory_or_header": "HTTP 200 `application/http-message-signatures-directory+json`",
     "signing_algorithm": "Ed25519 (`alg=\"ed25519\"`, `tag=\"http-message-signatures-directory\"`)",
     "verification_role": "Bot / Agent signer (partial; JWK object omits key ID)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 1,
     "kid_present": false,
     "keyid": "ytpCrk8u74NJ08SQepVrOmovFBEXUZPq7Nv8FCg_Qdw",
     "alg": "ed25519"
    },
    "source_url": "https://cloudsurf.shopify.io/.well-known/http-message-signatures-directory"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Shopify (Cloudsurf)",
    "role": "Bot / Agent signer (Web Bot Auth profile)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Web Bot Auth profile: publishes `Ed25519` JWK (omitting JWK key ID) and `alg=\"ed25519\"` directory-response signature headers.",
    "full_detail_md": "Serves HTTP 200 `application/http-message-signatures-directory+json` at the Cloudsurf key directory endpoint, publishing one `OKP` `Ed25519` JWK (whose JWK object omits a key ID property while `signature-input` sets `keyid=\"ytpCrk8u74NJ08SQepVrOmovFBEXUZPq7Nv8FCg_Qdw\"`, `alg=\"ed25519\"`, `tag=\"http-message-signatures-directory\"`); cryptographic signature validation is not established by the recorded HTTP observation.",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth profile of RFC 9421 (`tag=\"http-message-signatures-directory\"`)",
     "signature_fields": "HTTP 200 `application/http-message-signatures-directory+json` (`keyid` in `signature-input`; JWK object omits key ID)",
     "algorithms_or_keys": "Publishes 1 `OKP` `Ed25519` JWK (`alg=\"ed25519\"`) and directory-response signature headers",
     "verification_posture": "Bot / Agent signer (partial; JWK omits key ID and signature validation is not established by HTTP observation)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/http-message-signatures-directory+json",
     "kty": "OKP",
     "crv": "Ed25519",
     "directory_response_signed": true,
     "tag": "http-message-signatures-directory",
     "key_count": 1,
     "kid_present": false,
     "keyid": "ytpCrk8u74NJ08SQepVrOmovFBEXUZPq7Nv8FCg_Qdw",
     "alg": "ed25519"
    },
    "source_url": "https://cloudsurf.shopify.io/.well-known/http-message-signatures-directory"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://cloudsurf.shopify.io/.well-known/http-message-signatures-directory",
  "note": "Publishes `Ed25519` JWK (header `keyid` only) and directory-response signature headers; signature validation not established by HTTP observation."
 },
 {
  "id": "singlefax",
  "org_id": "monocube",
  "name": "SingleFax",
  "url": "https://singlefax.com",
  "type": "venue",
  "implements": [
   "ap2"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ap2",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "SingleFax (Monocube LLC)",
    "role": "Merchant",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Monocube LLC publishes the SingleFax agent card with a required AP2 extension at `https://github.com/google-agentic-commerce/AP2/tree/v0.1.0`, role `merchant`, version `0.1.0`, checkout mode `human_present`, and payment method `stripe_shared_payment_token`. singlefax.com/ap2.md says SingleFax implements the human-present merchant flow of AP2 v0.1.0 and accepts Stripe Shared Payment Tokens (SPTs). The cart request carries an unsigned `IntentMandate`; the response includes `ap2.mandates.CartMandate`; prepare sends `ap2.mandates.PaymentMandate`. AP2 v0.2 and purchases without the user present are not negotiated.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8"
    },
    "source_url": "https://singlefax.com/.well-known/agent-card.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://singlefax.com/.well-known/agent-card.json",
  "note": "Monocube LLC publishes the SingleFax agent card with a required AP2 extension at `https://github.com/google-agentic-commerce/AP2/tree/v0.1.0`, role `merchant`, version `0.1.0`, checkout mode `human_present`, and payment method `stripe_shared_payment_token`. singlefax.com/ap2.md says SingleFax implements the human-present merchant flow of AP2 v0.1.0 and accepts Stripe Shared Payment Tokens (SPTs). "
 },
 {
  "id": "skill-a2a-middleware",
  "org_id": "copilotkit",
  "name": "A2A Middleware",
  "url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "A2A Middleware",
    "role": "Archived AG-UI adapter binding",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-06-03",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-03",
    "col4_md": "Archived Jun 3, 2026 skill `1.0.0` (Python + TS): `A2AMiddlewareAgent` from `@ag-ui/a2a-middleware`; adapter Per-agent (mixed frameworks); port 9000-9002.",
    "full_detail_md": "From the CopilotKit integrations skill archived Jun 3, 2026: A2A Middleware (Python + TS) uses `A2AMiddlewareAgent` from `@ag-ui/a2a-middleware` as the AG-UI client and Per-agent (mixed frameworks) as the server adapter, with agent port 9000-9002.",
    "facets": {
     "transport": "Agent port 9000-9002",
     "event_or_state_model": "AG-UI client class in the CopilotKit route",
     "integration_role": "A2A Middleware",
     "sdk_or_package": "Per-agent (mixed frameworks)"
    },
    "telemetry": null,
    "source_url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "note": "Archived Jun 3, 2026 skill `1.0.0` (Python + TS): `A2AMiddlewareAgent` from `@ag-ui/a2a-middleware`; adapter Per-agent (mixed frameworks); port 9000-9002."
 },
 {
  "id": "skill-langgraph-js",
  "org_id": "copilotkit",
  "name": "LangGraph (JS)",
  "url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LangGraph (JS)",
    "role": "Archived AG-UI adapter binding",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-06-03",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-03",
    "col4_md": "Archived Jun 3, 2026 skill `1.0.0` (TypeScript): `LangGraphAgent` from `@copilotkit/runtime/langgraph`; adapter Built into `@copilotkit/sdk-js/langgraph`; port 8123.",
    "full_detail_md": "From the CopilotKit integrations skill archived Jun 3, 2026: LangGraph (JS) (TypeScript) uses `LangGraphAgent` from `@copilotkit/runtime/langgraph` as the AG-UI client and Built into `@copilotkit/sdk-js/langgraph` as the server adapter, with agent port 8123.",
    "facets": {
     "transport": "Agent port 8123",
     "event_or_state_model": "AG-UI client class in the CopilotKit route",
     "integration_role": "LangGraph (JS)",
     "sdk_or_package": "Built into `@copilotkit/sdk-js/langgraph`"
    },
    "telemetry": null,
    "source_url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "note": "Archived Jun 3, 2026 skill `1.0.0` (TypeScript): `LangGraphAgent` from `@copilotkit/runtime/langgraph`; adapter Built into `@copilotkit/sdk-js/langgraph`; port 8123."
 },
 {
  "id": "skill-langgraph-python-langgraph-platform",
  "org_id": "copilotkit",
  "name": "LangGraph (Python, LangGraph Platform)",
  "url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "LangGraph (Python, LangGraph Platform)",
    "role": "Archived AG-UI adapter binding",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-06-03",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-03",
    "col4_md": "Archived Jun 3, 2026 skill `1.0.0` (Python): `LangGraphAgent` from `@copilotkit/runtime/langgraph`; adapter LangGraph Platform (managed); port varies.",
    "full_detail_md": "From the CopilotKit integrations skill archived Jun 3, 2026: LangGraph (Python, LangGraph Platform) (Python) uses `LangGraphAgent` from `@copilotkit/runtime/langgraph` as the AG-UI client and LangGraph Platform (managed) as the server adapter, with agent port varies.",
    "facets": {
     "transport": "Agent port varies",
     "event_or_state_model": "AG-UI client class in the CopilotKit route",
     "integration_role": "LangGraph (Python, LangGraph Platform)",
     "sdk_or_package": "LangGraph Platform (managed)"
    },
    "telemetry": null,
    "source_url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "note": "Archived Jun 3, 2026 skill `1.0.0` (Python): `LangGraphAgent` from `@copilotkit/runtime/langgraph`; adapter LangGraph Platform (managed); port varies."
 },
 {
  "id": "skill-mcp-apps",
  "org_id": "copilotkit",
  "name": "MCP Apps",
  "url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "MCP Apps",
    "role": "Archived AG-UI adapter binding",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-06-03",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-06-03",
    "col4_md": "Archived Jun 3, 2026 skill `1.0.0` (TypeScript): `BuiltInAgent` with `MCPAppsMiddleware`; adapter N/A (middleware on BuiltInAgent); port 3108.",
    "full_detail_md": "From the CopilotKit integrations skill archived Jun 3, 2026: MCP Apps (TypeScript) uses `BuiltInAgent` with `MCPAppsMiddleware` as the AG-UI client and N/A (middleware on BuiltInAgent) as the server adapter, with agent port 3108.",
    "facets": {
     "transport": "Agent port 3108",
     "event_or_state_model": "AG-UI client class in the CopilotKit route",
     "integration_role": "MCP Apps",
     "sdk_or_package": "N/A (middleware on BuiltInAgent)"
    },
    "telemetry": null,
    "source_url": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://github.com/copilotkit/skills/blob/HEAD/skills/copilotkit-integrations/SKILL.md",
  "note": "Archived Jun 3, 2026 skill `1.0.0` (TypeScript): `BuiltInAgent` with `MCPAppsMiddleware`; adapter N/A (middleware on BuiltInAgent); port 3108."
 },
 {
  "id": "skyfire",
  "org_id": "skyfire",
  "name": "Skyfire",
  "url": "https://app.skyfire.xyz/.well-known/jwks.json",
  "type": "authority",
  "implements": [
   "kyapay-token"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Skyfire",
    "role": "Token issuer & settler (Originator)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "ES256-signed JWTs (kya+jwt, pay+jwt, kya-pay+jwt; live JWK kid: \"BEDD-0\" at `app.skyfire.xyz/.well-known/jwks.json`) settling in usdc or card tokens (visa_vic, mastercard_scof; up to 51h settlement)",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://app.skyfire.xyz/.well-known/jwks.json"
   },
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Skyfire (`skyfire-xyz/kyapay_a2a`)",
    "role": "Protocol extension (Originator)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "A2A protocol extension enabling client agents to pay merchant agents automatically with KYAPay tokens",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/skyfire-xyz/kyapay_a2a/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://app.skyfire.xyz/.well-known/jwks.json",
  "note": "ES256-signed JWTs (kya+jwt, pay+jwt, kya-pay+jwt; live JWK kid: \"BEDD-0\" at `app.skyfire.xyz/.well-known/jwks.json`) settling in usdc or card tokens (visa_vic, mastercard_scof; up to 51h settlement)"
 },
 {
  "id": "skyfire-mcp-server-create-token-api",
  "org_id": "skyfire-mcp-server-create-token-api",
  "name": "Skyfire MCP Server & Create Token API",
  "url": "https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server",
  "type": "authority",
  "implements": [
   "kyapay-token"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "kyapay-token",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Skyfire MCP Server & Create Token API",
    "role": "Issuer client MCP server (Originator)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Buyer-agent MCP server & token provisioning API minting scoped kya+jwt, pay+jwt, and kya-pay+jwt tokens for transmission in the kyapay-token header",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.skyfire.xyz/docs/using-the-skyfire-mcp-server",
  "note": "Buyer-agent MCP server & token provisioning API minting scoped kya+jwt, pay+jwt, and kya-pay+jwt tokens for transmission in the kyapay-token header"
 },
 {
  "id": "snowflake",
  "org_id": "snowflake",
  "name": "Snowflake",
  "url": "https://docs.snowflake.com/en/sql-reference/stored-procedures/system_create_semantic_view_from_ossie_yaml",
  "type": "origin",
  "implements": [
   "osi"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "osi",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Snowflake",
    "role": "BI / Query engine",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Stored procedure `SYSTEM$CREATE_SEMANTIC_VIEW_FROM_OSSIE_YAML` creates a semantic view from Apache Ossie YAML. Snowflake labels the procedure Preview Feature, Open, available to all accounts. Docs returned status 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.snowflake.com/en/sql-reference/stored-procedures/system_create_semantic_view_from_ossie_yaml"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.snowflake.com/en/sql-reference/stored-procedures/system_create_semantic_view_from_ossie_yaml",
  "note": "Stored procedure `SYSTEM$CREATE_SEMANTIC_VIEW_FROM_OSSIE_YAML` creates a semantic view from Apache Ossie YAML. Snowflake labels the procedure Preview Feature, Open, available to all accounts. Docs returned status 200 on 2026-10-29."
 },
 {
  "id": "solidus-network",
  "org_id": "solidus-network",
  "name": "Solidus Network",
  "url": "https://auth.solidus.network/v1/x401/demo",
  "type": "authority",
  "implements": [
   "x401"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "x401",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Solidus Network",
    "role": "Relying server / Verifier",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Independent verifier. `https://auth.solidus.network/v1/x401/demo` answered on 2026-10-29 with status 200 and a `PROOF-REQUEST` header for `scheme` `x401` and `version` `0.2.0`. Library `@solidus-network/x401` says it is not affiliated with the draft authors.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://auth.solidus.network/v1/x401/demo"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://auth.solidus.network/v1/x401/demo",
  "note": "Independent verifier. `https://auth.solidus.network/v1/x401/demo` answered on 2026-10-29 with status 200 and a `PROOF-REQUEST` header for `scheme` `x401` and `version` `0.2.0`. Library `@solidus-network/x401` says it is not affiliated with the draft authors."
 },
 {
  "id": "solo-agentgateway-verifier",
  "org_id": "solo",
  "name": "agentgateway WIMSE enforcement",
  "url": "https://docs.solo.io/agentgateway/kubernetes/latest/documentation/security/wimse/",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Solo.io",
    "role": "Gateway verifier",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "On the receive side, Solo Enterprise for agentgateway validates proofs by setting `traffic.entWptEnforcement` in an EnterpriseAgentgatewayPolicy. When `VALIDATE_SPIFFE_TRUST_DOMAIN_NAMES=STRICT` is set and a request carries a WIT, agentgateway verifies the `x5c` certificate chain embedded in the WIT in addition to the mTLS certificate chain. WIMSE/WIT support is in the alpha state and is not supported for production. The same docs identify the current line as `2026.10.2`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.solo.io/agentgateway/kubernetes/latest/documentation/security/wimse/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.solo.io/agentgateway/kubernetes/latest/documentation/security/wimse/",
  "note": "On the receive side, Solo Enterprise for agentgateway validates proofs by setting `traffic.entWptEnforcement` in an EnterpriseAgentgatewayPolicy. When `VALIDATE_SPIFFE_TRUST_DOMAIN_NAMES=STRICT` is set and a request carries a WIT, agentgateway verifies the `x5c` certificate chain embedded in the WIT in addition to the mTLS certificate chain. WIMSE/WIT support is in the alpha state and is not suppo"
 },
 {
  "id": "solo-agentgateway-wit",
  "org_id": "solo",
  "name": "Solo Enterprise for agentgateway",
  "url": "https://docs.solo.io/agentgateway/kubernetes/latest/documentation/security/wimse/",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Solo.io",
    "role": "WIT issuer / waypoint",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Solo Enterprise for agentgateway documents WIMSE Workload Identity Tokens for service-to-service traffic when agentgateway is deployed as a waypoint proxy in an ambient mesh. WIMSE/WIT support is in the alpha state: alpha features are likely to change, are not fully tested, and are not supported for production. Deployed as a waypoint, agentgateway can forward or exchange the WIT. Emitting a proof works with both `SourceDelegation` and `SelfIdentification`. The docs page identifies the current line as `2026.10.2` and records `dateModified` 2026-10-30.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://docs.solo.io/agentgateway/kubernetes/latest/documentation/security/wimse/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://docs.solo.io/agentgateway/kubernetes/latest/documentation/security/wimse/",
  "note": "Solo Enterprise for agentgateway documents WIMSE Workload Identity Tokens for service-to-service traffic when agentgateway is deployed as a waypoint proxy in an ambient mesh. WIMSE/WIT support is in the alpha state: alpha features are likely to change, are not fully tested, and are not supported for production. Deployed as a waypoint, agentgateway can forward or exchange the WIT. Emitting a proof "
 },
 {
  "id": "spawning-api",
  "org_id": "spawning-api",
  "name": "Spawning API",
  "url": "https://spawning.substack.com/p/aitxt-a-new-way-for-websites-to-set",
  "type": "sdk",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Spawning API",
    "role": "Opt-out relay API & rules library",
    "status": "Partial",
    "status_display": "Partial · as of 2023-05-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2023-05-30",
    "col4_md": "Launch post (2023-05-30) announces that Spawning's backend API relays permissions set by `ai.txt` files to partner networks (naming Hugging Face and Stability AI), whereas the open-source `datadiligence.rules` Python package queries `https://opts-api.spawningaiapi.com/api/v2/query/urls/` and implements `TDMRepHeader` and `XRobotsTagHeader` rather than parsing /ai.txt directly.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://spawning.substack.com/p/aitxt-a-new-way-for-websites-to-set"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://spawning.substack.com/p/aitxt-a-new-way-for-websites-to-set",
  "note": "Launch post (2023-05-30) announces that Spawning's backend API relays permissions set by `ai.txt` files to partner networks (naming Hugging Face and Stability AI), whereas the open-source `datadiligence.rules` Python package queries `https://opts-api.spawningaiapi.com/api/v2/query/urls/` and implements `TDMRepHeader` and `XRobotsTagHeader` rather than parsing /ai.txt directly."
 },
 {
  "id": "spawning-wordpress-plugin",
  "org_id": "spawning-wordpress-plugin",
  "name": "Spawning WordPress plugin",
  "url": "https://github.com/Spawning-Inc/spawning-wp-plugin",
  "type": "sdk",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Spawning WordPress plugin",
    "role": "CMS / Generator",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Plugin v1.0 writes `/ai.txt` at the site root from Images, Audio, Video, Text, and Code toggles (`# Spawning AI`, `User-agent: *`, per-extension `Disallow:`). Uninstall deletes the file.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/Spawning-Inc/spawning-wp-plugin"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/Spawning-Inc/spawning-wp-plugin",
  "note": "Plugin v1.0 writes `/ai.txt` at the site root from Images, Audio, Video, Text, and Code toggles (`# Spawning AI`, `User-agent: *`, per-extension `Disallow:`). Uninstall deletes the file."
 },
 {
  "id": "specification-website-okf-index-md",
  "org_id": "website-specification",
  "name": "The Website Specification",
  "url": "https://specification.website/okf/index.md",
  "type": "origin",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "The Website Specification",
    "role": "Docs publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`okf_version: \"0.2\"` at `https://specification.website/okf/index.md` (`text/markdown`, HTTP 200).",
    "full_detail_md": "Serves https://specification.website/okf/index.md as text/markdown; charset=utf-8 (content-length 1598, HTTP 200) with okf_version: \"0.2\" and a body describing 178 checks across 10 categories. The agent-readiness page says the bundle targets OKF 0.2, is generated from the same content collection, is served at /okf/, and is packaged as /okf.tar.gz.",
    "facets": {
     "artifact_or_endpoint": "https://specification.website/okf/index.md and /okf.tar.gz",
     "content_type_or_schema": "text/markdown; charset=utf-8; YAML frontmatter okf_version 0.2",
     "discovery_mechanism": "Browsable /okf/ tree plus /okf.tar.gz archive named on the agent-readiness page",
     "version_or_posture": "Live index HTTP 200 declaring okf_version 0.2"
    },
    "telemetry": {
     "artifact_kind": "okf_index_md",
     "http_status": 200,
     "marker": "okf_version: \"0.2\""
    },
    "source_url": "https://specification.website/spec/agent-readiness/okf-bundle/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://specification.website/spec/agent-readiness/okf-bundle/",
  "note": "`okf_version: \"0.2\"` at `https://specification.website/okf/index.md` (`text/markdown`, HTTP 200)."
 },
 {
  "id": "specworks-ai-catalog",
  "org_id": "specworks-ai-catalog",
  "name": "SpecWorks AI Catalog",
  "url": "https://raw.githubusercontent.com/spec-works/ai-catalog/main/README.md",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "SpecWorks AI Catalog",
    "role": "Validator / Parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": ".NET package `SpecWorks.AiCatalog` and Python package `specworks-aicatalog` parse, validate, serialize, and install artifacts from `application/ai-catalog+json` documents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/spec-works/ai-catalog/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/spec-works/ai-catalog/main/README.md",
  "note": ".NET package `SpecWorks.AiCatalog` and Python package `specworks-aicatalog` parse, validate, serialize, and install artifacts from `application/ai-catalog+json` documents."
 },
 {
  "id": "spiffe-workload-api-clients",
  "org_id": "spiffe",
  "name": "Go and Java Workload API libraries",
  "url": "https://github.com/spiffe/go-spiffe",
  "type": "sdk",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "SPIFFE Workload API client libraries",
    "role": "Workload API SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Official Workload API clients in Go (`go-spiffe`) and Java (`java-spiffe`).",
    "full_detail_md": "The SPIRE README says officially maintained client libraries for interacting with the SPIFFE Workload API are available in Go (`go-spiffe`) and Java (`java-spiffe`).",
    "facets": {
     "svid_or_bundle_format": "Clients of the Workload API. They fetch SVIDs; they do not issue them.",
     "api_or_federation_surface": "Official SPIFFE Workload API libraries: Go go-spiffe and Java java-spiffe.",
     "attestation_or_trust_domain": "Attestation and trust-domain issuance stay in the SPIRE agent. These libraries consume the issued identity.",
     "verification_posture": "The SPIRE README names these as the officially maintained Workload API clients."
    },
    "telemetry": null,
    "source_url": "https://github.com/spiffe/spire/blob/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://github.com/spiffe/spire/blob/main/README.md",
  "note": "Official Workload API clients in Go (`go-spiffe`) and Java (`java-spiffe`)."
 },
 {
  "id": "spike",
  "org_id": "spike",
  "name": "SPIKE",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "SPIKE",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication.",
    "full_detail_md": "The SPIFFE overview lists SPIKE under open-source software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID, JWT SVID, and SPIFFE Authentication, and is not marked for Workload API. SPIKE is listed as a lightweight secrets store that uses SPIFFE as its identity control plane.",
    "facets": {
     "svid_or_bundle_format": "Marks for X.509 SVID-based authentication and JWT SVID-based authentication.",
     "api_or_federation_surface": "SPIFFE Authentication is marked (federated authentication by trust domain name). Workload API is not marked.",
     "attestation_or_trust_domain": "Trust-domain federation is the marked SPIFFE Authentication column. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication."
 },
 {
  "id": "spinxo",
  "org_id": "spinxo",
  "name": "SpinXO",
  "url": "https://www.spinxo.com",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment",
   "aipref-vocabulary"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "SpinXO",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Both surfaces serve the same statement. In robots.txt the `User-agent: *` group carries `Content-Usage: train-ai=y, search=y` under the comment that this is the AI usage preference (draft-ietf-aipref-attach), and the same line is repeated on later crawler groups. The home page responds with the header `content-usage: train-ai=y, search=y`. Vocab-08 Table 1 maps AI Training to `train-ai` (Section 4.1) and Search to `search` (Section 4.3).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain",
     "attachment": "robots.txt",
     "header_attachment_url": "https://www.spinxo.com/",
     "content_usage": "Content-Usage: train-ai=y, search=y"
    },
    "source_url": "https://www.spinxo.com/robots.txt"
   },
   {
    "protocol_id": "aipref-vocabulary",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "SpinXO",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "robots.txt sets `Content-Usage: train-ai=y, search=y` under the comment `draft-ietf-aipref-attach`. The home response sends `content-usage: train-ai=y, search=y`. `train-ai` and `search` are the AI Training and Search labels in `draft-ietf-aipref-vocab-08` Table 1. Allow and disallow map to `y` and `n`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "surface": "robots.txt",
     "content_usage": "train-ai=y, search=y",
     "header_content_usage": "train-ai=y, search=y"
    },
    "source_url": "https://www.spinxo.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.spinxo.com/robots.txt",
  "note": "Both surfaces serve the same statement. In robots.txt the `User-agent: *` group carries `Content-Usage: train-ai=y, search=y` under the comment that this is the AI usage preference (draft-ietf-aipref-attach), and the same line is repeated on later crawler groups. The home page responds with the header `content-usage: train-ai=y, search=y`. Vocab-08 Table 1 maps AI Training to `train-ai` (Section 4"
 },
 {
  "id": "spire",
  "org_id": "spiffe",
  "name": "SPIRE",
  "url": "https://github.com/spiffe/spire",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "SPIRE (CNCF)",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-05",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-05",
    "as_of": "2026-11-05",
    "col4_md": "Reference implementation of SPIFFE (CNCF Graduated); issues X.509-SVIDs, JWT-SVIDs, and (in v1.16.0, 2026-11-05) experimental WIT-SVIDs via the Workload API.",
    "full_detail_md": "SPIRE is a production-ready implementation of the SPIFFE APIs that performs node and workload attestation in order to securely issue SVIDs to workloads, and verify the SVIDs of other workloads, based on a predefined set of conditions. SPIRE was accepted to CNCF on March 29, 2018, moved to Incubating on June 22, 2020, and graduated on August 22, 2022. The latest release is `v1.16.0` (published `2026-11-05T18:37:05Z`), which adds experimental WIT-SVID support (`enable_wit_svids` server and agent options, Workload API methods, and `spire-agent api fetch wit`).",
    "facets": {
     "svid_or_bundle_format": "Generates X.509 SVIDs and JWT SVIDs, and can use existing or external PKI for X.509 issuance. Container images are published for spire-server, spire-agent, and oidc-discovery-provider.",
     "api_or_federation_surface": "Serves the SPIFFE Workload API, the Envoy SDS API, the SPIFFE Federation API, and the OIDC Federation API. Latest release tag v1.16.0, published_at 2026-11-05T18:37:05Z.",
     "attestation_or_trust_domain": "Issues SVIDs from node and/or workload attestation, for Kubernetes, VMs or bare metal, and serverless workloads.",
     "verification_posture": "CNCF moved SPIRE to Graduated on August 22, 2022. The SPIFFE open-source implements table marks all eleven issuer columns for SPIRE."
    },
    "telemetry": null,
    "source_url": "https://github.com/spiffe/spire/blob/main/README.md"
   }
  ],
  "observed": "2026-11-05",
  "date_basis": "source",
  "source": "https://github.com/spiffe/spire/blob/main/README.md",
  "note": "Reference implementation of SPIFFE (CNCF Graduated); issues X.509-SVIDs, JWT-SVIDs, and (in v1.16.0, 2026-11-05) experimental WIT-SVIDs via the Workload API."
 },
 {
  "id": "spire-wit-svid",
  "org_id": "spiffe",
  "name": "SPIRE WIT-SVID",
  "url": "https://github.com/spiffe/spire",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "SPIRE",
    "role": "WIT-SVID issuer",
    "status": "Development",
    "status_display": "Development · as of 2026-11-05",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-11-05",
    "col4_md": "Issue #6326, WIT-SVID support in SPIRE, was opened on 2025-09-18 and remains open; the SPIFFE sig-spec note states Workload Identity Token support is being brought into SPIFFE. The changelog records dummy implementations for the WIT-SVID profile (#6399) in 1.14.0 (2025-12-11), iss claim support for WIT-SVIDs (#6857) in 1.15.0 (2026-05-19), incremental WIT-SVID work for the `svid.v1` API client (#7132, #7134) in 1.15.3 (2026-08-21), and experimental WIT-SVID support in 1.16.0 (2026-11-05) gated behind the `enable_wit_svids` server and agent options with a `spire-agent api fetch wit` CLI command (#7243, #7244, #7273, #7282, #7302, #7306, #7354).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/spiffe/spire/issues/6326"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/spiffe/spire/issues/6326",
  "note": "Issue #6326, WIT-SVID support in SPIRE, was opened on 2025-09-18 and remains open; the SPIFFE sig-spec note states Workload Identity Token support is being brought into SPIFFE. The changelog records dummy implementations for the WIT-SVID profile (#6399) in 1.14.0 (2025-12-11), iss claim support for WIT-SVIDs (#6857) in 1.15.0 (2026-05-19), incremental WIT-SVID work for the `svid.v1` API client (#7"
 },
 {
  "id": "spotify",
  "org_id": "spotify",
  "name": "Spotify",
  "url": "https://newsroom.spotify.com/2025-10-06/spotify-personalized-prompts-chatgpt/",
  "type": "origin",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Spotify",
    "role": "ChatGPT app",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-06",
    "col4_md": "Live in English in 145 countries for logged-in Free, Plus, and Pro on web and mobile.",
    "full_detail_md": "Spotify's newsroom post, datePublished 2025-10-06, says the Spotify app in ChatGPT is live in English across 145 countries for logged-in ChatGPT Free, Plus, and Pro accounts on web and mobile (iOS and Android). The Verge also names Spotify in the launch set.",
    "facets": {
     "transport_or_manifest": "Vendor newsroom announcement; no plugin.json cited on this row",
     "ui_or_widget_surface": "Spotify app inside ChatGPT on web and mobile (iOS and Android)",
     "auth_or_permissions": "Logged-in ChatGPT Free, Plus, and Pro accounts",
     "sdk_or_version": "Live at Apps SDK launch, datePublished 2025-10-06; English; 145 countries"
    },
    "telemetry": null,
    "source_url": "https://newsroom.spotify.com/2025-10-06/spotify-personalized-prompts-chatgpt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://newsroom.spotify.com/2025-10-06/spotify-personalized-prompts-chatgpt/",
  "note": "Live in English in 145 countries for logged-in Free, Plus, and Pro on web and mobile."
 },
 {
  "id": "stablecoin-402-ecosystem",
  "org_id": "stablecoin",
  "name": "stablecoin.com x402 ecosystem",
  "url": "https://stablecoin.com/402/ecosystem",
  "type": "authority",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "stablecoin.com x402 ecosystem",
    "role": "Ecosystem directory",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Directory of facilitators, payment schemes, and settlement chains.",
    "full_detail_md": "Third-party table of x402 ecosystem entries. Rows include the default testnet facilitator and an independent Rust facilitator, with scheme and chain columns that vary by listing.",
    "facets": null,
    "telemetry": null,
    "source_url": "https://stablecoin.com/402/ecosystem"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://stablecoin.com/402/ecosystem",
  "note": "Directory of facilitators, payment schemes, and settlement chains."
 },
 {
  "id": "stableenrich",
  "org_id": "merit-systems",
  "name": "StableEnrich",
  "url": "https://stableenrich.dev",
  "type": "origin",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "StableEnrich",
    "role": "Seller",
    "status": "Listed",
    "status_display": "Listed · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Catalog active: Merit Systems, `tempo` `charge`; POST `/api/apollo/people-search` finds prospects.",
    "full_detail_md": "The catalog lists StableEnrich as active, provider Merit Systems, with method tempo, intent charge, and asset 0x20c000000000000000000000b9537d11c60e8b50. POST /api/apollo/people-search finds prospects by filters.",
    "facets": {
     "settlement_rail": "tempo charge on asset 0x20c000000000000000000000b9537d11c60e8b50",
     "challenge_or_scheme": "Catalog status active; provider Merit Systems",
     "headers_or_methods": "Payment method tempo, intent charge",
     "sdk_or_endpoint": "POST /api/apollo/people-search finds prospects by filters"
    },
    "telemetry": null,
    "source_url": "https://mpp.dev/api/services"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.dev/api/services",
  "note": "Catalog active: Merit Systems, `tempo` `charge`; POST `/api/apollo/people-search` finds prospects."
 },
 {
  "id": "stackoverflow",
  "org_id": "stackoverflow",
  "name": "Stack Overflow",
  "url": "https://stackoverflow.blog/2026/02/19/stack-overflow-cloudflare-pay-per-crawl/",
  "type": "origin",
  "implements": [
   "cloudflare-pay-per-crawl"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-pay-per-crawl",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Stack Overflow",
    "role": "Publisher (announced beta co-launch partner)",
    "status": "Supported (release announcement)",
    "status_display": "Supported (release announcement) · as of 2026-02-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-02-19",
    "col4_md": "Announced private-beta co-launch partner reporting WAF-wrapped HTTP 402 responses to targeted bots; live endpoint not independently verified.",
    "full_detail_md": "In a February 19, 2026 Stack Overflow blog post and podcast discussion with Cloudflare VP Will Allen, Stack Overflow reported enrolling in Cloudflare's Pay Per Crawl private beta via a dashboard UI wrapping WAF rules to allow targeted bots or charge them at a configured rate, noting that turning on the switch served HTTP 402 Payment Required responses to bots that previously received 403 blocks. Evidence is based on Stack Overflow's self-reported announcement; live HTTP 402 responses on stackoverflow.com were not independently verified.",
    "facets": {
     "scope_host": "https://stackoverflow.blog/2026/02/19/stack-overflow-cloudflare-pay-per-crawl/ (self-reported Cloudflare instance enrollment)",
     "policy_or_enforcement_role": "Announced private-beta co-launch publisher configuring Cloudflare WAF-wrapped Allow or Charge rules per targeted bot",
     "pricing_or_headers": "Reported serving HTTP 402 Payment Required in place of prior 403 blocks (specific charge rate not disclosed)",
     "auth_mechanism": "Delegated to Cloudflare Pay Per Crawl edge enforcement",
     "beta_or_availability_posture": "Announced launch partner (private beta, 2026-02-19 blog post) — live endpoint not independently verified"
    },
    "telemetry": null,
    "source_url": "https://stackoverflow.blog/2026/02/19/stack-overflow-cloudflare-pay-per-crawl/"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "source",
  "source": "https://stackoverflow.blog/2026/02/19/stack-overflow-cloudflare-pay-per-crawl/",
  "note": "Announced private-beta co-launch partner reporting WAF-wrapped HTTP 402 responses to targeted bots; live endpoint not independently verified."
 },
 {
  "id": "steve-madden",
  "org_id": "steve-madden",
  "name": "Steve Madden",
  "url": "https://www.stevemadden.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Steve Madden",
    "role": "Seller (Shopify merchant)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`.",
    "full_detail_md": "The live profile declares protocol version 2026-08-25 (the ucp.version field, not a publication date) on stevemadden.myshopify.com, where dev.ucp.shopping binds transports mcp and embedded and no dev.ucp.common service is published. Payment handlers are com.google.pay at handler spec 2026-01-11, dev.shopify.card at handler spec 2026-01-15, and dev.shopify.shop_pay at handler spec 2026-04-08, and capabilities include dev.ucp.shopping.checkout plus dev.ucp.common.identity_linking.",
    "facets": {
     "commerce_surface": "Shopify storefront stevemadden.myshopify.com",
     "payment_handlers_or_rail": "com.google.pay (handler spec 2026-01-11), dev.shopify.card (handler spec 2026-01-15), dev.shopify.shop_pay (handler spec 2026-04-08)",
     "transport_bindings": "dev.ucp.shopping over mcp and embedded; no dev.ucp.common service",
     "spec_version": "ucp.version 2026-08-25 (protocol version, not a publication date); supported_versions also lists 2026-04-08 and 2026-01-23"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8",
     "ucp_version": "2026-08-25",
     "transports": [
      "mcp",
      "embedded"
     ],
     "payment_handlers": [
      "com.google.pay",
      "dev.shopify.card",
      "dev.shopify.shop_pay"
     ],
     "merchant_host": "stevemadden.myshopify.com",
     "publishes_dev_ucp_common_service": false
    },
    "source_url": "https://www.stevemadden.com/.well-known/ucp"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.stevemadden.com/.well-known/ucp",
  "note": "`2026-08-25` via `mcp` and `embedded`; `com.google.pay`, `dev.shopify.card`, `dev.shopify.shop_pay`."
 },
 {
  "id": "storewalk-trx-009",
  "org_id": "storewalk-trx-009",
  "name": "Storewalk TRX-009",
  "url": "https://storewalk.ai/checks/TRX-009",
  "type": "authority",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Storewalk TRX-009",
    "role": "Verifier / Audit parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Passive check TRX-009: /auth.md must exist, the body must be a Markdown document rather than the storefront HTML page, and the file must open with a heading that names auth.md.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://storewalk.ai/checks/TRX-009"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://storewalk.ai/checks/TRX-009",
  "note": "Passive check TRX-009: /auth.md must exist, the body must be a Markdown document rather than the storefront HTML page, and the file must open with a heading that names auth.md."
 },
 {
  "id": "stripe",
  "org_id": "stripe",
  "name": "Stripe",
  "url": "https://stripe.com",
  "type": "venue",
  "implements": [
   "agentic-commerce-protocol",
   "cloudflare-pay-per-crawl",
   "mpp",
   "ucp",
   "x402"
  ],
  "archetypes": [
   "crawler_policy",
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Payment rail (Co-author)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Codeveloped ACP; public-preview Shared Payment Tokens in the US, Canada, and select European countries.",
    "full_detail_md": "The Agentic Commerce Protocol was codeveloped by Stripe and OpenAI. Shared payment tokens (SPTs) are marked Public preview. They grant sellers scoped access to customers' payment methods for agent-initiated purchases, and Stripe says SPTs are available to agents, customers, and sellers in the US, Canada, and select European countries. The ACP site calls Stripe the first compatible PSP with its Shared Payment Token.",
    "facets": {
     "commerce_role_or_surface": "Co-author and first compatible payment service provider",
     "payment_or_token_rail": "Shared Payment Token (public preview) for agent-initiated purchases",
     "api_or_spec_version": "Agentic Commerce Protocol, codeveloped by Stripe and OpenAI",
     "availability_or_eligibility_posture": "Agents, customers, and sellers in the US, Canada, and select European countries"
    },
    "telemetry": null,
    "source_url": "https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce"
   },
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Payment processor (Governing Council)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-02",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-02",
    "col4_md": "Checkout, identity linking, order tracking, and payment-token exchange.",
    "full_detail_md": "Stripe documents UCP support for checkout, identity linking, order tracking, and secure payment token exchange, and states that Stripe is a member of the UCP Tech Council. Separately, Stripe joined the Governing Council on April 28, 2026, is an inaugural Payments Technical Council member as of September 2, 2026, and MAINTAINERS.md seats Twum Djin (Stripe).",
    "facets": {
     "commerce_surface": "Payment processor and UCP Tech Council member",
     "payment_handlers_or_rail": "Secure payment token exchange, plus checkout, identity linking, and order tracking",
     "transport_bindings": "Documented UCP protocol support; not graded from a floating main-branch source file",
     "spec_version": "Governing Council join dated April 28, 2026; Payments TC formed September 2, 2026"
    },
    "telemetry": null,
    "source_url": "https://docs.stripe.com/agentic-commerce/protocols/ucp"
   },
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Payment rail (TSC member)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Accepts `exact` USDC on Base (`2026-05-27.preview` `transaction_verification`); requires Dashboard approval and US (ex-NY) or 30+ country eligibility.",
    "full_detail_md": "Stripe serves on the x402 Technical Steering Committee and lets eligible merchants accept x402 USDC payments on Base (`eip155:8453`, `scheme: \"exact\"`) via `/v1/crypto/deposit_addresses`, the CDP Facilitator, and `PaymentIntent` `transaction_verification` mode (requiring preview API `Stripe-Version: 2026-05-27.preview`). Availability requires requesting the Stablecoins and Crypto payment method in the Stripe Dashboard and is gated to US states except New York (plus 30+ countries upon access request).",
    "facets": {
     "settlement_rail": "x402 `exact` scheme settled via Coinbase CDP Facilitator into Stripe `PaymentIntent` (`transaction_verification`)",
     "supported_assets": "USDC on Base settled into merchant Stripe balance",
     "chains_or_networks": "Base mainnet (`eip155:8453`, `network: \"base\"`)",
     "headers_or_methods": "HTTP 402 via `@x402/hono` `paymentMiddleware`, `/v1/crypto/deposit_addresses`, and `Stripe-Version: 2026-05-27.preview`",
     "eligibility_and_approval": "Requires requesting Stablecoins and Crypto in Dashboard; available in US states except New York, plus 30+ countries upon access request; requires `2026-05-27.preview` API (`transaction_verification`)"
    },
    "telemetry": null,
    "source_url": "https://docs.stripe.com/payments/machine/x402"
   },
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Payment rail (Co-author)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`stripe` `charge` via cards, buy-now-pay-later SPTs, and stablecoin offramp into the Stripe balance.",
    "full_detail_md": "Stripe co-authored MPP and currently supports the charge intent: cards and buy now, pay later via Shared Payment Tokens, plus stablecoin payments that Stripe automatically offramps into the Stripe balance. The documented challenge is WWW-Authenticate: Payment method=\"stripe\", intent=\"charge\".",
    "facets": {
     "settlement_rail": "Cards and buy now, pay later via Shared Payment Tokens, plus stablecoins offramped into the Stripe balance",
     "challenge_or_scheme": "HTTP Payment authentication scheme, method stripe, intent charge",
     "headers_or_methods": "WWW-Authenticate: Payment method=\"stripe\", intent=\"charge\"",
     "sdk_or_endpoint": "Stripe MPP docs; charge is the only intent Stripe currently documents as supported"
    },
    "telemetry": null,
    "source_url": "https://docs.stripe.com/payments/machine/mpp"
   },
   {
    "protocol_id": "cloudflare-pay-per-crawl",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_b",
    "actor": "Stripe",
    "role": "Payment processor & payout rail",
    "status": "Supported",
    "status_display": "Supported · as of 2026-04-23",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-04-23",
    "col4_md": "Invoices AI crawler owners via Stripe and pays publishers monthly via dedicated Cloudflare Stripe Connect accounts; Cloudflare's 2025-09-23 `x402` post separately describes a single end-of-day card or bank fee.",
    "full_detail_md": "Under Cloudflare's Merchant-of-Record model, AI crawler owners connect a Cloudflare account to Stripe (`Connect to Stripe` in the Pay Per Crawl tab) so charges recorded upon HTTP 200 delivery with valid crawler price headers (`crawler-charged`) are invoiced via Stripe, while participating site owners create a dedicated Cloudflare Stripe Connect account (pre-existing Stripe accounts are not compatible) for monthly payouts after Cloudflare aggregates and reconciles recorded charges. Separately, Cloudflare's 2025-09-23 `x402` blog post states that private-beta crawlers are charged a single fee via a connected credit card or bank account at the end of each day.",
    "facets": {
     "scope_host": "https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/connect-to-stripe/",
     "policy_or_enforcement_role": "Off-wire fiat payment processor for crawler invoicing and dedicated Stripe Connect publisher payouts under Cloudflare as Merchant of Record",
     "pricing_or_headers": "Records charges on HTTP 200 responses carrying crawler-charged after valid crawler-exact-price or crawler-max-price request headers",
     "auth_mechanism": "Cloudflare account linked to Stripe (crawler owners) and dedicated Cloudflare Stripe Connect account (site owners)",
     "beta_or_availability_posture": "Active settlement rail for Pay Per Crawl closed/private beta (docs updated 2026-04-23)"
    },
    "telemetry": null,
    "source_url": "https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/connect-to-stripe/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce",
  "note": "Codeveloped ACP; public-preview Shared Payment Tokens in the US, Canada, and select European countries."
 },
 {
  "id": "stripe-link-cli",
  "org_id": "stripe",
  "name": "Stripe Link CLI",
  "url": "https://github.com/stripe/link-cli",
  "type": "sdk",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Stripe Link CLI",
    "role": "Wallet CLI & MCP server (Co-author)",
    "status": "Partial",
    "status_display": "Partial · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`npx skills add stripe/link-cli` provisions SPT credentials; `mpp pay` buys (US and Canada).",
    "full_detail_md": "The Stripe Link CLI provisions one-time shared payment token credentials from a Link account for Machine Payment Protocols (MPP), and for now this is only available to US and Canadian Link accounts. Install with npx skills add stripe/link-cli, mpp pay completes purchases, and Stripe docs say to register it as an MCP server.",
    "facets": {
     "settlement_rail": "One-time shared payment token credentials from a Link account",
     "challenge_or_scheme": "Machine Payment Protocols (MPP); mpp pay completes purchases",
     "headers_or_methods": "Client credential provisioning; Stripe docs say to register it as an MCP server",
     "sdk_or_endpoint": "npx skills add stripe/link-cli; US and Canadian Link accounts only"
    },
    "telemetry": null,
    "source_url": "https://github.com/stripe/link-cli"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/stripe/link-cli",
  "note": "`npx skills add stripe/link-cli` provisions SPT credentials; `mpp pay` buys (US and Canada)."
 },
 {
  "id": "stripe-mcp",
  "org_id": "stripe",
  "name": "Stripe MCP Server",
  "url": "https://mcp.stripe.com",
  "type": "origin",
  "implements": [
   "mcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Stripe",
    "role": "Remote & local MCP server",
    "status": "Live (HTTP 401)",
    "status_display": "Live (HTTP 401) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Remote server at `https://mcp.stripe.com` with OAuth `resource_metadata` challenge, Agent API keys, and `missing_api_key` error.",
    "full_detail_md": "Stripe's remote MCP server at `https://mcp.stripe.com` returns HTTP 401 with `WWW-Authenticate: Bearer resource_metadata=\"https://mcp.stripe.com/.well-known/oauth-protected-resource\"` and JSON error `missing_api_key`, supporting OAuth user consent flows and persistent Bearer Agent API keys.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1 Protected Resource Metadata, Stripe Agent API key (Bearer)",
     "primitives": "tools",
     "sdk_or_package": "https://mcp.stripe.com"
    },
    "telemetry": {
     "http_status": 401,
     "content_type": "application/json",
     "error_code": "missing_api_key"
    },
    "source_url": "https://mcp.stripe.com"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mcp.stripe.com",
  "note": "Remote server at `https://mcp.stripe.com` with OAuth `resource_metadata` challenge, Agent API keys, and `missing_api_key` error."
 },
 {
  "id": "stytch-cimd",
  "org_id": "stytch",
  "name": "Stytch",
  "url": "https://stytch.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Stytch",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-17",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-17",
    "col4_md": "Announced 2025-10-17; discovers clients without pre-registering credentials.",
    "full_detail_md": "Stytch announced CIMD support on Oct 17, 2025. The post says Stytch supports Client ID Metadata Documents so apps can discover and verify clients without pre-registering or hardcoding credentials.",
    "facets": {
     "metadata_flag_or_profile": "Product announcement of Client ID Metadata Document support for discovering and verifying clients",
     "auth_method_or_pkce": "Described as avoiding pre-registered or hardcoded credentials; the post does not name a PKCE method",
     "uri_or_ssrf_rules": "Not specified in the announcement post",
     "draft_or_spec_version": "Announcement dated Oct 17, 2025 (probe as_of 2025-10-17); the post does not name a CIMD draft revision"
    },
    "telemetry": null,
    "source_url": "https://stytch.com/blog/stytch-supports-cimd/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://stytch.com/blog/stytch-supports-cimd/",
  "note": "Announced 2025-10-17; discovers clients without pre-registering credentials."
 },
 {
  "id": "supabase",
  "org_id": "supabase",
  "name": "Supabase",
  "url": "https://supabase.com/.well-known/ard.json",
  "type": "origin",
  "implements": [
   "api-catalog-rfc9727",
   "ard"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ard",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Supabase",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"1.0\"`) with 5 entries, first `urn:air:supabase.com:mcp:server` type `application/json` at https://mcp.supabase.com/mcp",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://supabase.com/.well-known/ard.json"
   },
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Supabase",
    "role": "Postgres & MCP API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`application/linkset+json` lists `item` `https://api.supabase.com/v1` and `https://mcp.supabase.com/mcp`; no `Link` header.",
    "full_detail_md": "On 2026-11-04, `https://supabase.com/.well-known/api-catalog` returned HTTP 200 (`content-type: application/linkset+json`, `content-length: 1030`, `last-modified: Wed, 04 Nov 2026 19:52:25 GMT`) with no `Link` response header. The `item` array lists `https://api.supabase.com/v1` (`service-desc` `application/openapi+json`, `service-doc`, `status`) and `https://mcp.supabase.com/mcp` (`service-doc` plus `service-meta` for the OAuth protected-resource document).",
    "facets": {
     "well_known_endpoint": "https://supabase.com/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json",
     "link_relations": "item (https://api.supabase.com/v1, https://mcp.supabase.com/mcp); service-desc; service-doc; status; service-meta",
     "http_or_link_header": "HTTP 200; no Link rel=api-catalog response header; last-modified Wed, 04 Nov 2026 19:52:25 GMT"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json",
     "link_header_rel_api_catalog": false,
     "has_item_array": true
    },
    "source_url": "https://supabase.com/.well-known/api-catalog"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://supabase.com/.well-known/ard.json",
  "note": "`/.well-known/ard.json` (`application/json`); unsigned `entries` catalog (`specVersion` `\"1.0\"`) with 5 entries, first `urn:air:supabase.com:mcp:server` type `application/json` at https://mcp.supabase.com/mcp"
 },
 {
  "id": "supabase-com-docs-llms-txt",
  "org_id": "supabase",
  "name": "Supabase Docs",
  "url": "https://supabase.com/docs/llms.txt",
  "type": "origin",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Supabase (Docs)",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://supabase.com/docs/llms.txt` as `text/plain` (`# Supabase Docs`) under `/docs/`, linking `llms-full.txt`, OpenAPI spec, and MCP server.",
    "full_detail_md": "Serves `https://supabase.com/docs/llms.txt` as `text/plain; charset=utf-8` (3,652 bytes, fetched 2026-11-04). Deployed under `/docs/`, the file opens `# Supabase Docs`, links `https://supabase.com/llms-full.txt` for single-file ingestion, and indexes `.md` guide pages alongside `https://supabase.com/openapi.json` and `https://mcp.supabase.com/mcp`.",
    "facets": {
     "artifact_path": "https://supabase.com/docs/llms.txt",
     "companion_files": "https://supabase.com/llms-full.txt; https://supabase.com/openapi.json; https://mcp.supabase.com/mcp; .md guides",
     "content_type_or_bytes": "text/plain; charset=utf-8 (3,652 bytes)",
     "generator_or_consumer_mode": "Subpath documentation index (/docs/llms.txt)"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# Supabase Docs"
    },
    "source_url": "https://supabase.com/docs/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://supabase.com/docs/llms.txt",
  "note": "Serves `https://supabase.com/docs/llms.txt` as `text/plain` (`# Supabase Docs`) under `/docs/`, linking `llms-full.txt`, OpenAPI spec, and MCP server."
 },
 {
  "id": "superfluid-wallet",
  "org_id": "superfluid-wallet",
  "name": "Superfluid Wallet",
  "url": "https://www.superfluidwallet.com/identity",
  "type": "agent",
  "implements": [
   "x401"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "x401",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Superfluid Wallet",
    "role": "Agent wallet / Proof presenter",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Wallet presentation of an x401 proof. The identity page says an agent proves a verified person with x401 before it pays or signs up, and the agent reference says it follows x401 0.2.0.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.superfluidwallet.com/identity"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.superfluidwallet.com/identity",
  "note": "Wallet presentation of an x401 proof. The identity page says an agent proves a verified person with x401 before it pays or signs up, and the agent reference says it follows x401 0.2.0."
 },
 {
  "id": "svelte-llms-txt",
  "org_id": "svelte",
  "name": "Svelte",
  "url": "https://svelte.dev/llms.txt",
  "type": "sdk",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Svelte",
    "role": "Framework docs origin",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://svelte.dev/llms.txt` (`# Svelte Documentation for LLMs`, `text/plain`), linking `llms-small.txt`, `llms-medium.txt`, and `llms-full.txt` bundles.",
    "full_detail_md": "Serves `https://svelte.dev/llms.txt` (`HTTP 200`, `text/plain; charset=utf-8`, 2,177 bytes, fetched 2026-11-04) opening `# Svelte Documentation for LLMs` with a summary blockquote and linking tiered single-file bundles (`llms-small.txt`, `llms-medium.txt`, and `llms-full.txt`) alongside per-package documentation.",
    "facets": {
     "artifact_path": "https://svelte.dev/llms.txt",
     "companion_files": "https://svelte.dev/llms-small.txt; https://svelte.dev/llms-medium.txt; https://svelte.dev/llms-full.txt",
     "content_type_or_bytes": "text/plain; charset=utf-8 (2,177 bytes)",
     "generator_or_consumer_mode": "Multi-tier context index (small, medium, and full bundles)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Svelte Documentation for LLMs"
    },
    "source_url": "https://svelte.dev/llms.txt"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://svelte.dev/llms.txt",
  "note": "Serves `https://svelte.dev/llms.txt` (`# Svelte Documentation for LLMs`, `text/plain`), linking `llms-small.txt`, `llms-medium.txt`, and `llms-full.txt` bundles."
 },
 {
  "id": "swiftui",
  "org_id": "google",
  "name": "A2UI SwiftUI renderer",
  "url": "https://a2ui.org/roadmap/",
  "type": "sdk",
  "implements": [
   "a2ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "SwiftUI",
    "role": "Apple renderer",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Roadmap marks SwiftUI Alpha for iOS/macOS (v0.9, v0.9.1, v1.0); renderers matrix marks v1.0 Planned. The Google Developers Blog says SwiftUI on iOS and Jetpack Compose on Android are currently v0.9.1, with v1.0 coming soon.",
    "full_detail_md": "The roadmap marks SwiftUI Alpha for iOS/macOS covering v0.9, v0.9.1, and v1.0, whereas the renderers reference table lists SwiftUI as Planned on v1.0.",
    "facets": {
     "transport_or_binding": "Native Apple renderer listed on the roadmap",
     "component_or_catalog": "SwiftUI coverage of v0.9, v0.9.1, and v1.0",
     "spec_version": "Alpha on the roadmap; Planned on v1.0 in the renderers matrix",
     "sdk_or_renderer": "SwiftUI for iOS and macOS"
    },
    "telemetry": null,
    "source_url": "https://a2ui.org/roadmap/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://a2ui.org/roadmap/",
  "note": "Roadmap marks SwiftUI Alpha for iOS/macOS (v0.9, v0.9.1, v1.0); renderers matrix marks v1.0 Planned. The Google Developers Blog says SwiftUI on iOS and Jetpack Compose on Android are currently v0.9.1, with v1.0 coming soon."
 },
 {
  "id": "swivel",
  "org_id": "swivel",
  "name": "Swivel",
  "url": "https://adcp.swivel.ai/mcp",
  "type": "agent",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Swivel",
    "role": "Sales agent",
    "status": "Listed",
    "status_display": "Listed · as of 2026-06-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-19",
    "col4_md": "Talpa's adagents.json lists `https://adcp.swivel.ai/mcp` under `authorized_agents`, `authorized_for` All Talpa Network properties, with `authorization_type` `property_tags` and `delegation_type` `direct`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://kijk.nl/.well-known/adagents.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://kijk.nl/.well-known/adagents.json",
  "note": "Talpa's adagents.json lists `https://adcp.swivel.ai/mcp` under `authorized_agents`, `authorized_for` All Talpa Network properties, with `authorization_type` `property_tags` and `delegation_type` `direct`."
 },
 {
  "id": "talpa-kijk",
  "org_id": "talpa",
  "name": "Talpa Network (kijk.nl)",
  "url": "https://kijk.nl/.well-known/adagents.json",
  "type": "origin",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Talpa Network",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-19",
    "col4_md": "HTTP 200 at `https://kijk.nl/.well-known/adagents.json`. The document sets `$schema` to `https://adcontextprotocol.org/schemas/v3/adagents.json`, contact `seller_id` `58523` for Talpa Media, and `last_updated` 2026-06-19. `authorized_agents` names `https://adcp.swivel.ai/mcp`, `https://adcp-salesagent.api.tritondigital.com/mcp`, and `https://interchange.io`, each with `authorization_type` `property_tags`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=utf-8",
     "schema": "https://adcontextprotocol.org/schemas/v3/adagents.json",
     "seller_id": "58523"
    },
    "source_url": "https://kijk.nl/.well-known/adagents.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://kijk.nl/.well-known/adagents.json",
  "note": "HTTP 200 at `https://kijk.nl/.well-known/adagents.json`. The document sets `$schema` to `https://adcontextprotocol.org/schemas/v3/adagents.json`, contact `seller_id` `58523` for Talpa Media, and `last_updated` 2026-06-19. `authorized_agents` names `https://adcp.swivel.ai/mcp`, `https://adcp-salesagent.api.tritondigital.com/mcp`, and `https://interchange.io`, each with `authorization_type` `propert"
 },
 {
  "id": "target",
  "org_id": "target",
  "name": "Target",
  "url": "https://www.target.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Target",
    "role": "Retailer (co-developer)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-15",
    "col4_md": "Buy in Google Search AI Mode and Gemini via UCP; Universal Cart merchant.",
    "full_detail_md": "Target's fact sheet, updated Jun 18, 2026, says shoppers can browse product listings and buy items directly from Target in Google Search, including AI Mode, and the Gemini app, and that the capability comes from the Universal Commerce Protocol. The launch post (datePublished 2026-01-11) names Target as a co-developer, and Universal Cart (datePublished 2026-10-15) includes Target among merchants for checkout powered by UCP.",
    "facets": {
     "commerce_surface": "Target listings in Google Search, AI Mode, and the Gemini app",
     "payment_handlers_or_rail": "UCP-powered checkout; Universal Cart merchant as of 2026-10-15",
     "transport_bindings": "Google AI surfaces; no probed Target /.well-known/ucp body in this row",
     "spec_version": "Co-developer in the 2026-01-11 launch; fact sheet updated Jun 18, 2026; cart post datePublished 2026-10-15"
    },
    "telemetry": null,
    "source_url": "https://corporate.target.com/press/fact-sheet/2026/06/conversational-ai"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://corporate.target.com/press/fact-sheet/2026/06/conversational-ai",
  "note": "Buy in Google Search AI Mode and Gemini via UCP; Universal Cart merchant."
 },
 {
  "id": "teleport-machine-workload-identity",
  "org_id": "teleport",
  "name": "Machine & Workload Identity",
  "url": "https://goteleport.com",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Teleport",
    "role": "Workload credential issuer",
    "status": "Development",
    "status_display": "Development · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "draft-ietf-wimse-workload-creds-03 (dated 30 October 2026) records Teleport Machine & Workload Identity with Workload Identity Certificate maturity production and Workload Identity Token maturity research. The coverage line for that entry lists the Workload Identity Certificate.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.ietf.org/archive/id/draft-ietf-wimse-workload-creds-03.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ietf.org/archive/id/draft-ietf-wimse-workload-creds-03.txt",
  "note": "draft-ietf-wimse-workload-creds-03 (dated 30 October 2026) records Teleport Machine & Workload Identity with Workload Identity Certificate maturity production and Workload Identity Token maturity research. The coverage line for that entry lists the Workload Identity Certificate."
 },
 {
  "id": "teleport-workload-identity",
  "org_id": "teleport",
  "name": "Teleport Workload Identity",
  "url": "https://goteleport.com/blog/workload-identity/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Teleport Workload Identity",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2024-04-11",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2024-04-11",
    "col4_md": "Adds a SPIFFE Workload API, SVID issuance, TPM attestation, and AWS Roles Anywhere.",
    "full_detail_md": "Published April 11, 2024, Teleport Workload Identity extends Teleport Machine ID with a SPIFFE workload API endpoint, the ability to issue SVIDs, TPM server attestation, and support for AWS Roles Anywhere.",
    "facets": {
     "svid_or_bundle_format": "Issues SVIDs. The cited sentence does not split X.509-SVID from JWT-SVID.",
     "api_or_federation_surface": "A SPIFFE Workload API endpoint, plus support for AWS Roles Anywhere.",
     "attestation_or_trust_domain": "TPM server attestation, extending Teleport Machine ID.",
     "verification_posture": "Teleport announcement published April 11, 2024."
    },
    "telemetry": null,
    "source_url": "https://goteleport.com/blog/workload-identity/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://goteleport.com/blog/workload-identity/",
  "note": "Adds a SPIFFE Workload API, SVID issuance, TPM attestation, and AWS Roles Anywhere."
 },
 {
  "id": "telnyx-assistant",
  "org_id": "telnyx",
  "name": "Telnyx Assistant",
  "url": "https://telnyx.com/.well-known/agent-card.json",
  "type": "agent",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Telnyx (Telnyx Assistant)",
    "role": "Public A2A agent",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "Live Agent Card binding `JSONRPC` (`1.0` and `0.3`) at `https://api.telnyx.com/v2/support_agent/public/a2a` with `tasks/get` polling.",
    "full_detail_md": "Telnyx serves a live HTTP 200 Agent Card at https://telnyx.com/.well-known/agent-card.json (`Telnyx Assistant` v`1.1.0`, checked 2026-11-03) declaring `supportedInterfaces` over `JSONRPC` at `https://api.telnyx.com/v2/support_agent/public/a2a` for both `protocolVersion` `1.0` and `0.3` (alongside legacy root `preferredTransport`: `\"JSONRPC\"` and `protocolVersion`: `\"0.3\"`), with `streaming`: `false`, task-state polling via `tasks/get`, keyless public access, and six skills (`public-pricing`, `country-coverage`, `product-and-evaluation`, `ask-docs`, `platform-status`, and `feature-requests`).",
    "facets": {
     "transport_bindings": "JSONRPC at https://api.telnyx.com/v2/support_agent/public/a2a (streaming: false; tasks/get polling)",
     "discovery_artifact": "GET https://telnyx.com/.well-known/agent-card.json (v1.1.0, dual v1.0 supportedInterfaces and v0.3 root fields)",
     "protocol_version": "1.0 and 0.3",
     "auth_schemes": "None (public keyless access)",
     "verification_posture": "Live HTTP 200 Agent Card probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "protocol_versions": [
      "1.0",
      "0.3"
     ],
     "agent_version": "1.1.0"
    },
    "source_url": "https://telnyx.com/.well-known/agent-card.json"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://telnyx.com/.well-known/agent-card.json",
  "note": "Live Agent Card binding `JSONRPC` (`1.0` and `0.3`) at `https://api.telnyx.com/v2/support_agent/public/a2a` with `tasks/get` polling."
 },
 {
  "id": "tempo",
  "org_id": "tempo",
  "name": "Tempo",
  "url": "https://tempo.xyz",
  "type": "venue",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Tempo (Tempo Labs / Paradigm)",
    "role": "Settlement chain (Co-author)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-18",
    "col4_md": "`tempo` supports `charge`, `session`, and `subscription`; Tempo Labs and Stripe maintain the spec.",
    "full_detail_md": "MPP runs on Tempo today; Tempo supports charge, session, and subscription, and Fortune describes Tempo as incubated by Stripe and Paradigm. The documented challenge is WWW-Authenticate: Payment method=\"tempo\", intent=\"charge\", and the specification is maintained by Tempo Labs and Stripe.",
    "facets": {
     "settlement_rail": "Tempo; MPP runs on Tempo today and the protocol is described as rail-agnostic",
     "challenge_or_scheme": "HTTP Payment authentication scheme, method tempo, intents charge, session, and subscription",
     "headers_or_methods": "WWW-Authenticate: Payment method=\"tempo\", intent=\"charge\"",
     "sdk_or_endpoint": "Specification maintained by Tempo Labs and Stripe"
    },
    "telemetry": null,
    "source_url": "https://tempo.xyz/blog/mainnet/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://tempo.xyz/blog/mainnet/",
  "note": "`tempo` supports `charge`, `session`, and `subscription`; Tempo Labs and Stripe maintain the spec."
 },
 {
  "id": "tempo-cli-wallet",
  "org_id": "tempo",
  "name": "Tempo CLI Wallet",
  "url": "https://mpp.dev/services",
  "type": "sdk",
  "implements": [
   "mpp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Tempo CLI Wallet",
    "role": "Wallet CLI (Co-author)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Tempo CLI wallet funds agent use of MPP; the directory accepts production-ready services.",
    "full_detail_md": "Install the Tempo CLI and its wallet to fund your agent's use of MPP services. The curated directory accepts live, production-ready MPP services.",
    "facets": {
     "settlement_rail": "Tempo CLI wallet funding an agent's use of MPP services",
     "challenge_or_scheme": "Client wallet for paying MPP services in the curated directory",
     "headers_or_methods": "Client funding of requests to services that answer with the Payment challenge",
     "sdk_or_endpoint": "Tempo CLI and its wallet; curated directory at mpp.dev/services"
    },
    "telemetry": null,
    "source_url": "https://mpp.dev/services"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://mpp.dev/services",
  "note": "Tempo CLI wallet funds agent use of MPP; the directory accepts production-ready services."
 },
 {
  "id": "temporal-sdk-java-agents-md",
  "org_id": "temporalio",
  "name": "temporalio/sdk-java",
  "url": "https://raw.githubusercontent.com/temporalio/sdk-java/master/AGENTS.md",
  "type": "origin",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "temporalio/sdk-java",
    "role": "Repo publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves root `AGENTS.md` (`# Contributor Quickstart Guide`, `text/plain`) with Gradle layout, `./gradlew spotlessCheck`, and `./gradlew test` rules.",
    "full_detail_md": "Serves root `AGENTS.md` (HTTP 200, `text/plain; charset=utf-8`, 2,391 bytes, checked 2026-11-04) opening `# Contributor Quickstart Guide`, documenting the multi-module Gradle layout (`temporal-sdk`, `temporal-testing`, `temporal-test-server`, `temporal-serviceclient`), review checklist (`./gradlew spotlessCheck`, `./gradlew test`), and root `CONTRIBUTING.md` reference.",
    "facets": {
     "artifact_path": "https://raw.githubusercontent.com/temporalio/sdk-java/master/AGENTS.md",
     "repo_scope": "Temporal Java SDK multi-module repository root (2,391 bytes)",
     "heading_structure": "# Contributor Quickstart Guide; ## Repository Layout; ## General Guidance; ## Building and Testing; ## Tests; ## Commit Messages and Pull Requests; ## Review Checklist",
     "precedence_or_nested_files": "Root guide covering Gradle submodules and referencing root CONTRIBUTING.md"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "h1_title": "# Contributor Quickstart Guide"
    },
    "source_url": "https://raw.githubusercontent.com/temporalio/sdk-java/master/AGENTS.md"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/temporalio/sdk-java/master/AGENTS.md",
  "note": "Serves root `AGENTS.md` (`# Contributor Quickstart Guide`, `text/plain`) with Gradle layout, `./gradlew spotlessCheck`, and `./gradlew test` rules."
 },
 {
  "id": "terminal-agent",
  "org_id": "ag-ui",
  "name": "Terminal + Agent",
  "url": "https://docs.ag-ui.com/introduction",
  "type": "sdk",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Terminal + Agent",
    "role": "Terminal client",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Overview lists a terminal client; AG-UI is an event stream, not a web-only renderer.",
    "full_detail_md": "The overview lists Terminal + Agent as a Supported community client and says an AG-UI client does not have to be a web application: the protocol describes an event stream rather than a rendering target, so a terminal, a mobile app, or a chat platform can each act as a client.",
    "facets": {
     "transport": "Not stated beyond the AG-UI event stream",
     "event_or_state_model": "Ordered event stream with no required rendering target",
     "integration_role": "Community terminal client",
     "sdk_or_package": "Not named; Getting Started link only"
    },
    "telemetry": null,
    "source_url": "https://docs.ag-ui.com/introduction"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://docs.ag-ui.com/introduction",
  "note": "Overview lists a terminal client; AG-UI is an event stream, not a web-only renderer."
 },
 {
  "id": "thayn-me",
  "org_id": "thayn-me",
  "name": "thayn.me",
  "url": "https://thayn.me/.well-known/ai.txt",
  "type": "origin",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "thayn.me",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Serves Cardillo draft-car-ai-txt-wellknown-00 at `/.well-known/ai.txt` (`Spec-Version: 1.0`, `Site-Name: thayn.me`, `Training: deny`, `Scraping: allow`, `Indexing: allow`, `Caching: allow`, `Attribution: required`).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://thayn.me/.well-known/ai.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://thayn.me/.well-known/ai.txt",
  "note": "Serves Cardillo draft-car-ai-txt-wellknown-00 at `/.well-known/ai.txt` (`Spec-Version: 1.0`, `Site-Name: thayn.me`, `Training: deny`, `Scraping: allow`, `Indexing: allow`, `Caching: allow`, `Attribution: required`)."
 },
 {
  "id": "theatlantic-com-robots-txt",
  "org_id": "the-atlantic",
  "name": "The Atlantic",
  "url": "https://www.theatlantic.com/robots.txt",
  "type": "origin",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "The Atlantic",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Allows `GPTBot` and `OAI-SearchBot` (`Allow: /`), blocks `ClaudeBot` and `Google-Extended` (`Disallow: /`), and sets `Content-signal: search=yes, ai-input=no, ai-train=no`.",
    "full_detail_md": "Sets `Content-signal: search=yes, ai-input=no, ai-train=no` on `User-agent: Googlebot`, `User-agent: FacebookBot`, and `User-agent: DuckAssistBot`. Sets `Disallow: /` on `User-agent: Google-Extended`, `User-agent: ClaudeBot`, `User-agent: CCBot`, `User-agent: Applebot-Extended`, `User-agent: cohere-ai`, and `User-agent: MistralAI-User`, while allowing `User-agent: GPTBot` and `User-agent: OAI-SearchBot` (`Allow: /`) and restricting `User-agent: Claude-SearchBot` and `User-agent: PerplexityBot` to `Allow: /sponsored/`.",
    "facets": {
     "scope_host": "https://www.theatlantic.com/robots.txt",
     "policy_role": "Publisher robots.txt policy declaration",
     "published_rules": [
      {
       "tokens": [
        "GPTBot",
        "OAI-SearchBot"
       ],
       "directives": [
        "Allow: /"
       ]
      },
      {
       "tokens": [
        "Claude-SearchBot",
        "PerplexityBot"
       ],
       "directives": [
        "Allow: /sponsored/",
        "Disallow: /"
       ]
      },
      {
       "tokens": [
        "Google-Extended",
        "ClaudeBot",
        "CCBot",
        "Applebot-Extended",
        "cohere-ai",
        "MistralAI-User"
       ],
       "directives": [
        "Disallow: /"
       ]
      }
     ],
     "content_signals": "Content-signal: search=yes, ai-input=no, ai-train=no"
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "robots_txt",
     "marker": "Content-signal: search=yes, ai-input=no, ai-train=no"
    },
    "source_url": "https://www.theatlantic.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.theatlantic.com/robots.txt",
  "note": "Allows `GPTBot` and `OAI-SearchBot` (`Allow: /`), blocks `ClaudeBot` and `Google-Extended` (`Disallow: /`), and sets `Content-signal: search=yes, ai-input=no, ai-train=no`."
 },
 {
  "id": "they-said-so",
  "org_id": "they-said-so",
  "name": "They Said So",
  "url": "https://theysaidso.com",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment",
   "aipref-vocabulary"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "They Said So",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "robots.txt serves `Content-Usage: ai=n` in the `User-Agent: *` group, beside `Content-Signal: search=yes, ai-input=no, ai-train=no`, with the comment `# Source: https://robotstxt.com/ai`. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain",
     "attachment": "robots.txt",
     "content_usage": "Content-Usage: ai=n"
    },
    "source_url": "https://theysaidso.com/robots.txt"
   },
   {
    "protocol_id": "aipref-vocabulary",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "They Said So",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `Content-Usage: ai=n` in the `User-Agent: *` group, next to `Content-Signal: search=yes, ai-input=no, ai-train=no`. The file comment cites `https://robotstxt.com/ai`. `ai` is the AI Training label in `draft-ietf-aipref-vocab-01` Table 1 and is absent from `draft-ietf-aipref-vocab-08` Table 1.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "surface": "robots.txt",
     "content_usage": "ai=n"
    },
    "source_url": "https://theysaidso.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://theysaidso.com/robots.txt",
  "note": "robots.txt serves `Content-Usage: ai=n` in the `User-Agent: *` group, beside `Content-Signal: search=yes, ai-input=no, ai-train=no`, with the comment `# Source: https://robotstxt.com/ai`. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored."
 },
 {
  "id": "ticket-fairy",
  "org_id": "ticket-fairy",
  "name": "Ticket Fairy events and ticket checkout",
  "url": "https://www.ticketfairy.com/.well-known/agent-card.json",
  "type": "agent",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Ticket Fairy",
    "role": "Public A2A agent",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Live Agent Card binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.ticketfairy.com/agentic/a2a` with `search_events`, `ticket-checkout`, A2UI `v0.8`, and UCP.",
    "full_detail_md": "Ticket Fairy serves a live HTTP 200 Agent Card at https://www.ticketfairy.com/.well-known/agent-card.json (v`1.0.0`, checked 2026-10-30) binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.ticketfairy.com/agentic/a2a` with anonymous `search_events` (`SendMessage` with `A2A-Version: 1.0`) and authenticated `ticket-checkout` skills, declaring optional extensions for A2UI `v0.8` (`https://a2ui.org/a2a-extension/a2ui/v0.8`) and Universal Commerce Protocol (`https://ucp.dev/2026-08-25/specification/reference`, requiring `UCP-Agent`, `Content-Digest`, and RFC 9421 HTTP Message Signatures).",
    "facets": {
     "transport_bindings": "JSONRPC at https://www.ticketfairy.com/agentic/a2a (SendMessage with A2A-Version: 1.0; streaming: false)",
     "discovery_artifact": "GET https://www.ticketfairy.com/.well-known/agent-card.json (v1.0.0, A2A 1.0 card schema with A2UI v0.8 and UCP 2026-08-25 extensions)",
     "protocol_version": "1.0",
     "auth_schemes": "Anonymous for search_events; onboarded application with UCP-Agent, Content-Digest, and RFC 9421 HTTP Message Signatures for ticket-checkout",
     "verification_posture": "Live HTTP 200 Agent Card probe (checked 2026-10-30)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json; charset=UTF-8",
     "protocol_version": "1.0",
     "agent_version": "1.0.0"
    },
    "source_url": "https://www.ticketfairy.com/.well-known/agent-card.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.ticketfairy.com/.well-known/agent-card.json",
  "note": "Live Agent Card binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.ticketfairy.com/agentic/a2a` with `search_events`, `ticket-checkout`, A2UI `v0.8`, and UCP."
 },
 {
  "id": "tierion-boltwall",
  "org_id": "tierion",
  "name": "Tierion",
  "url": "https://github.com/Tierion/boltwall",
  "type": "sdk",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Tierion (boltwall)",
    "role": "Server middleware",
    "status": "Listed",
    "status_display": "Listed · as of 2023-04-26",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2023-04-26",
    "col4_md": "Express LSAT paywall middleware; repo pushed 2023-04-26.",
    "full_detail_md": "Boltwall is Express middleware for a Bitcoin Lightning paywall and authentication using LSATs, installed as app.use(boltwall()), and the L402 README lists it as Node.js middleware-based authentication using L402. The Tierion/boltwall repository was last pushed on 2023-04-26, so this row records that listing rather than a live challenge probe.",
    "facets": {
     "settlement_rail": "Bitcoin Lightning paywall using LSATs",
     "token_or_macaroon": "LSAT macaroon bearer credential",
     "headers_or_challenge": "Express middleware paywall via app.use(boltwall())",
     "sdk_or_endpoint": "Tierion/boltwall, listed in the L402 README; repository pushed 2023-04-26"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/Tierion/boltwall/master/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/Tierion/boltwall/master/README.md",
  "note": "Express LSAT paywall middleware; repo pushed 2023-04-26."
 },
 {
  "id": "tierion-lsat-js",
  "org_id": "tierion",
  "name": "Tierion",
  "url": "https://github.com/Tierion/lsat-js",
  "type": "sdk",
  "implements": [
   "l402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "l402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Tierion (lsat-js)",
    "role": "Client SDK",
    "status": "Listed",
    "status_display": "Listed · as of 2023-08-09",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2023-08-09",
    "col4_md": "JavaScript LSAT tools; last push 2023-08-09.",
    "full_detail_md": "lsat-js is a Node.js and TypeScript suite for LSAT credentials, and after the invoice is paid the caller adds the preimage. The repository was last pushed on 2023-08-09, and the L402 README lists it as a JavaScript utility library for L402 credentials.",
    "facets": {
     "settlement_rail": "Lightning invoice paid before the LSAT preimage is attached",
     "token_or_macaroon": "LSAT macaroon; caller adds the preimage after payment",
     "headers_or_challenge": "LSAT bearer-credential helpers for Node.js and TypeScript clients",
     "sdk_or_endpoint": "Tierion/lsat-js, pushed 2023-08-09, listed in the L402 README"
    },
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/Tierion/lsat-js/master/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/Tierion/lsat-js/master/README.md",
  "note": "JavaScript LSAT tools; last push 2023-08-09."
 },
 {
  "id": "tomevault-ai-catalog-reference",
  "org_id": "tomevault-ai-catalog-reference",
  "name": "TomeVault AI Catalog reference",
  "url": "https://raw.githubusercontent.com/tomevault-io/ai-catalog-reference/main/README.md",
  "type": "sdk",
  "implements": [
   "ai-catalog-well-known-file"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "TomeVault AI Catalog reference",
    "role": "Validator / Parser",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Python signer and verifier for Level 3 trust manifests: signed subject binding, `did:web` identity, an algorithm allowlist, freshness, substantive-member checks, and SSRF-safe fetches.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/tomevault-io/ai-catalog-reference/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://raw.githubusercontent.com/tomevault-io/ai-catalog-reference/main/README.md",
  "note": "Python signer and verifier for Level 3 trust manifests: signed subject binding, `did:web` identity, an algorithm allowlist, freshness, substantive-member checks, and SSRF-safe fetches."
 },
 {
  "id": "triton-digital",
  "org_id": "triton-digital",
  "name": "Triton Digital",
  "url": "https://adcp-salesagent.api.tritondigital.com/mcp",
  "type": "agent",
  "implements": [
   "adcp"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "adcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Triton Digital",
    "role": "Sales agent",
    "status": "Listed",
    "status_display": "Listed · as of 2026-06-19",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-19",
    "col4_md": "Talpa's adagents.json lists `https://adcp-salesagent.api.tritondigital.com/mcp` under `authorized_agents`, `authorized_for` Talpa audio and podcast properties, with `authorization_type` `property_tags` and `delegation_type` `direct`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://kijk.nl/.well-known/adagents.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://kijk.nl/.well-known/adagents.json",
  "note": "Talpa's adagents.json lists `https://adcp-salesagent.api.tritondigital.com/mcp` under `authorized_agents`, `authorized_for` Talpa audio and podcast properties, with `authorization_type` `property_tags` and `delegation_type` `direct`."
 },
 {
  "id": "tuist",
  "org_id": "tuist",
  "name": "Tuist",
  "url": "https://tuist.dev/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Tuist",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://tuist.dev/auth.md implements auth.md v0.6.0 for the MCP server at https://tuist.dev/mcp. Registration returns a signed identity assertion, not an access token, and the agent exchanges that assertion at the discovered token endpoint. Authorization-server metadata advertises identity_endpoint https://tuist.dev/agent/identity and identity_types_supported anonymous, identity_assertion, and service_auth, plus /agent/identity/claim and /agent/event/notify.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://tuist.dev/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://tuist.dev/auth.md",
  "note": "https://tuist.dev/auth.md implements auth.md v0.6.0 for the MCP server at https://tuist.dev/mcp. Registration returns a signed identity assertion, not an access token, and the agent exchanges that assertion at the discovered token endpoint. Authorization-server metadata advertises identity_endpoint https://tuist.dev/agent/identity and identity_types_supported anonymous, identity_assertion, and ser"
 },
 {
  "id": "uber",
  "org_id": "uber",
  "name": "Uber SPIRE deployment",
  "url": "https://www.uber.com/us/en/blog/our-journey-adopting-spiffe-spire/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Uber",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2023-11-09",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2023-11-09",
    "col4_md": "Uses SPIRE for workload identity across GCP, OCI, AWS, and on-premise since mid-2018.",
    "full_detail_md": "On November 9, 2023, Uber wrote that it uses SPIRE to provide identity to workloads running in multiple clouds (GCP, OCI, AWS, on-premise) for stateless services, stateful storage, batch and streaming jobs, CI jobs, workflow executions, and infrastructure services. Uber has worked with the open source community since the early stages of the project in mid-2018.",
    "facets": {
     "svid_or_bundle_format": "SPIRE-issued workload identity. The post does not split X.509 SVIDs from JWT SVIDs.",
     "api_or_federation_surface": "SPIRE providing identity to workloads in GCP, OCI, AWS, and on-premise.",
     "attestation_or_trust_domain": "Covers stateless services, stateful storage, batch and streaming jobs, CI jobs, workflow executions, and infrastructure services. Community work since mid-2018.",
     "verification_posture": "Uber engineering post dated November 9, 2023 describing production SPIRE use."
    },
    "telemetry": null,
    "source_url": "https://www.uber.com/us/en/blog/our-journey-adopting-spiffe-spire/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.uber.com/us/en/blog/our-journey-adopting-spiffe-spire/",
  "note": "Uses SPIRE for workload identity across GCP, OCI, AWS, and on-premise since mid-2018."
 },
 {
  "id": "ubuntu-changelogs",
  "org_id": "ubuntu-changelogs",
  "name": "Ubuntu Changelogs",
  "url": "https://changelogs.ubuntu.com",
  "type": "origin",
  "implements": [
   "aipref-content-usage-attachment",
   "aipref-vocabulary"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "aipref-content-usage-attachment",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Ubuntu Changelogs",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "robots.txt serves `Content-Usage: ai=n` in the `User-Agent: *` group, with the comment `# Source: https://robotstxt.com/ai`. This file has no Content-Signal line. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "attachment": "robots.txt",
     "content_usage": "Content-Usage: ai=n"
    },
    "source_url": "https://changelogs.ubuntu.com/robots.txt"
   },
   {
    "protocol_id": "aipref-vocabulary",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Ubuntu Changelogs",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Serves `Content-Usage: ai=n` in the `User-Agent: *` group. The file comment cites `https://robotstxt.com/ai`. The response names `nginx/1.14.0 (Ubuntu)`. `ai` is the AI Training label in `draft-ietf-aipref-vocab-01` Table 1 and is absent from `draft-ietf-aipref-vocab-08` Table 1.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "surface": "robots.txt",
     "content_usage": "ai=n",
     "server": "nginx/1.14.0 (Ubuntu)"
    },
    "source_url": "https://changelogs.ubuntu.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://changelogs.ubuntu.com/robots.txt",
  "note": "robots.txt serves `Content-Usage: ai=n` in the `User-Agent: *` group, with the comment `# Source: https://robotstxt.com/ai`. This file has no Content-Signal line. The label ai is not in vocab-08 Table 1 (`train-ai`, `ai-use`, `search`); any unknown labels MUST be ignored."
 },
 {
  "id": "ucp-ap2-mandates",
  "org_id": "ucp",
  "name": "UCP AP2 Mandates Extension",
  "url": "https://ucp.dev/latest/specification/payment/extensions/ap2-mandates/",
  "type": "origin",
  "implements": [
   "ap2"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ap2",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Universal Commerce Protocol (UCP) AP2 Mandates Extension",
    "role": "Protocol extension",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-25",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-25",
    "col4_md": "Businesses declare support by adding `dev.ucp.common.payment.ap2_mandate` to their capabilities list in `/.well-known/ucp`. When that capability is in the intersection, the business MUST include `ap2.merchant_authorization` on checkout responses and MUST NOT accept `complete_checkout` without `ap2.checkout_mandate`. Mandates are SD-JWT credentials; the extension places `checkout_mandate` at `ap2.checkout_mandate` and `payment_mandate` at `payment.instruments[*].credential.token`. Allbirds' `/.well-known/ucp` (version 2026-08-25) lists `dev.ucp.shopping.checkout`, and IKEA's `/.well-known/ucp` (version 2026-04-08, with 2026-08-25 under `supported_versions`) lists `dev.ucp.shopping.checkout` and `dev.ucp.shopping.fulfillment`; neither declares `dev.ucp.common.payment.ap2_mandate`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://ucp.dev/latest/specification/payment/extensions/ap2-mandates/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://ucp.dev/latest/specification/payment/extensions/ap2-mandates/",
  "note": "Businesses declare support by adding `dev.ucp.common.payment.ap2_mandate` to their capabilities list in `/.well-known/ucp`. When that capability is in the intersection, the business MUST include `ap2.merchant_authorization` on checkout responses and MUST NOT accept `complete_checkout` without `ap2.checkout_mandate`. Mandates are SD-JWT credentials; the extension places `checkout_mandate` at `ap2.c"
 },
 {
  "id": "ucp-official-sdks",
  "org_id": "universal-commerce-protocol",
  "name": "Universal Commerce Protocol",
  "url": "https://github.com/Universal-Commerce-Protocol",
  "type": "sdk",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Universal-Commerce-Protocol Official SDKs",
    "role": "Client SDK & conformance suite",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Official `python-sdk`, `js-sdk`, and `conformance` repositories.",
    "full_detail_md": "The organization repository index lists python-sdk (The official Python SDK for UCP), js-sdk (The official JavaScript SDK for UCP), and conformance (Conformance Tests for UCP). This grade uses that index of official repositories, not a floating main-branch source file and not a live merchant profile.",
    "facets": {
     "commerce_surface": "Official client SDK and conformance repositories",
     "payment_handlers_or_rail": "SDK and conformance suite for UCP; handler choice is per business profile",
     "transport_bindings": "Client libraries, not a probed /.well-known/ucp transport",
     "spec_version": "Organization repository index checked 2026-10-30; not a release-tag pin and not a Live registry grade"
    },
    "telemetry": null,
    "source_url": "https://api.github.com/orgs/Universal-Commerce-Protocol/repos?per_page=100"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://api.github.com/orgs/Universal-Commerce-Protocol/repos?per_page=100",
  "note": "Official `python-sdk`, `js-sdk`, and `conformance` repositories."
 },
 {
  "id": "ujex",
  "org_id": "ujex",
  "name": "Ujex (ujex-compliance-callback)",
  "url": "https://pypi.org/pypi/ujex-compliance-callback/json",
  "type": "sdk",
  "implements": [
   "agent-audit-trail"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "agent-audit-trail",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Ujex (ujex-compliance-callback)",
    "role": "Audit emitter",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-06-18",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-18",
    "col4_md": "PyPI ujex-compliance-callback 0.1.1, uploaded 2026-06-18 by axysar. Drop-in callbacks for LangChain, LangGraph, CrewAI, AutoGen, and PydanticAI stream events into a hash-chained ledger aimed at draft-sharif-agent-audit-trail-00. The current draft revision is -09.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://pypi.org/pypi/ujex-compliance-callback/json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://pypi.org/pypi/ujex-compliance-callback/json",
  "note": "PyPI ujex-compliance-callback 0.1.1, uploaded 2026-06-18 by axysar. Drop-in callbacks for LangChain, LangGraph, CrewAI, AutoGen, and PydanticAI stream events into a hash-chained ledger aimed at draft-sharif-agent-audit-trail-00. The current draft revision is -09."
 },
 {
  "id": "upstash",
  "org_id": "upstash",
  "name": "Upstash (Context7)",
  "url": "https://mcp.context7.com/mcp/server-card",
  "type": "authority",
  "implements": [
   "mcp-server-cards"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "mcp-server-cards",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Upstash (Context7)",
    "role": "Server Card publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GET https://mcp.context7.com/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://mcp.context7.com/mcp, card name io.github.upstash/context7. https://context7.com/.well-known/ai-catalog.json (status 200, application/ai-catalog+json) links to this card. The Context7 README tells clients to use https://mcp.context7.com/mcp.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://mcp.context7.com/mcp/server-card"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://mcp.context7.com/mcp/server-card",
  "note": "GET https://mcp.context7.com/mcp/server-card returned status 200, Content-Type application/mcp-server-card+json, $schema set to the v1 schema URL, remotes entry https://mcp.context7.com/mcp, card name io.github.upstash/context7. https://context7.com/.well-known/ai-catalog.json (status 200, application/ai-catalog+json) links to this card. The Context7 README tells clients to use https://mcp.context"
 },
 {
  "id": "vawe-awesome-skill-directories",
  "org_id": "vawe-hq",
  "name": "Awesome Agent Skills Directories",
  "url": "https://github.com/vawe-hq/awesome-agent-skills-directories/blob/main/README.md",
  "type": "authority",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Awesome Agent Skills Directories",
    "role": "Index of skill directories",
    "status": "Listed",
    "status_display": "Listed · as of 2026-10-29",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-10-29",
    "col4_md": "Directory index checked `2026-10-29`; Smithery at `25,346` (self-reported directory listing counter).",
    "full_detail_md": "The list covers registries, marketplaces, directories, and awesome-lists. It records Smithery at 25,346 skills, lists VoltAgent/awesome-agent-skills, and notes vercel-labs/skills as the npx skills installer that feeds skills.sh.",
    "facets": {
     "transport_or_packaging": "Markdown index of directories",
     "manifest_or_entry": "One table row per directory, checked 2026-10-29",
     "execution_or_sandbox": "Submission notes only; the list does not host skill files",
     "verification_posture": "Every row checked 2026-10-29"
    },
    "telemetry": null,
    "source_url": "https://github.com/vawe-hq/awesome-agent-skills-directories/blob/main/README.md"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://github.com/vawe-hq/awesome-agent-skills-directories/blob/main/README.md",
  "note": "Directory index checked `2026-10-29`; Smithery at `25,346` (self-reported directory listing counter)."
 },
 {
  "id": "veezoo",
  "org_id": "veezoo",
  "name": "Veezoo",
  "url": "https://www.veezoo.com/apache-ossie",
  "type": "origin",
  "implements": [
   "osi"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "osi",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Veezoo",
    "role": "BI / Query engine",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "Veezoo reads Apache Ossie documents as a native source for its Knowledge Graph, the semantic layer behind its agentic analytics. Page returned HTTP 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.veezoo.com/apache-ossie"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.veezoo.com/apache-ossie",
  "note": "Veezoo reads Apache Ossie documents as a native source for its Knowledge Graph, the semantic layer behind its agentic analytics. Page returned HTTP 200 on 2026-10-29."
 },
 {
  "id": "vercel",
  "org_id": "vercel",
  "name": "Vercel",
  "url": "https://vercel.com/llms.txt",
  "type": "origin",
  "implements": [
   "ai-catalog-well-known-file",
   "api-catalog-rfc9727",
   "http-message-signatures",
   "llms-txt",
   "webbotauth"
  ],
  "archetypes": [
   "identity_auth_crypto",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Vercel",
    "role": "Product site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Serves `https://vercel.com/llms.txt` as `text/plain` (`# Vercel`), with an Optional section linking `/.well-known/ai-catalog.json`.",
    "full_detail_md": "Serves `https://vercel.com/llms.txt` as `text/plain; charset=utf-8` (5,397 bytes, fetched 2026-11-04). The file opens `# Vercel` with `## When to use Vercel` and `## How agents should use Vercel` guidance, links `https://vercel.com/openapi.json` and Vercel MCP, and includes an `## Optional` section pointing to `https://vercel.com/.well-known/ai-catalog.json`, `taxonomy.json`, and `graph.json`.",
    "facets": {
     "artifact_path": "https://vercel.com/llms.txt",
     "companion_files": "https://vercel.com/openapi.json; https://vercel.com/.well-known/ai-catalog.json; taxonomy.json; graph.json",
     "content_type_or_bytes": "text/plain; charset=utf-8 (5,397 bytes)",
     "generator_or_consumer_mode": "Origin platform index linking OpenAPI, MCP, and ai-catalog.json"
    },
    "telemetry": {
     "artifact_kind": "llms_txt",
     "http_status": 200,
     "content_type": "text/plain; charset=utf-8",
     "marker": "# Vercel"
    },
    "source_url": "https://vercel.com/llms.txt"
   },
   {
    "protocol_id": "webbotauth",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Vercel",
    "role": "CDN / WAF verifier",
    "status": "Supported",
    "status_display": "Supported · as of 2025-08-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-08-12",
    "col4_md": "Vercel Bot Verification validates Web Bot Auth HTTP Message Signatures and allows signed ChatGPT operator requests.",
    "full_detail_md": "Vercel Bot Protection verifies HTTP Message Signatures using the Web Bot Auth protocol to authenticate automated traffic from dynamic and distributed sources, allowing signed requests such as the ChatGPT operator (published 2025-08-12).",
    "facets": {
     "signature_or_key_format": "HTTP Message Signatures (Web Bot Auth)",
     "directory_or_header": "Bot Protection HTTP Message Signatures verification",
     "signing_algorithm": "HTTP Message Signatures",
     "verification_role": "CDN / WAF verifier (allows verified Web Bot Auth traffic such as ChatGPT operator)"
    },
    "telemetry": null,
    "source_url": "https://vercel.com/changelog/vercels-bot-verification-now-supports-web-bot-auth"
   },
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Vercel",
    "role": "CDN / WAF verifier (Web Bot Auth profile)",
    "status": "Partial",
    "status_display": "Partial · as of 2025-08-12",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-08-12",
    "col4_md": "Bot Protection verifies HTTP Message Signatures under the Web Bot Auth profile, allowing signed ChatGPT operator requests.",
    "full_detail_md": "Vercel Bot Protection validates HTTP Message Signatures scoped to the Web Bot Auth protocol to authenticate automated traffic from dynamic and distributed sources, allowing signed requests such as the OpenAI ChatGPT operator (published 2025-08-12).",
    "facets": {
     "profile_or_spec_target": "Web Bot Auth profile of HTTP Message Signatures (RFC 9421)",
     "signature_fields": "Web Bot Auth HTTP Message Signatures headers",
     "algorithms_or_keys": "Public-key verification for dynamic and distributed automated traffic",
     "verification_posture": "CDN / WAF verifier (Vercel Bot Protection; allows signed ChatGPT operator requests)"
    },
    "telemetry": null,
    "source_url": "https://vercel.com/changelog/vercels-bot-verification-now-supports-web-bot-auth"
   },
   {
    "protocol_id": "ai-catalog-well-known-file",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Vercel",
    "role": "Publisher",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Level 2 catalog, `Content-Type: application/ai-catalog+json`, `displayName` Vercel, `documentationUrl` `https://vercel.com/docs/agent-resources`, indexing MCP OAuth metadata, the Vercel MCP server, and the documentation graph.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://vercel.com/.well-known/ai-catalog.json"
   },
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Vercel",
    "role": "Cloud platform API catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "Profiled `application/linkset+json` with `item` `https://api.vercel.com` and `rel=\"api-catalog\"`.",
    "full_detail_md": "On 2026-11-04, `https://vercel.com/.well-known/api-catalog` returned HTTP 200 (`content-length: 405`) as `application/linkset+json` with profile `https://www.rfc-editor.org/info/rfc9727` and `Link: </.well-known/api-catalog>; rel=\"api-catalog\"`. The `item` href is `https://api.vercel.com`, with `service-desc` `https://openapi.vercel.sh/` (`application/json`), `service-doc` `https://vercel.com/docs/rest-api`, and `status` `https://www.vercel-status.com/api/v2/status.json`.",
    "facets": {
     "well_known_endpoint": "https://vercel.com/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_relations": "item (https://api.vercel.com); service-desc (https://openapi.vercel.sh/); service-doc; status",
     "http_or_link_header": "HTTP 200; Link: </.well-known/api-catalog>; rel=\"api-catalog\""
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; profile=\"https://www.rfc-editor.org/info/rfc9727\"",
     "link_header_rel_api_catalog": true,
     "has_item_array": true
    },
    "source_url": "https://vercel.com/.well-known/api-catalog"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://vercel.com/llms.txt",
  "note": "Serves `https://vercel.com/llms.txt` as `text/plain` (`# Vercel`), with an Optional section linking `/.well-known/ai-catalog.json`."
 },
 {
  "id": "vercel-agent-readability",
  "org_id": "vercel-agent-readability",
  "name": "@vercel/agent-readability",
  "url": "https://registry.npmjs.org/@vercel/agent-readability",
  "type": "sdk",
  "implements": [
   "vercel-agent-readability"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "vercel-agent-readability",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "@vercel/agent-readability",
    "role": "CDN / Edge",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-04",
    "col4_md": "npm package v0.7.0 (published 2026-09-04; v0.1.0 on 2026-03-30) installs Next.js, SvelteKit, Nuxt, and Vercel Edge routing middleware. Agent detection uses known user-agent patterns (30+ agents, including ClaudeBot, GPTBot, Cursor, and Perplexity), a `Signature-Agent` header for the ChatGPT agent (RFC 9421), and a `sec-fetch-mode` heuristic.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@vercel/agent-readability"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@vercel/agent-readability",
  "note": "npm package v0.7.0 (published 2026-09-04; v0.1.0 on 2026-03-30) installs Next.js, SvelteKit, Nuxt, and Vercel Edge routing middleware. Agent detection uses known user-agent patterns (30+ agents, including ClaudeBot, GPTBot, Cursor, and Perplexity), a `Signature-Agent` header for the ChatGPT agent (RFC 9421), and a `sec-fetch-mode` heuristic."
 },
 {
  "id": "vercel-agent-readability-audit",
  "org_id": "vercel-agent-readability-audit",
  "name": "@vercel/agent-readability audit",
  "url": "https://registry.npmjs.org/@vercel/agent-readability",
  "type": "sdk",
  "implements": [
   "vercel-agent-readability"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "vercel-agent-readability",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "@vercel/agent-readability audit",
    "role": "Validator / CLI",
    "status": "Supported",
    "status_display": "Supported · as of 2026-09-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-04",
    "col4_md": "npx @vercel/agent-readability audit `<url>` runs 25 weighted checks in 4 categories and returns a score from 0 to 100 (package v0.7.0, 2026-09-04).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://registry.npmjs.org/@vercel/agent-readability"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://registry.npmjs.org/@vercel/agent-readability",
  "note": "npx @vercel/agent-readability audit `<url>` runs 25 weighted checks in 4 categories and returns a score from 0 to 100 (package v0.7.0, 2026-09-04)."
 },
 {
  "id": "vercel-ai-gateway",
  "org_id": "vercel",
  "name": "Vercel AI Gateway",
  "url": "https://ai-gateway.vercel.sh/v1/responses",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Vercel AI Gateway",
    "role": "Model router",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-15",
    "col4_md": "Day 0 launch partner; AI SDK example URL `https://ai-gateway.vercel.sh/v1/responses`.",
    "full_detail_md": "The 15 Jan 2026 Vercel changelog calls Vercel AI Gateway a day 0 launch partner for the OpenResponses API, which it describes as a unified interface for text generation, streaming, and tool calling. The AI SDK documents createOpenResponses with url https://ai-gateway.vercel.sh/v1/responses, and The New Stack says Vercel AI Gateway already implements the spec.",
    "facets": {
     "endpoint_or_route": "https://ai-gateway.vercel.sh/v1/responses",
     "streaming_or_items": "Changelog names streaming among OpenResponses interactions",
     "tool_or_state_model": "Changelog names tool calling among OpenResponses interactions",
     "sdk_or_version": "Day 0 launch partner, changelog 15 Jan 2026; createOpenResponses example"
    },
    "telemetry": null,
    "source_url": "https://vercel.com/changelog/openresponses-api-now-supported-on-vercel-ai-gateway"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://vercel.com/changelog/openresponses-api-now-supported-on-vercel-ai-gateway",
  "note": "Day 0 launch partner; AI SDK example URL `https://ai-gateway.vercel.sh/v1/responses`."
 },
 {
  "id": "vercel-ai-sdk",
  "org_id": "vercel",
  "name": "Vercel AI SDK (@ai-sdk/open-responses)",
  "url": "https://ai-sdk.dev/providers/ai-sdk-providers/open-responses",
  "type": "sdk",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Vercel AI SDK",
    "role": "Client SDK",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "`createOpenResponses` from `@ai-sdk/open-responses` for `generateText` and `streamText`.",
    "full_detail_md": "The Open Responses provider connects AI SDK Core to language model servers that implement an Open Responses-compatible POST endpoint. Callers import createOpenResponses from @ai-sdk/open-responses and use generateText and streamText, and the gateway example sets the url to https://ai-gateway.vercel.sh/v1/responses.",
    "facets": {
     "endpoint_or_route": "Open Responses-compatible POST endpoint; gateway example https://ai-gateway.vercel.sh/v1/responses",
     "streaming_or_items": "generateText and streamText",
     "tool_or_state_model": "AI SDK Core provider for servers that implement the Open Responses POST endpoint",
     "sdk_or_version": "@ai-sdk/open-responses createOpenResponses; the page prints no package version"
    },
    "telemetry": null,
    "source_url": "https://ai-sdk.dev/providers/ai-sdk-providers/open-responses"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://ai-sdk.dev/providers/ai-sdk-providers/open-responses",
  "note": "`createOpenResponses` from `@ai-sdk/open-responses` for `generateText` and `streamText`."
 },
 {
  "id": "vercel-com-well-known-agent-skills-index-json",
  "org_id": "vercel",
  "name": "Vercel agent skills",
  "url": "https://vercel.com/.well-known/agent-skills/index.json",
  "type": "origin",
  "implements": [
   "anthropic-agent-skills-format"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "anthropic-agent-skills-format",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Vercel",
    "role": "Well-known skill publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200 `application/json` at `/.well-known/agent-skills/index.json` (`0.2.0` schema) listing 9 skills across `skill-md` (`deploy-to-vercel`) and `archive` entries.",
    "full_detail_md": "Vercel serves HTTP 200 `application/json` at `/.well-known/agent-skills/index.json` using `$schema` `https://schemas.agentskills.io/discovery/0.2.0/schema.json`, indexing 9 skills that mix single-file `skill-md` entries (such as `deploy-to-vercel` and `vercel-cli-with-tokens`) and multi-file `archive` bundles (such as `writing-guidelines`), each with a `sha256:` `digest`.",
    "facets": {
     "transport_or_packaging": "HTTPS well-known index (/.well-known/agent-skills/index.json) with skill-md and archive artifacts",
     "manifest_or_entry": "Discovery v0.2.0 schema (https://schemas.agentskills.io/discovery/0.2.0/schema.json) with 9 skill entries",
     "execution_or_sandbox": "Single-file Markdown (skill-md) and packaged archives verified by sha256 digest",
     "verification_posture": "Live HTTP 200 probe checked 2026-10-30"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "skill_count": 9,
     "schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json"
    },
    "source_url": "https://vercel.com/.well-known/agent-skills/index.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://vercel.com/.well-known/agent-skills/index.json",
  "note": "HTTP 200 `application/json` at `/.well-known/agent-skills/index.json` (`0.2.0` schema) listing 9 skills across `skill-md` (`deploy-to-vercel`) and `archive` entries."
 },
 {
  "id": "vercel-documentation",
  "org_id": "vercel-documentation",
  "name": "Vercel documentation",
  "url": "https://vercel.com/docs/agent-resources.md",
  "type": "origin",
  "implements": [
   "vercel-agent-readability"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "vercel-agent-readability",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Vercel documentation",
    "role": "Docs platform",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "`https://vercel.com/docs/agent-resources.md` returned status 200 on 2026-10-29. A docs URL returns HTML to a browser and `text/markdown` when the client prefers Markdown or when Vercel detects an AI agent; responses set `Vary: Accept`. The same site serves `.md` twins, `.graph.md` cross-link maps, `/docs/sitemap.md`, `/.well-known/ai-catalog.json`, and `/.well-known/api-catalog`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://vercel.com/docs/agent-resources.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://vercel.com/docs/agent-resources.md",
  "note": "`https://vercel.com/docs/agent-resources.md` returned status 200 on 2026-10-29. A docs URL returns HTML to a browser and `text/markdown` when the client prefers Markdown or when Vercel detects an AI agent; responses set `Vary: Accept`. The same site serves `.md` twins, `.graph.md` cross-link maps, `/docs/sitemap.md`, `/.well-known/ai-catalog.json`, and `/.well-known/api-catalog`."
 },
 {
  "id": "vercel-mcp-cimd",
  "org_id": "vercel",
  "name": "Vercel MCP",
  "url": "https://mcp.vercel.com",
  "type": "authority",
  "implements": [
   "oauth-cimd",
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Vercel",
    "role": "Protected resource",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`resource` `https://mcp.vercel.com/`, `resource_name` `Vercel MCP`, `authorization_servers` `https://vercel.com`, `scopes_supported` `openid`. Any MCP client can connect by publishing a Client ID Metadata Document and using that document's HTTPS URL as its OAuth `client_id`, without a prior Vercel review of the client.",
    "full_detail_md": "GET https://mcp.vercel.com/.well-known/oauth-protected-resource returned HTTP 200 `application/json` with `access-control-allow-origin` `*`. `resource` is `https://mcp.vercel.com/` and `resource_name` is `Vercel MCP`. `authorization_servers` is `https://vercel.com`. `scopes_supported` is `openid`. Checked 2026-11-03. The 2 Nov 2026 changelog says any MCP client can ask to connect to Vercel MCP. The user still logs in and approves each connection, but the client no longer has to be reviewed by Vercel first. Previously, Vercel reviewed and allowlisted each client and its redirect URIs by hand. A client publishes a Client ID Metadata Document (CIMD) and uses that file's HTTPS URL as its OAuth client_id. Apps already registered with Vercel are unchanged.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.vercel.com/.well-known/oauth-protected-resource (resource https://mcp.vercel.com/; resource_name Vercel MCP; authorization_servers https://vercel.com; scopes_supported openid)",
     "registration_or_client_id_modes": "Protected-resource document does not declare a client registration mode. The 2 Nov 2026 changelog says Vercel MCP accepts a Client ID Metadata Document and uses that document's HTTPS URL as the OAuth client_id, replacing hand allowlisting of clients and redirect URIs. Apps already registered with Vercel are unchanged.",
     "pkce_or_grant_types": "Not declared in this protected-resource document",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03); access-control-allow-origin *"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-protected-resource",
     "resource": "https://mcp.vercel.com/"
    },
    "source_url": "https://mcp.vercel.com/.well-known/oauth-protected-resource"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Vercel MCP",
    "role": "MCP authorization server",
    "status": "Supported",
    "status_display": "Supported · checked 2026-11-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Accepts a CIMD: a JSON file on the client's own domain, with that file's HTTPS URL used as the OAuth `client_id`.",
    "full_detail_md": "The Vercel changelog says that to connect, a client publishes a Client ID Metadata Document, a JSON file on its own domain, and uses that file's HTTPS URL as its OAuth `client_id`. It says this follows the MCP authorization spec, which now recommends CIMD over Dynamic Client Registration.",
    "facets": {
     "metadata_flag_or_profile": "CIMD JSON on the client domain; HTTPS URL used as client_id",
     "auth_method_or_pkce": "The changelog does not name a PKCE method",
     "uri_or_ssrf_rules": "The client_id is the HTTPS URL of the client's own JSON document",
     "draft_or_spec_version": "Follows the MCP authorization spec recommendation of CIMD over Dynamic Client Registration; no draft number is named"
    },
    "telemetry": null,
    "source_url": "https://vercel.com/changelog/vercel-mcp-now-supports-client-id-metadata-documents"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.vercel.com/.well-known/oauth-protected-resource",
  "note": "`resource` `https://mcp.vercel.com/`, `resource_name` `Vercel MCP`, `authorization_servers` `https://vercel.com`, `scopes_supported` `openid`. Any MCP client can connect by publishing a Client ID Metadata Document and using that document's HTTPS URL as its OAuth `client_id`, without a prior Vercel review of the client."
 },
 {
  "id": "vercel-x402-mcp",
  "org_id": "vercel",
  "name": "Vercel x402-mcp",
  "url": "https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools",
  "type": "sdk",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Vercel x402-mcp",
    "role": "SDK integration",
    "status": "Supported",
    "status_display": "Supported · as of 2025-09-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-09-12",
    "col4_md": "Integrates x402 payments into MCP servers and Vercel AI SDK alongside `x402-fetch` and `x402-next` middleware.",
    "full_detail_md": "Announced on September 12, 2025, Vercel's `x402-mcp` integrates x402 payments with Model Context Protocol (MCP) servers and the Vercel AI SDK, pairing with `wrapFetchWithPayment` from `x402-fetch` on the client and `paymentMiddleware` from `x402-next` on protected API routes.",
    "facets": {
     "settlement_rail": "x402 HTTP 402 programmatic payments for MCP tools and Next.js routes",
     "supported_assets": "x402-supported assets (e.g., USD-denominated route pricing)",
     "chains_or_networks": "x402-supported payment networks",
     "headers_or_methods": "`x402-mcp` MCP tool integration, `x402-fetch` (`wrapFetchWithPayment`), and `x402-next` (`paymentMiddleware`)"
    },
    "telemetry": null,
    "source_url": "https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools",
  "note": "Integrates x402 payments into MCP servers and Vercel AI SDK alongside `x402-fetch` and `x402-next` middleware."
 },
 {
  "id": "via-operator-console",
  "org_id": "via",
  "name": "Via Operator Console",
  "url": "https://ridewithvia.com/resources/agent-user-interaction-protocol-when-the-frontend-got-an-ai-protocol",
  "type": "harness",
  "implements": [
   "ag-ui"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "ag-ui",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Via Operator Console",
    "role": "Internal host",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-01-07",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-07",
    "col4_md": "Via backoffice experiment uses front-end tool calls plus `STATE_SNAPSHOT` and `STATE_DELTA`.",
    "full_detail_md": "Roi Dannon's January 7, 2026 note describes a Via experiment: a specialized chatbot assistant for the backoffice rider management system, using Front-end Tool Calls for web app navigation and Streaming Chat. The walkthrough names `STATE_SNAPSHOT` and `STATE_DELTA`.",
    "facets": {
     "transport": "Not named beyond streaming chat",
     "event_or_state_model": "STATE_SNAPSHOT and STATE_DELTA, plus front-end tool calls",
     "integration_role": "Internal backoffice host experiment",
     "sdk_or_package": "Not named (Via operator-console experiment)"
    },
    "telemetry": null,
    "source_url": "https://ridewithvia.com/resources/agent-user-interaction-protocol-when-the-frontend-got-an-ai-protocol"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://ridewithvia.com/resources/agent-user-interaction-protocol-when-the-frontend-got-an-ai-protocol",
  "note": "Via backoffice experiment uses front-end tool calls plus `STATE_SNAPSHOT` and `STATE_DELTA`."
 },
 {
  "id": "virtuals-acp-cli",
  "org_id": "virtuals-acp-cli",
  "name": "Virtuals ACP CLI (@virtuals-protocol/acp-cli)",
  "url": "https://os.virtuals.io/acp/overview",
  "type": "sdk",
  "implements": [
   "erc-8183"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8183",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Virtuals ACP CLI (`@virtuals-protocol/acp-cli`)",
    "role": "Client CLI (Co-author)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-31",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "CLI (v1.0.40 on npm) for shell-based agents, scripted workflows, and human-operated ERC-8183 job management on Base",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://os.virtuals.io/acp/overview"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://os.virtuals.io/acp/overview",
  "note": "CLI (v1.0.40 on npm) for shell-based agents, scripted workflows, and human-operated ERC-8183 job management on Base"
 },
 {
  "id": "virtuals-acp-sdk",
  "org_id": "virtuals-acp-sdk",
  "name": "Virtuals ACP SDK (@virtuals-protocol/acp-node-v2)",
  "url": "https://os.virtuals.io/acp/overview",
  "type": "sdk",
  "implements": [
   "erc-8183"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8183",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_b",
    "actor": "Virtuals ACP SDK (`@virtuals-protocol/acp-node-v2`)",
    "role": "Client SDK (Co-author)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-31",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": null,
    "col4_md": "Node.js SDK (v0.1.15 on npm) for programmatic agents and LLM-driven automation interacting with Virtuals' ERC-8183 escrow contracts on Base",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://os.virtuals.io/acp/overview"
   }
  ],
  "observed": "2026-10-31",
  "date_basis": "recorded",
  "source": "https://os.virtuals.io/acp/overview",
  "note": "Node.js SDK (v0.1.15 on npm) for programmatic agents and LLM-driven automation interacting with Virtuals' ERC-8183 escrow contracts on Base"
 },
 {
  "id": "virtuals-protocol",
  "org_id": "virtuals-protocol",
  "name": "Virtuals Protocol",
  "url": "https://whitepaper.virtuals.io/acp/acp-changelogs",
  "type": "authority",
  "implements": [
   "erc-8004",
   "erc-8183"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "erc-8004",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Virtuals Protocol",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2026-02-01",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02-01",
    "col4_md": "Since 01 Feb 2026, graduated ACP agents auto-register and store reviews on-chain.",
    "full_detail_md": "Virtuals Protocol's ACP changelog dated 01 Feb 2026 says ERC-8004 support is fully enabled for agents that completed ACP registration: every graduated agent is automatically registered on ERC-8004, and reviews and ratings are written on-chain under that agent identity.",
    "facets": {
     "registry_or_contract": "Graduated ACP agents are automatically registered on the ERC-8004 identity registry",
     "chains_or_networks": "On-chain ERC-8004 identity; the ACP changelog does not name a chain id",
     "standards_profile": "ERC-8004 identity with reviews and ratings written under that agent identity",
     "sdk_or_deployment": "ACP release dated 01 Feb 2026, enabled after the ACP agent registration process"
    },
    "telemetry": null,
    "source_url": "https://whitepaper.virtuals.io/acp/acp-changelogs"
   },
   {
    "protocol_id": "erc-8183",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Virtuals Protocol (`AgenticCommerceV3`)",
    "role": "Escrow platform & settlement contract (Co-author)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-31",
    "as_of": "2026-10-29",
    "col4_md": "EIP-20 token escrow & evaluator attestation contract on Base (`0x238E541BfefD82238730D00a2208E5497F1832E0` proxy to AgenticCommerceV3); 6-state job machine (Open → Funded → Submitted → Completed/Rejected/Expired), 7,630 mainnet txns as of 2026-10-29",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://os.virtuals.io/acp/overview"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://whitepaper.virtuals.io/acp/acp-changelogs",
  "note": "Since 01 Feb 2026, graduated ACP agents auto-register and store reviews on-chain."
 },
 {
  "id": "visa",
  "org_id": "visa",
  "name": "Visa",
  "url": "https://www.visa.com",
  "type": "authority",
  "implements": [
   "mpp",
   "tap",
   "ucp"
  ],
  "archetypes": [
   "identity_auth_crypto",
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Visa",
    "role": "Payment network (endorser)",
    "status": "Listed",
    "status_display": "Listed · as of 2026-01-11",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-11",
    "col4_md": "Named among more than 20 launch endorsers on 2026-01-11.",
    "full_detail_md": "The launch post (datePublished 2026-01-11) says UCP was endorsed by more than 20 others across the ecosystem like Adyen, American Express, Best Buy, Flipkart, Macy's Inc., Mastercard, Stripe, The Home Depot, Visa and Zalando. That sentence is an endorsement list, not a live /.well-known/ucp profile and not a payment-handler declaration.",
    "facets": {
     "commerce_surface": "Named ecosystem endorser in the 2026-01-11 launch post",
     "payment_handlers_or_rail": "No payment-handler id in the launch endorsement sentence",
     "transport_bindings": "No transport binding in the launch endorsement sentence",
     "spec_version": "Article datePublished 2026-01-11, not a ucp.version pin and not a registry Live grade"
    },
    "telemetry": null,
    "source_url": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/"
   },
   {
    "protocol_id": "mpp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Visa",
    "role": "Payment rail (Design partner)",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Design partner extending cards on Visa's network and Acceptance Platform; Card-Based MPP Spec is live.",
    "full_detail_md": "Announced 03/18/2026, Visa is a design partner extending card-based payments on its global network and the Visa Acceptance Platform. The Card-Based MPP Spec defines how tokenized card credentials are passed, authenticated, and processed inside MPP-compatible workflows, and Visa says the spec is now live.",
    "facets": {
     "settlement_rail": "Visa global network and the Visa Acceptance Platform for card-based payments",
     "challenge_or_scheme": "Card-Based MPP Spec for tokenized card credentials inside MPP-compatible workflows",
     "headers_or_methods": "Card credentials passed, authenticated, and processed inside the MPP Payment workflow",
     "sdk_or_endpoint": "Visa Card-Based MPP Spec, announced 03/18/2026; Visa says the spec is now live"
    },
    "telemetry": null,
    "source_url": "https://corporate.visa.com/en/sites/visa-perspectives/innovation/visa-card-specification-sdk-for-machine-payments-protocol.html"
   },
   {
    "protocol_id": "tap",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Visa",
    "role": "Identity issuer / CA",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-24",
    "col4_md": "Three signatures. The agent-recognition signature is HTTP Message Signatures (RFC 9421), aligned with Web Bot Auth. The tag is `agent-browser-auth` or `agent-payer-auth`. A public key associated with Visa means the agent is in Visa Intelligent Commerce. The ID Token is an OpenID Connect-compatible JWT (RFC 7519) digitally signed by Visa. The specification says Visa will host a well-known URL for its keys. Cloudflare's 2025-10-24 post says Visa hosts a directory of Visa-registered agents.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://developer.visa.com/docs/trusted-agent-protocol/trusted-agent-protocol-specifications"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/",
  "note": "Named among more than 20 launch endorsers on 2026-01-11."
 },
 {
  "id": "visa-tap",
  "org_id": "visa",
  "name": "Trusted Agent Protocol",
  "url": "https://developer.visa.com/docs/trusted-agent-protocol",
  "type": "authority",
  "implements": [
   "http-message-signatures"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Visa (Trusted Agent Protocol)",
    "role": "Commerce verifier (TAP profile)",
    "status": "Partial",
    "status_display": "Partial · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Trusted Agent Protocol profiles RFC 9421 `signature_base` reconstruction and public-key verification to authenticate Visa-approved commerce agents.",
    "full_detail_md": "Visa's Trusted Agent Protocol (TAP) profiles RFC 9421 HTTP Message Signatures for agentic commerce, specifying required message signature fields and merchant reconstruction of `signature_base` strings verified against an agent's public key to validate agent authenticity, consumer recognition, and payment intent.",
    "facets": {
     "profile_or_spec_target": "Visa Trusted Agent Protocol (TAP) profile of RFC 9421",
     "signature_fields": "RFC 9421 message signature fields and reconstructed `signature_base` strings",
     "algorithms_or_keys": "Public-key signature verification for Visa-approved agents",
     "verification_posture": "Commerce merchant verifier (validates agent authenticity, consumer recognition, and payment signatures)"
    },
    "telemetry": null,
    "source_url": "https://developer.visa.com/docs/trusted-agent-protocol"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://developer.visa.com/docs/trusted-agent-protocol",
  "note": "Trusted Agent Protocol profiles RFC 9421 `signature_base` reconstruction and public-key verification to authenticate Visa-approved commerce agents."
 },
 {
  "id": "vllm",
  "org_id": "vllm",
  "name": "vLLM",
  "url": "https://thenewstack.io/openai-donates-open-responses/",
  "type": "origin",
  "implements": [
   "open-responses"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "open-responses",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "vLLM",
    "role": "Inference engine",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "AWS, The New Stack, and InfoQ name vLLM among projects serving the format.",
    "full_detail_md": "AWS says open-weight serving includes vLLM among the providers serving the format, alongside Ollama, OpenRouter, and Hugging Face. The New Stack lists vLLM with OGC (previously Llama Stack) as open source projects supporting the specification, and InfoQ names vLLM with LM Studio and Ollama as a local inference provider.",
    "facets": {
     "endpoint_or_route": "No route is published in the cited AWS, New Stack, or InfoQ lines",
     "streaming_or_items": "Not stated in those provider lists",
     "tool_or_state_model": "Not stated in those provider lists",
     "sdk_or_version": "Named as an open-source serving project; those lines print no version"
    },
    "telemetry": null,
    "source_url": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://aws.amazon.com/blogs/opensource/open-responses-joins-aaif-with-aws-support/",
  "note": "AWS, The New Stack, and InfoQ name vLLM among projects serving the format."
 },
 {
  "id": "vmware-secrets-manager",
  "org_id": "vmware",
  "name": "VMware Secrets Manager",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "VMware Secrets Manager",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication.",
    "full_detail_md": "The SPIFFE overview lists VMware Secrets Manager under open-source software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID, JWT SVID, and SPIFFE Authentication, and is not marked for Workload API. VMware Secrets Manager is listed as a Kubernetes-first secrets manager that uses SPIFFE and SPIRE as its identity control plane.",
    "facets": {
     "svid_or_bundle_format": "Marks for X.509 SVID-based authentication and JWT SVID-based authentication.",
     "api_or_federation_surface": "SPIFFE Authentication is marked (federated authentication by trust domain name). Workload API is not marked.",
     "attestation_or_trust_domain": "Trust-domain federation is the marked SPIFFE Authentication column. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Open-source works-with listing: X.509 SVID, JWT SVID, and SPIFFE Authentication."
 },
 {
  "id": "vox-com-robots-txt",
  "org_id": "vox-media",
  "name": "Vox Media",
  "url": "https://www.vox.com/robots.txt",
  "type": "origin",
  "implements": [
   "ai-crawler-tokens-robots"
  ],
  "archetypes": [
   "crawler_policy"
  ],
  "implementations": [
   {
    "protocol_id": "ai-crawler-tokens-robots",
    "schema_id": "db4.crawler_policy.1",
    "archetype_slug": "crawler_policy",
    "side": "side_a",
    "actor": "Vox Media (vox.com)",
    "role": "Publisher (vox.com)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Allows `User-agent: GPTBot` and `User-agent: Amazonbot` (`Allow: /`); sets `Disallow: /` (with `Allow: /sp/` and `Allow: /strategist`) for `ClaudeBot`, `Google-Extended`, `PerplexityBot`, `Applebot-Extended`, and `CCBot`.",
    "full_detail_md": "On vox.com (covering vox.com specifically rather than every Vox Media property), sets `Allow: /` for `User-agent: GPTBot` and `User-agent: Amazonbot` while setting `Disallow: /` (with `Allow: /sp/` and `Allow: /strategist`) across `User-agent: ClaudeBot`, `User-agent: Google-Extended`, `User-agent: Google-CloudVertexBot`, `User-agent: PerplexityBot`, `User-agent: Applebot-Extended`, `User-agent: CCBot`, `User-agent: FacebookBot`, `User-agent: MistralAI-User`, `User-agent: DuckAssistBot`, `User-agent: cohere-ai`, and `User-agent: AI2Bot` alongside additional restricted crawler groups.",
    "facets": {
     "scope_host": "https://www.vox.com/robots.txt (covers vox.com only, not necessarily every Vox Media property)",
     "policy_role": "Publisher robots.txt policy declaration",
     "published_rules": [
      {
       "tokens": [
        "GPTBot",
        "Amazonbot"
       ],
       "directives": [
        "Allow: /"
       ]
      },
      {
       "tokens": [
        "ClaudeBot",
        "Google-Extended",
        "Google-CloudVertexBot",
        "PerplexityBot",
        "Applebot-Extended",
        "CCBot",
        "FacebookBot",
        "MistralAI-User",
        "DuckAssistBot",
        "cohere-ai",
        "AI2Bot"
       ],
       "directives": [
        "Disallow: /",
        "Allow: /sp/",
        "Allow: /strategist"
       ],
       "note": "Selected 11-token subset on vox.com; the live file contains additional restricted crawler groups"
      }
     ],
     "content_signals": null
    },
    "telemetry": {
     "http_status": 200,
     "artifact_kind": "robots_txt",
     "marker": "User-agent: GPTBot"
    },
    "source_url": "https://www.vox.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.vox.com/robots.txt",
  "note": "Allows `User-agent: GPTBot` and `User-agent: Amazonbot` (`Allow: /`); sets `Disallow: /` (with `Allow: /sp/` and `Allow: /strategist`) for `ClaudeBot`, `Google-Extended`, `PerplexityBot`, `Applebot-Extended`, and `CCBot`."
 },
 {
  "id": "vscode",
  "org_id": "microsoft",
  "name": "Visual Studio Code",
  "url": "https://code.visualstudio.com",
  "type": "harness",
  "implements": [
   "agents-md",
   "mcp",
   "mcp-apps",
   "mcp-registry",
   "oauth-cimd"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "identity_auth_crypto",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "mcp",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Visual Studio Code",
    "role": "IDE host",
    "status": "Supported",
    "status_display": "Supported · as of 2025-06-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-06-12",
    "col4_md": "Supports `streamable HTTP` and local transports, OAuth resource-server authorization, `tools`, `prompts`, `resources`, and `sampling`.",
    "full_detail_md": "Visual Studio Code implements the handshake-era MCP specification (`2025-06-12`), supporting local `stdio` and remote `streamable HTTP` servers, OAuth authorization separating Resource Providers from Authorization Servers, `tools`, slash-command `prompts`, interactive `resources`, and `sampling`.",
    "facets": {
     "transport": "Streamable HTTP, stdio",
     "auth_or_oauth": "OAuth 2.1 (Resource Provider / Authorization Server separation), Bearer PAT",
     "primitives": "tools, prompts, resources, sampling",
     "sdk_or_package": "VS Code v1.101+"
    },
    "telemetry": null,
    "source_url": "https://code.visualstudio.com/blogs/2025/06/12/full-mcp-spec-support"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Visual Studio Code",
    "role": "IDE / Editor",
    "status": "Experimental",
    "status_display": "Experimental · as of 2025-08",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-08",
    "col4_md": "Picks up workspace-root `AGENTS.md` for chat requests under default-enabled experimental `chat.useAgentsMdFile` setting (v1.104).",
    "full_detail_md": "Introduced experimental `AGENTS.md` support in Visual Studio Code v1.104 (August 2025), enabled by default via the `chat.useAgentsMdFile` setting so any `AGENTS.md` file in the workspace root(s) is automatically attached as context for chat requests.",
    "facets": {
     "discovery_behavior": "Automatically picks up workspace-root AGENTS.md for chat requests (controlled by chat.useAgentsMdFile, enabled by default)",
     "hierarchy_precedence": "Workspace root(s) in v1.104 release notes",
     "fallback_files": ".github/copilot-instructions.md",
     "verification_posture": "Documented as Experimental in VS Code v1.104 (August 2025) release notes"
    },
    "telemetry": null,
    "source_url": "https://code.visualstudio.com/updates/v1_104"
   },
   {
    "protocol_id": "mcp-apps",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Visual Studio Code",
    "role": "IDE",
    "status": "Supported",
    "status_display": "Supported · as of 2026-02-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-02-04",
    "col4_md": "Release 1.109 (February 4, 2026) added MCP Apps; the January 26 post was Insiders.",
    "full_detail_md": "The January 26, 2026 post says VS Code is the first major AI code editor with full MCP Apps support and that it was available then in VS Code Insiders. Release 1.109, dated February 4, 2026, says VS Code has added support for MCP Apps so servers can display rich, interactive UI in the client, which is the released surface rather than the Insiders announcement alone.",
    "facets": {
     "transport_or_channel": "VS Code client renders MCP Apps UI from the server inside the editor",
     "ui_resource_or_primitive": "Rich, interactive UI that MCP servers display in the client",
     "sandbox_or_security": "Release notes do not restate CSP; rendering follows the MCP Apps sandbox model",
     "sdk_or_version": "Insiders announcement 2026-01-26; released support in VS Code 1.109 on 2026-02-04"
    },
    "telemetry": null,
    "source_url": "https://code.visualstudio.com/blogs/2026/01/26/mcp-apps-support"
   },
   {
    "protocol_id": "mcp-registry",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "VS Code",
    "role": "IDE client",
    "status": "Supported",
    "status_display": "Supported · as of 2025-11-18",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-18",
    "col4_md": "Supports `v0.1` MCP registries and allowlist controls in VS Code Stable (since 2025-11-18) with `@mcp` gallery search.",
    "full_detail_md": "On `2025-11-18` GitHub said VS Code Stable shows registry servers in the MCP servers sidebar panel, and that a registry-only policy blocks servers that are not on the registry. Self-hosted registries must follow the `v0.1` MCP registry specification. VS Code also documents an MCP server gallery (Preview) opened by searching `@mcp` in the Extensions view.",
    "facets": {
     "registry_or_namespace": "VS Code MCP servers sidebar and Extensions gallery (@mcp)",
     "api_or_schema_version": "Self-hosted registries must follow the v0.1 MCP registry specification",
     "transport_or_package_types": "IDE client consuming registry listings",
     "verification_posture": "Document citation of the GitHub changelog 2025-11-18 and VS Code MCP docs (checked 2026-10-30)"
    },
    "telemetry": null,
    "source_url": "https://github.blog/changelog/2025-11-18-internal-mcp-registry-and-allowlist-controls-for-vs-code-stable-in-public-preview/"
   },
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Microsoft, Visual Studio Code",
    "role": "OAuth client",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; `token_endpoint_auth_method` `none`; `application_type` `native`.",
    "full_detail_md": "`https://vscode.dev/oauth/client-metadata.json` returned HTTP 200 `application/json`, with `client_id` equal to that URL, `client_name` Visual Studio Code, and `client_uri` `https://vscode.dev/product`. `token_endpoint_auth_method` is `none`, `application_type` is `native`, `grant_types` are `authorization_code`, `refresh_token`, and `urn:ietf:params:oauth:grant-type:device_code`, and `redirect_uris` are `http://127.0.0.1:33418/` and `https://vscode.dev/redirect`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "Published client metadata JSON; client_name Visual Studio Code; client_id equals the document URL; application_type native",
     "auth_method_or_pkce": "token_endpoint_auth_method none; grant_types authorization_code, refresh_token, and urn:ietf:params:oauth:grant-type:device_code; this document has no code_challenge_methods_supported field",
     "uri_or_ssrf_rules": "redirect_uris http://127.0.0.1:33418/ and https://vscode.dev/redirect; the client_id URL itself is https on vscode.dev, not a special-use address",
     "draft_or_spec_version": "Live client metadata JSON checked 2026-10-30; the document does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "client_name": "Visual Studio Code",
     "token_endpoint_auth_method": "none"
    },
    "source_url": "https://vscode.dev/oauth/client-metadata.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://code.visualstudio.com/blogs/2025/06/12/full-mcp-spec-support",
  "note": "Supports `streamable HTTP` and local transports, OAuth resource-server authorization, `tools`, `prompts`, `resources`, and `sampling`."
 },
 {
  "id": "vscode-pagepilot",
  "org_id": "pagepilot",
  "name": "VS Code PagePilot Extension",
  "url": "https://llmstxt.org",
  "type": "harness",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "VS Code PagePilot Extension",
    "role": "Coding agent / IDE",
    "status": "Listed integration",
    "status_display": "Listed integration · as of 2026-08-10",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-10",
    "col4_md": "Listed integration on `llmstxt.org` for VS Code context; implementation behavior not independently verified.",
    "full_detail_md": "Listed integration on `llmstxt.org` as a VS Code extension that uses `llms.txt` to provide documentation context for GitHub Copilot and Cursor; implementation behavior is not independently verified.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "Linked documentation, API references, and README files",
     "content_type_or_bytes": "External Markdown context loading",
     "generator_or_consumer_mode": "Listed integration on `llmstxt.org` (`PagePilot` VS Code extension; implementation behavior not independently verified)"
    },
    "telemetry": null,
    "source_url": "https://llmstxt.org"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://llmstxt.org",
  "note": "Listed integration on `llmstxt.org` for VS Code context; implementation behavior not independently verified."
 },
 {
  "id": "walmart",
  "org_id": "walmart",
  "name": "Walmart",
  "url": "https://corporate.walmart.com/news/2025/10/14/walmart-partners-with-openai-to-create-ai-first-shopping-experiences",
  "type": "origin",
  "implements": [
   "agentic-commerce-protocol",
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "agentic-commerce-protocol",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Walmart",
    "role": "Enterprise retailer",
    "status": "Supported",
    "status_display": "Supported · as of 2026-03-24",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-03-24",
    "col4_md": "Announced ChatGPT Instant Checkout partnership on October 14, 2025; introduced tailored in-ChatGPT app with account linking, loyalty, and Walmart payments on March 24, 2026.",
    "full_detail_md": "Walmart announced on October 14, 2025 a partnership with OpenAI allowing customers and Sam's Club members to shop Walmart through ChatGPT using Instant Checkout. On March 24, 2026, OpenAI announced that Walmart was introducing a tailored in-ChatGPT app experience supporting account linking, loyalty, and Walmart payments.",
    "facets": {
     "commerce_role_or_surface": "In-ChatGPT shopping and tailored Walmart app experience",
     "payment_or_token_rail": "Instant Checkout (announced October 2025); tailored Walmart app with account linking, loyalty, and Walmart payments (March 2026)",
     "api_or_spec_version": "Agentic Commerce Protocol",
     "availability_or_eligibility_posture": "Announced October 14, 2025; tailored in-ChatGPT app experience announced March 24, 2026"
    },
    "telemetry": null,
    "source_url": "https://corporate.walmart.com/news/2025/10/14/walmart-partners-with-openai-to-create-ai-first-shopping-experiences"
   },
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Walmart",
    "role": "Retailer (co-developer)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-15",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-15",
    "col4_md": "Co-developer; coming soon on 2026-02-11; listed on Universal Cart.",
    "full_detail_md": "The launch post (datePublished 2026-01-11) names Walmart as a co-developer, and the 2026-02-11 post said Shopify, Target, and Walmart were coming soon while Etsy and Wayfair checkout was rolling out. Universal Cart (datePublished 2026-10-15) includes Walmart among merchants for checkout powered by UCP.",
    "facets": {
     "commerce_surface": "Walmart named on Universal Cart and as a launch co-developer",
     "payment_handlers_or_rail": "UCP checkout; February 2026 post still said Walmart was coming soon",
     "transport_bindings": "Google AI surfaces; no probed Walmart /.well-known/ucp body in this row",
     "spec_version": "Co-developer 2026-01-11; coming-soon clause datePublished 2026-02-11; cart list datePublished 2026-10-15"
    },
    "telemetry": null,
    "source_url": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://corporate.walmart.com/news/2025/10/14/walmart-partners-with-openai-to-create-ai-first-shopping-experiences",
  "note": "Announced ChatGPT Instant Checkout partnership on October 14, 2025; introduced tailored in-ChatGPT app with account linking, loyalty, and Walmart payments on March 24, 2026."
 },
 {
  "id": "warp-freight",
  "org_id": "warp",
  "name": "Warp Freight",
  "url": "https://www.wearewarp.com/.well-known/agent-card.json",
  "type": "agent",
  "implements": [
   "a2a"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "a2a",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Warp (Warp Freight)",
    "role": "Public A2A agent",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Live Agent Card binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.wearewarp.com/api/a2a/jsonrpc` with `bearer` `warpApiKey` and freight skills.",
    "full_detail_md": "Warp serves a live HTTP 200 Agent Card at https://www.wearewarp.com/.well-known/agent-card.json (`Warp Freight` v`0.23.0`, response header `a2a-version: 1.0.0`, checked 2026-10-30) binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.wearewarp.com/api/a2a/jsonrpc` with keyless US domestic quote skills (`get_ltl_freight_quote`, `get_ftl_freight_quote`, `get_box_truck_quote`, `get_cargo_van_quote`) and `bearer` `warpApiKey`-authenticated tracking, rate-history, and booking skills (`track_shipment`, `get_lane_rate_history`, `book_shipment`).",
    "facets": {
     "transport_bindings": "JSONRPC at https://www.wearewarp.com/api/a2a/jsonrpc (streaming: false; response header a2a-version: 1.0.0)",
     "discovery_artifact": "GET https://www.wearewarp.com/.well-known/agent-card.json (v0.23.0, A2A 1.0 card schema)",
     "protocol_version": "1.0 (header a2a-version: 1.0.0)",
     "auth_schemes": "Optional HTTP Bearer (warpApiKey: wak_test_* / wak_live_*); keyless for quote skills, Bearer required for tracking and booking",
     "verification_posture": "Live HTTP 200 Agent Card probe (checked 2026-10-30)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "a2a_version_header": "1.0.0",
     "protocol_version": "1.0",
     "agent_version": "0.23.0"
    },
    "source_url": "https://www.wearewarp.com/.well-known/agent-card.json"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.wearewarp.com/.well-known/agent-card.json",
  "note": "Live Agent Card binding `JSONRPC` (`protocolVersion` `1.0`) at `https://www.wearewarp.com/api/a2a/jsonrpc` with `bearer` `warpApiKey` and freight skills."
 },
 {
  "id": "warpstream",
  "org_id": "warpstream",
  "name": "WarpStream",
  "url": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "type": "authority",
  "implements": [
   "spiffe"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "spiffe",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "WarpStream",
    "role": "Relying service",
    "status": "Listed integration",
    "status_display": "Listed integration · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Commercial works-with listing: X.509 SVID authentication only.",
    "full_detail_md": "The SPIFFE overview lists WarpStream under commercial software that works with SPIFFE. Columns on that table are X.509 SVID, JWT SVID, SPIFFE Authentication, and Workload API. The works-with row is marked for X.509 SVID only.",
    "facets": {
     "svid_or_bundle_format": "A single mark, for X.509 SVID-based authentication.",
     "api_or_federation_surface": "JWT SVID, SPIFFE Authentication, and the Workload API are not marked.",
     "attestation_or_trust_domain": "No trust-domain federation mark. The listing does not describe an attestation method.",
     "verification_posture": "Listed in the SPIFFE overview table (fetched 2026-10-30); reflects ecosystem directory listing rather than an independent conformance audit."
    },
    "telemetry": null,
    "source_url": "https://spiffe.io/docs/latest/spiffe-about/overview/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://spiffe.io/docs/latest/spiffe-about/overview/",
  "note": "Commercial works-with listing: X.509 SVID authentication only."
 },
 {
  "id": "wayfair",
  "org_id": "wayfair",
  "name": "Wayfair",
  "url": "https://www.wayfair.com",
  "type": "venue",
  "implements": [
   "ucp"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "ucp",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "Wayfair",
    "role": "Retailer (co-developer)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-15",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-15",
    "col4_md": "Co-developer; 2026-02-11 UCP checkout rollout; Universal Cart merchant.",
    "full_detail_md": "The launch post (datePublished 2026-01-11) names Wayfair as a co-developer, and on datePublished 2026-02-11 UCP-powered checkout was rolling out for US shoppers to buy from Etsy and Wayfair in AI Mode in Search and the Gemini app. Universal Cart (datePublished 2026-10-15) includes Wayfair among merchants for checkout powered by UCP.",
    "facets": {
     "commerce_surface": "Wayfair checkout in AI Mode, Search, and the Gemini app",
     "payment_handlers_or_rail": "UCP-powered checkout rolling out 2026-02-11; Universal Cart merchant",
     "transport_bindings": "Google AI surfaces; no probed Wayfair /.well-known/ucp body in this row",
     "spec_version": "Co-developer in the 2026-01-11 launch; rollout article datePublished 2026-02-11; cart post datePublished 2026-10-15"
    },
    "telemetry": null,
    "source_url": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/",
  "note": "Co-developer; 2026-02-11 UCP checkout rollout; Universal Cart merchant."
 },
 {
  "id": "web-bot-auth-sdk",
  "org_id": "web-bot-auth-sdk",
  "name": "web-bot-auth SDK (Cloudflare)",
  "url": "https://raw.githubusercontent.com/cloudflare/web-bot-auth/main/packages/web-bot-auth/src/registry.ts",
  "type": "sdk",
  "implements": [
   "web-bot-auth-signature-agent-card"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "web-bot-auth-signature-agent-card",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "web-bot-auth SDK (Cloudflare)",
    "role": "Verifier SDK / Runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-31",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-31",
    "col4_md": "npm package web-bot-auth 0.2.0, published 2026-08-31. TypeScript registry.ts parses Signature-Agent entries whose type is directory, jwks_uri, or cimd, each with a label and a URI. The Rust crate uses the same three discovery types: Directory, JwksUri, and Cimd.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/cloudflare/web-bot-auth/main/packages/web-bot-auth/src/registry.ts"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/cloudflare/web-bot-auth/main/packages/web-bot-auth/src/registry.ts",
  "note": "npm package web-bot-auth 0.2.0, published 2026-08-31. TypeScript registry.ts parses Signature-Agent entries whose type is directory, jwks_uri, or cimd, each with a label and a URI. The Rust crate uses the same three discovery types: Directory, JwksUri, and Cimd."
 },
 {
  "id": "webbotauth-net",
  "org_id": "webbotauth-net",
  "name": "WebBotAuth.net",
  "url": "https://webbotauth.net/kb/signature-agent-card",
  "type": "authority",
  "implements": [
   "web-bot-auth-signature-agent-card"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "web-bot-auth-signature-agent-card",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "WebBotAuth.net",
    "role": "Explorer / Scanner",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Finds a Signature Agent Card from the directory Link header or a homepage link element. Reads both the nested web_bot_auth object (registry-03 and -04) and the flat registry-02 document. A card needs at least one parameter. Card checks are advisory: a missing or incomplete card lowers the score and never overrides a VALID directory. The checker does not resolve Signature-Agent type=cimd yet. The directory path remains /.well-known/http-message-signatures-directory.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://webbotauth.net/kb/signature-agent-card"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://webbotauth.net/kb/signature-agent-card",
  "note": "Finds a Signature Agent Card from the directory Link header or a homepage link element. Reads both the nested web_bot_auth object (registry-03 and -04) and the flat registry-02 document. A card needs at least one parameter. Card checks are advisory: a missing or incomplete card lowers the score and never overrides a VALID directory. The checker does not resolve Signature-Agent type=cimd yet. The d"
 },
 {
  "id": "webclaw",
  "org_id": "webclaw",
  "name": "WebClaw",
  "url": "https://webclaw.io/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "WebClaw",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "https://webclaw.io/auth.md says onboarding is OAuth 2.0 Device Authorization. The agent requests a short-lived scoped bearer token, shows the user a code, and waits for browser approval. Fetched status 200 on 2026-10-29.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://webclaw.io/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://webclaw.io/auth.md",
  "note": "https://webclaw.io/auth.md says onboarding is OAuth 2.0 Device Authorization. The agent requests a short-lived scoped bearer token, shows the user a code, and waits for browser approval. Fetched status 200 on 2026-10-29."
 },
 {
  "id": "webmcp-extension",
  "org_id": "googlechromelabs",
  "name": "webmcp-extension",
  "url": "https://github.com/GoogleChromeLabs/webmcp-extension/",
  "type": "sdk",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Chrome WebMCP example extension",
    "role": "Reference agent extension",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Reads `document.modelContext.getTools()` and `ontoolchange`.",
    "full_detail_md": "The example extension reads document.modelContext.getTools() and listens for ontoolchange, including iframes. Cross-origin tools require allow=\"tools\". Backends are a local server or the on-device Prompt API behind chrome://flags/#prompt-api-tool-use. The repository says it is not an officially supported Google product.",
    "facets": {
     "engine_or_runtime": "Example agentic Chrome extension",
     "api_surface_or_flag": "document.modelContext.getTools(), ontoolchange, allow=\"tools\"",
     "position_or_status": "Example extension, not an officially supported Google product",
     "package_or_version": "https://github.com/GoogleChromeLabs/webmcp-extension/"
    },
    "telemetry": null,
    "source_url": "https://github.com/GoogleChromeLabs/webmcp-extension/"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/GoogleChromeLabs/webmcp-extension/",
  "note": "Reads `document.modelContext.getTools()` and `ontoolchange`."
 },
 {
  "id": "webmcp-tools-demos",
  "org_id": "googlechromelabs",
  "name": "webmcp-tools demos",
  "url": "https://github.com/GoogleChromeLabs/webmcp-tools",
  "type": "sdk",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_a",
    "actor": "Chrome WebMCP demos",
    "role": "Reference page demos",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Travel imperative demo and Le Petit Bistro declarative demo.",
    "full_detail_md": "The GoogleChromeLabs webmcp-tools repository includes a Travel React demo of the imperative API and Le Petit Bistro as a declarative reservation form, plus a mini-site explainer.",
    "facets": {
     "engine_or_runtime": "Reference demos in GoogleChromeLabs/webmcp-tools",
     "api_surface_or_flag": "Imperative Travel demo and declarative Le Petit Bistro demo",
     "position_or_status": "Official demo repository checked 2026-11-06",
     "package_or_version": "https://github.com/GoogleChromeLabs/webmcp-tools"
    },
    "telemetry": null,
    "source_url": "https://github.com/GoogleChromeLabs/webmcp-tools"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/GoogleChromeLabs/webmcp-tools",
  "note": "Travel imperative demo and Le Petit Bistro declarative demo."
 },
 {
  "id": "webmcp-tools-utilities",
  "org_id": "googlechromelabs",
  "name": "webmcp-tools utilities",
  "url": "https://github.com/GoogleChromeLabs/webmcp-tools",
  "type": "sdk",
  "implements": [
   "webmcp"
  ],
  "archetypes": [
   "browser_telemetry"
  ],
  "implementations": [
   {
    "protocol_id": "webmcp",
    "schema_id": "db4.browser_telemetry.1",
    "archetype_slug": "browser_telemetry",
    "side": "side_b",
    "actor": "Chrome WebMCP developer utilities",
    "role": "Inspector, evals, and polyfill",
    "status": "Experimental",
    "status_display": "Experimental · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Inspector, Evals CLI, skills, and a declarative polyfill.",
    "full_detail_md": "The same repository ships a Model Context Tool Inspector extension, a WebMCP Evals CLI, WebMCP Skills, and a declarative polyfill for form toolname, toolautosubmit, and respondWith().",
    "facets": {
     "engine_or_runtime": "Chrome extension, CLI, and page polyfill",
     "api_surface_or_flag": "Inspector, evals, skills, declarative polyfill",
     "position_or_status": "Developer utilities beside the reference demos",
     "package_or_version": "GoogleChromeLabs/webmcp-tools"
    },
    "telemetry": null,
    "source_url": "https://github.com/GoogleChromeLabs/webmcp-tools"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/GoogleChromeLabs/webmcp-tools",
  "note": "Inspector, Evals CLI, skills, and a declarative polyfill."
 },
 {
  "id": "wildcard-bridge",
  "org_id": "wildcard-bridge",
  "name": "Wildcard Bridge (agentsjson)",
  "url": "https://wildcard.mintlify.app/agentsjson/bridge-about",
  "type": "sdk",
  "implements": [
   "agents-json"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "agents-json",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Wildcard Bridge (agentsjson)",
    "role": "Client SDK / Runtime",
    "status": "Supported",
    "status_display": "Supported · as of 2025-03-01",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-03-01",
    "col4_md": "Python package `agentsjson` 0.1.14 on PyPI (uploaded 2025-03-01; python/pyproject.toml in the repo says 0.1.11) loads an `agents.json` file and dispatches chains via bundled integrations with `Basic`, `ApiKey`, `Bearer`, or OAuth auth; docs state Bridge is AGPL v3 while the repo root LICENSE is MIT and agents_json/LICENSE is Apache-2.0.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://wildcard.mintlify.app/agentsjson/bridge-about"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://wildcard.mintlify.app/agentsjson/bridge-about",
  "note": "Python package `agentsjson` 0.1.14 on PyPI (uploaded 2025-03-01; python/pyproject.toml in the repo says 0.1.11) loads an `agents.json` file and dispatches chains via bundled integrations with `Basic`, `ApiKey`, `Bearer`, or OAuth auth; docs state Bridge is AGPL v3 while the repo root LICENSE is MIT and agents_json/LICENSE is Apache-2.0."
 },
 {
  "id": "wimsey-issuer",
  "org_id": "kanywst",
  "name": "wimsey",
  "url": "https://github.com/kanywst/wimsey",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "wimsey",
    "role": "Reference WIT / WIC issuer",
    "status": "Development",
    "status_display": "Development · as of 2026-09-08",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-08",
    "col4_md": "wimsey is a vendor-neutral reference implementation of the IETF WIMSE workload-identity specs, in Rust. The repository says it is pre-alpha, that the specs are Internet-Drafts with no RFC yet, and that it is not production-ready. The `wimsey-wit` crate covers the Workload Identity Token (WIT / WIC). draft-ietf-wimse-http-signature-08 section 4.2 records the same repository at alpha maturity for WIT plus HTTP Message Signatures, including signed responses, Apache 2.0, last updated 08-Sep-2026. GitHub records repository creation on 2026-06-29 under the `Apache-2.0` license.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/kanywst/wimsey"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/kanywst/wimsey",
  "note": "wimsey is a vendor-neutral reference implementation of the IETF WIMSE workload-identity specs, in Rust. The repository says it is pre-alpha, that the specs are Internet-Drafts with no RFC yet, and that it is not production-ready. The `wimsey-wit` crate covers the Workload Identity Token (WIT / WIC). draft-ietf-wimse-http-signature-08 section 4.2 records the same repository at alpha maturity for WI"
 },
 {
  "id": "wimsey-verifier",
  "org_id": "kanywst",
  "name": "wimsey conformance",
  "url": "https://github.com/kanywst/wimsey",
  "type": "authority",
  "implements": [
   "wimse"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "wimse",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "wimsey",
    "role": "Reference verifier",
    "status": "Development",
    "status_display": "Development · as of 2026-09-08",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-09-08",
    "col4_md": "draft-ietf-wimse-http-signature-08 section 4.2 records wimsey at alpha maturity with coverage of WIT, HTTP Message Signatures, and signed responses. The repository is pre-alpha and not production-ready. Its `conformance/` notes record inputs, the exact bytes they must produce, and, for every negative case, a language-neutral code naming why the input must be rejected.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/kanywst/wimsey"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/kanywst/wimsey",
  "note": "draft-ietf-wimse-http-signature-08 section 4.2 records wimsey at alpha maturity with coverage of WIT, HTTP Message Signatures, and signed responses. The repository is pre-alpha and not production-ready. Its `conformance/` notes record inputs, the exact bytes they must produce, and, for every negative case, a language-neutral code naming why the input must be rejected."
 },
 {
  "id": "windsurf",
  "org_id": "cognition",
  "name": "Windsurf",
  "url": "https://agents.md/",
  "type": "harness",
  "implements": [
   "agents-md"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Windsurf (Cognition)",
    "role": "IDE / Coding agent",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Named in the compatible coding-agent roster on `agents.md`.",
    "full_detail_md": "Listed on `agents.md` under compatible AI coding agents and tools (Windsurf from Cognition); native `AGENTS.md` file discovery and directory-hierarchy precedence are not independently verified in the cited documentation snapshots.",
    "facets": {
     "discovery_behavior": "Listed on agents.md — implementation behavior not independently verified",
     "hierarchy_precedence": "Not independently verified in cited documentation",
     "fallback_files": ".windsurfrules; .windsurf/rules/",
     "verification_posture": "Listed on agents.md — implementation behavior not independently verified"
    },
    "telemetry": null,
    "source_url": "https://agents.md/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://agents.md/",
  "note": "Named in the compatible coding-agent roster on `agents.md`."
 },
 {
  "id": "wix",
  "org_id": "wix",
  "name": "Wix",
  "url": "https://support.wix.com/en/article/enabling-nlweb-for-ai-agent-access",
  "type": "origin",
  "implements": [
   "llms-txt",
   "nlweb"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "nlweb",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Wix",
    "role": "NLWeb site",
    "status": "Supported",
    "status_display": "Supported · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Wix documents NLWeb on hosted sites. The MCP URL pattern is `https://www.[your-domain.com]/_api/nlweb/mcp`, for an MCP-capable agent such as Claude or ChatGPT.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://support.wix.com/en/article/enabling-nlweb-for-ai-agent-access"
   },
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Wix",
    "role": "Hosted CMS platform",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-10",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-10",
    "col4_md": "Hosted website builder documented on `llmstxt.org` that generates an `llms.txt` file for every Wix site.",
    "full_detail_md": "Listed in the `llmstxt.org` Integrations section and Ahrefs' May 2026 study as a mainstream website builder that automatically generates an `/llms.txt` file for every hosted Wix site.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "None stated",
     "content_type_or_bytes": "Generated Markdown index (CMS platform)",
     "generator_or_consumer_mode": "Hosted CMS platform generating /llms.txt for every Wix site"
    },
    "telemetry": null,
    "source_url": "https://llmstxt.org"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://support.wix.com/en/article/enabling-nlweb-for-ai-agent-access",
  "note": "Wix documents NLWeb on hosted sites. The MCP URL pattern is `https://www.[your-domain.com]/_api/nlweb/mcp`, for an MCP-capable agent such as Claude or ChatGPT."
 },
 {
  "id": "wix-as-meta",
  "org_id": "wix",
  "name": "Wix MCP authorization server",
  "url": "https://mcp.wix.com",
  "type": "authority",
  "implements": [
   "oauth-metadata-for-agents"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-metadata-for-agents",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Wix",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "`issuer` `https://mcp.wix.com`; PKCE `plain` and `S256`; `authorization_code`, `refresh_token`; `registration_endpoint`.",
    "full_detail_md": "GET https://mcp.wix.com/.well-known/oauth-authorization-server returned HTTP 200 `application/json`. `issuer` is `https://mcp.wix.com`. `authorization_endpoint`, `token_endpoint`, and `registration_endpoint` are on that host. `grant_types_supported` are `authorization_code` and `refresh_token`. `code_challenge_methods_supported` are `plain` and `S256`. `token_endpoint_auth_methods_supported` includes `none`. Checked 2026-11-03.",
    "facets": {
     "metadata_endpoints_served": "GET https://mcp.wix.com/.well-known/oauth-authorization-server (issuer https://mcp.wix.com; authorization, token, and registration endpoints on that host)",
     "registration_or_client_id_modes": "registration_endpoint https://mcp.wix.com/register; token_endpoint_auth_methods_supported includes none, client_secret_basic, and client_secret_post; client_id_metadata_document_supported not declared",
     "pkce_or_grant_types": "PKCE plain and S256; grant_types_supported authorization_code and refresh_token",
     "verification_posture": "Live HTTP 200 application/json probe (checked 2026-11-03)"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "metadata_kind": "oauth-authorization-server",
     "issuer": "https://mcp.wix.com"
    },
    "source_url": "https://mcp.wix.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://mcp.wix.com/.well-known/oauth-authorization-server",
  "note": "`issuer` `https://mcp.wix.com`; PKCE `plain` and `S256`; `authorization_code`, `refresh_token`; `registration_endpoint`."
 },
 {
  "id": "wolfssl",
  "org_id": "wolfssl",
  "name": "wolfSSL",
  "url": "https://www.wolfssl.com/native-http-message-signatures-in-curl-powered-by-wolfssl-part-3/",
  "type": "sdk",
  "implements": [
   "http-message-signatures"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "http-message-signatures",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "wolfSSL",
    "role": "Crypto library (curl / libcurl RFC 9421)",
    "status": "Development",
    "status_display": "Development · as of 2026-06-12",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-06-12",
    "col4_md": "Contributes native RFC 9421 `Ed25519` signing in curl/libcurl via open PRs `curl/curl#21239` and `wolfSSL/wolfssl-examples#566`.",
    "full_detail_md": "Documents contributing native RFC 9421 HTTP Message Signatures support at the curl and libcurl plumbing layer (`CURLOPT_HTTPSIG`, `CURLOPT_HTTPSIG_KEY`, `CURLOPT_HTTPSIG_KEYID`, `CURLOPT_HTTPSIG_HEADERS`) with wolfCrypt providing the `Ed25519` and `hmac-sha256` cryptography across two open pull requests (`curl/curl#21239` and `wolfSSL/wolfssl-examples#566`, published June 12, 2026).",
    "facets": {
     "profile_or_spec_target": "RFC 9421 plumbing in curl and libcurl (`curl/curl#21239`, `wolfSSL/wolfssl-examples#566`)",
     "signature_fields": "`Signature-Input` and `Signature` (`CURLOPT_HTTPSIG`, `CURLOPT_HTTPSIG_HEADERS`)",
     "algorithms_or_keys": "wolfCrypt `Ed25519` and `hmac-sha256` (`CURLOPT_HTTPSIG_KEY`, `CURLOPT_HTTPSIG_KEYID`)",
     "verification_posture": "Crypto library / HTTP client integration (open pull requests as of 2026-06-12)"
    },
    "telemetry": null,
    "source_url": "https://www.wolfssl.com/native-http-message-signatures-in-curl-powered-by-wolfssl-part-3/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.wolfssl.com/native-http-message-signatures-in-curl-powered-by-wolfssl-part-3/",
  "note": "Contributes native RFC 9421 `Ed25519` signing in curl/libcurl via open PRs `curl/curl#21239` and `wolfSSL/wolfssl-examples#566`."
 },
 {
  "id": "wordpress-openverse-api",
  "org_id": "wordpress-openverse-api",
  "name": "WordPress Openverse API",
  "url": "https://api.openverse.org/ai.txt",
  "type": "origin",
  "implements": [
   "ai-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "ai-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "WordPress Openverse API",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, per-extension `Disallow:` from `*.txt` through `*.sql`, then `Disallow: /` and `Disallow: *`).",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://api.openverse.org/ai.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://api.openverse.org/ai.txt",
  "note": "Serves `/ai.txt` in Spawning format (`# Spawning AI`, `User-Agent: *`, per-extension `Disallow:` from `*.txt` through `*.sql`, then `Disallow: /` and `Disallow: *`)."
 },
 {
  "id": "workable",
  "org_id": "workable",
  "name": "Workable",
  "url": "https://workable.com/robots.txt",
  "type": "origin",
  "implements": [
   "cloudflare-content-signals-policy"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-content-signals-policy",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Workable",
    "role": "Publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · as of 2026-10-29",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-29",
    "col4_md": "`https://workable.com/robots.txt` returned status 200 on 2026-10-29 with a shortened policy comment and, in the group for all user agents, `Content-Signal: search=yes, ai-input=yes, ai-train=no`.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://workable.com/robots.txt"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://workable.com/robots.txt",
  "note": "`https://workable.com/robots.txt` returned status 200 on 2026-10-29 with a shortened policy comment and, in the group for all user agents, `Content-Signal: search=yes, ai-input=yes, ai-train=no`."
 },
 {
  "id": "workos",
  "org_id": "workos",
  "name": "WorkOS",
  "url": "https://workos.com/auth.md",
  "type": "origin",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "WorkOS",
    "role": "Auth policy publisher",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "https://workos.com/auth.md is the user-claimed flow for one-shot environments: the agent provisions an anonymous temporary environment, works immediately, and the user claims it later. Claim handoff is https://dashboard.workos.com or npx workos@latest env claim. The file says there is no agent-verified or email-verified registration on this surface.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://workos.com/auth.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://workos.com/auth.md",
  "note": "https://workos.com/auth.md is the user-claimed flow for one-shot environments: the agent provisions an anonymous temporary environment, works immediately, and the user claims it later. Claim handoff is https://dashboard.workos.com or npx workos@latest env claim. The file says there is no agent-verified or email-verified registration on this surface."
 },
 {
  "id": "workos-auth-md",
  "org_id": "workos",
  "name": "WorkOS auth.md",
  "url": "https://github.com/workos/auth.md",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "WorkOS",
    "role": "Sample ID-JAG issuer (auth.md)",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "The `workos/auth.md` README describes a reference implementation with an agent provider that mints identity assertions (ID-JAGs) and a sample agent IdP that mints ID-JAGs. Okta's partner announcement lists WorkOS among 25+ early adopters of Cross App Access.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://raw.githubusercontent.com/workos/auth.md/main/README.md"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://raw.githubusercontent.com/workos/auth.md/main/README.md",
  "note": "The `workos/auth.md` README describes a reference implementation with an agent provider that mints identity assertions (ID-JAGs) and a sample agent IdP that mints ID-JAGs. Okta's partner announcement lists WorkOS among 25+ early adopters of Cross App Access."
 },
 {
  "id": "workos-authkit",
  "org_id": "workos-authkit",
  "name": "WorkOS AuthKit",
  "url": "https://workos.com/docs/authkit/agent-registration",
  "type": "authority",
  "implements": [
   "auth-md"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "auth-md",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "WorkOS AuthKit",
    "role": "Authorization server / IdP",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-04",
    "col4_md": "Agent Registration has been generally available since 2026-08-04. The agent discovers the surface from /.well-known/oauth-authorization-server, registers with an identity type, optionally binds a user in a claim ceremony, and exchanges the resulting identity assertion for an access token or API key. v0.6.0 mints that identity_assertion at registration and exchanges it at the OAuth token endpoint. A first-time ID-JAG link to an existing account requires a user-confirmation ceremony and a fresh auth_time.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://workos.com/docs/authkit/agent-registration"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://workos.com/docs/authkit/agent-registration",
  "note": "Agent Registration has been generally available since 2026-08-04. The agent discovers the surface from /.well-known/oauth-authorization-server, registers with an identity type, optionally binds a user in a claim ceremony, and exchanges the resulting identity assertion for an access token or API key. v0.6.0 mints that identity_assertion at registration and exchanges it at the OAuth token endpoint. "
 },
 {
  "id": "workos-cimd",
  "org_id": "workos",
  "name": "WorkOS Connect",
  "url": "https://workos.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "WorkOS",
    "role": "Identity provider",
    "status": "Supported",
    "status_display": "Supported · as of 2025-11-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-11-30",
    "col4_md": "Connect supports CIMD; dashboard flag is off by default (2025-11-30).",
    "full_detail_md": "WorkOS Connect supports Client ID Metadata Documents for MCP, so clients can identify themselves without preregistration. AuthKit docs say Client ID Metadata Document is off by default and is enabled in the WorkOS Dashboard under Connect configuration. The changelog date is November 30, 2025.",
    "facets": {
     "metadata_flag_or_profile": "WorkOS Connect CIMD for MCP; AuthKit documents the feature as off by default until enabled in the Dashboard",
     "auth_method_or_pkce": "Clients identify themselves without preregistration; the cited pages do not name a PKCE method",
     "uri_or_ssrf_rules": "Not specified on the changelog or AuthKit MCP page",
     "draft_or_spec_version": "Changelog dated November 30, 2025. The AuthKit page says the MCP protocol specifies that authorization servers should support CIMD, which is SHOULD-level protocol guidance, separate from the CIMD draft MUST rules"
    },
    "telemetry": null,
    "source_url": "https://workos.com/changelog/client-id-metadata-support-for-mcp-auth"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://workos.com/changelog/client-id-metadata-support-for-mcp-auth",
  "note": "Connect supports CIMD; dashboard flag is off by default (2025-11-30)."
 },
 {
  "id": "world-monitor",
  "org_id": "world-monitor",
  "name": "World Monitor",
  "url": "https://www.worldmonitor.app/ask?query=What%20is%20World%20Monitor%3F",
  "type": "origin",
  "implements": [
   "nlweb"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "nlweb",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "World Monitor",
    "role": "NLWeb site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "GET `https://www.worldmonitor.app/ask?query=What%20is%20World%20Monitor%3F` returned status 200 JSON with _meta.response_type `list`, _meta.version `0.1`, `query_id`, and `results`. The agent guide says `POST https://www.worldmonitor.app/ask` supports SSE.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://www.worldmonitor.app/ask?query=What%20is%20World%20Monitor%3F"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "recorded",
  "source": "https://www.worldmonitor.app/ask?query=What%20is%20World%20Monitor%3F",
  "note": "GET `https://www.worldmonitor.app/ask?query=What%20is%20World%20Monitor%3F` returned status 200 JSON with _meta.response_type `list`, _meta.version `0.1`, `query_id`, and `results`. The agent guide says `POST https://www.worldmonitor.app/ask` supports SSE."
 },
 {
  "id": "www-taskade-com",
  "org_id": "taskade",
  "name": "Taskade",
  "url": "https://www.taskade.com/",
  "type": "origin",
  "implements": [
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Taskade",
    "role": "Product site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "Negotiated `text/markdown; charset=utf-8` with `content-signal: ai-train=yes, search=yes, ai-input=yes` (`server: cloudflare`).",
    "full_detail_md": "Fetched with Markdown content negotiation on 2026-11-03, Taskade returned `HTTP/2 200` with `content-type: text/markdown; charset=utf-8`, `content-signal: ai-train=yes, search=yes, ai-input=yes`, a `vary` list that includes `accept`, and `server: cloudflare`. The page title is Turn Business Processes Into Live Apps, Taskade Genesis.",
    "facets": {
     "negotiation_or_artifact": "Live Accept negotiation of https://www.taskade.com/",
     "response_headers": "HTTP/2 200; content-signal ai-train=yes, search=yes, ai-input=yes; vary includes accept; server: cloudflare",
     "content_type_or_tokens": "text/markdown; charset=utf-8",
     "verification_posture": "Live HTTP probe checked 2026-11-03 (response date Tue, 03 Nov 2026 21:03:55 GMT)"
    },
    "telemetry": {
     "artifact_kind": "negotiated_markdown",
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "content_signal": "ai-train=yes, search=yes, ai-input=yes",
     "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding, accept",
     "server": "cloudflare",
     "marker": "content-type: text/markdown; charset=utf-8"
    },
    "source_url": "https://www.taskade.com/"
   }
  ],
  "observed": "2026-11-03",
  "date_basis": "source",
  "source": "https://www.taskade.com/",
  "note": "Negotiated `text/markdown; charset=utf-8` with `content-signal: ai-train=yes, search=yes, ai-input=yes` (`server: cloudflare`)."
 },
 {
  "id": "x402-go-sdk",
  "org_id": "x402-foundation",
  "name": "x402 Go SDK",
  "url": "https://pkg.go.dev/github.com/x402-foundation/x402/go/v2",
  "type": "sdk",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "x402 Go SDK",
    "role": "Reference SDK",
    "status": "Supported",
    "status_display": "Supported · as of 2026-11-04",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": "2026-11-04",
    "col4_md": "Reference `go/v2` module implementing EVM (`exact`, `upto`, `batch-settlement`, `auth-capture`) and SVM (`exact`, `upto`, `batch-settlement`, `paymentchannels`) packages.",
    "full_detail_md": "Official `github.com/x402-foundation/x402/go/v2` reference module providing client, server, and facilitator packages across EVM (`mechanisms/evm/exact`, `upto`, `batch-settlement`, `auth-capture`) and Solana SVM (`mechanisms/svm/exact`, `upto`, `batch-settlement`, `paymentchannels`).",
    "facets": {
     "settlement_rail": "x402 v2 `exact` scheme (`mechanisms/evm/exact` via EIP-3009 and `mechanisms/svm/exact`)",
     "supported_assets": "EVM ERC-20 tokens (EIP-3009) and Solana SPL tokens",
     "chains_or_networks": "EVM (`Ethereum Virtual Machine`) and SVM (`Solana Virtual Machine`)",
     "headers_or_methods": "`Newx402Client`, `Newx402ResourceServer`, `Newx402Facilitator`, HTTP transport wrappers, and spend controls"
    },
    "telemetry": null,
    "source_url": "https://pkg.go.dev/github.com/x402-foundation/x402/go/v2"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "source",
  "source": "https://pkg.go.dev/github.com/x402-foundation/x402/go/v2",
  "note": "Reference `go/v2` module implementing EVM (`exact`, `upto`, `batch-settlement`, `auth-capture`) and SVM (`exact`, `upto`, `batch-settlement`, `paymentchannels`) packages."
 },
 {
  "id": "x402scan",
  "org_id": "merit-systems",
  "name": "x402scan",
  "url": "https://github.com/Merit-Systems/x402scan",
  "type": "authority",
  "implements": [
   "x402"
  ],
  "archetypes": [
   "payments_onchain"
  ],
  "implementations": [
   {
    "protocol_id": "x402",
    "schema_id": "db4.payments_onchain.1",
    "archetype_slug": "payments_onchain",
    "side": "side_a",
    "actor": "x402scan",
    "role": "Ecosystem explorer",
    "status": "Listed",
    "status_display": "Listed · checked 2026-11-06",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-11-06",
    "as_of": null,
    "col4_md": "Explorer of x402 servers, volumes, and facilitator configuration.",
    "full_detail_md": "The repository describes an ecosystem explorer for x402 servers, transaction volumes, and embedded-wallet access, and says it is live at x402scan.com. Workspaces include the web application, a background sync service, and shared facilitator configuration.",
    "facets": null,
    "telemetry": null,
    "source_url": "https://github.com/Merit-Systems/x402scan"
   }
  ],
  "observed": "2026-11-06",
  "date_basis": "recorded",
  "source": "https://github.com/Merit-Systems/x402scan",
  "note": "Explorer of x402 servers, volumes, and facilitator configuration."
 },
 {
  "id": "xaa-dev-sandbox",
  "org_id": "okta",
  "name": "xaa.dev",
  "url": "https://xaa.dev/",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "xaa.dev",
    "role": "Cross App Access sandbox",
    "status": "Experimental",
    "status_display": "Experimental · as of 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "Open sandbox to learn and debug Cross App Access. The page says Cross App Access (XAA) implements OAuth Identity Assertion Authorization Grant (ID-JAG), and that a real identity provider can issue an ID-JAG, exchange it for an access token, and call a protected API.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": null,
    "source_url": "https://xaa.dev/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://xaa.dev/",
  "note": "Open sandbox to learn and debug Cross App Access. The page says Cross App Access (XAA) implements OAuth Identity Assertion Authorization Grant (ID-JAG), and that a real identity provider can issue an ID-JAG, exchange it for an access token, and call a protected API."
 },
 {
  "id": "xmatrix",
  "org_id": "xmatrix",
  "name": "xMatrix",
  "url": "https://github.com/GoogleCloudPlatform/open-knowledge-format/issues/37",
  "type": "sdk",
  "implements": [
   "okf"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "okf",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "xMatrix",
    "role": "Community implementation",
    "status": "Supported",
    "status_display": "Supported · as of 2026-10-12",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-12",
    "col4_md": "Issue #37 says xMatrix supports bidirectional OKF v0.2 Pages bundles.",
    "full_detail_md": "Issue #37, createdAt 2026-10-12T17:50:59Z, says xMatrix supports bidirectional OKF v0.2 bundles for its collaborative Pages and describes the note as a community implementation, not a request to imply Google endorsement.",
    "facets": {
     "artifact_or_endpoint": "xMatrix collaborative Pages OKF import and export",
     "content_type_or_schema": "Bidirectional OKF v0.2 bundles",
     "discovery_mechanism": "GitHub issue #37 on GoogleCloudPlatform/open-knowledge-format",
     "version_or_posture": "Community implementation naming OKF v0.2, opened 2026-10-12"
    },
    "telemetry": null,
    "source_url": "https://github.com/GoogleCloudPlatform/open-knowledge-format/issues/37"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://github.com/GoogleCloudPlatform/open-knowledge-format/issues/37",
  "note": "Issue #37 says xMatrix supports bidirectional OKF v0.2 Pages bundles."
 },
 {
  "id": "yoast-seo",
  "org_id": "yoast",
  "name": "Yoast SEO",
  "url": "https://yoast.com/features/llms-txt/",
  "type": "sdk",
  "implements": [
   "llms-txt"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "llms-txt",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Yoast SEO",
    "role": "WordPress SEO plugin",
    "status": "Supported",
    "status_display": "Supported · as of 2026-08-10",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-08-10",
    "col4_md": "WordPress plugin documented on `llmstxt.org` that automatically generates and maintains an `llms.txt` file.",
    "full_detail_md": "Listed in the `llmstxt.org` Integrations section as a WordPress SEO plugin that automatically generates and maintains a site-root `/llms.txt` file for WordPress installations.",
    "facets": {
     "artifact_path": "/llms.txt",
     "companion_files": "None stated",
     "content_type_or_bytes": "Generated Markdown index (CMS plugin)",
     "generator_or_consumer_mode": "WordPress plugin generating and maintaining /llms.txt"
    },
    "telemetry": null,
    "source_url": "https://llmstxt.org"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://llmstxt.org",
  "note": "WordPress plugin documented on `llmstxt.org` that automatically generates and maintains an `llms.txt` file."
 },
 {
  "id": "zed",
  "org_id": "zed",
  "name": "Zed",
  "url": "https://zed.dev/docs/ai/external-agents",
  "type": "harness",
  "implements": [
   "agent-client-protocol",
   "agents-md"
  ],
  "archetypes": [
   "harnesses_rpc_ui",
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "agent-client-protocol",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_b",
    "actor": "Zed",
    "role": "Native code editor client (co-steward)",
    "status": "Supported",
    "status_display": "Supported · as of 2026-01-28",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2026-01-28",
    "col4_md": "Native ACP client hosting `External Agents` in the `Agent Panel` with built-in `zed: acp registry`.",
    "full_detail_md": "Zed originated ACP and natively hosts ACP-compatible `External Agents` as subprocesses in the `Agent Panel` and `Threads Sidebar`, forwarding configured Zed MCP servers over ACP while providing built-in discovery and installation via `zed: acp registry` (launched 2026-01-28) and custom `agent_servers` settings.",
    "facets": {
     "role_in_acp": "Editor client and protocol co-steward",
     "integration_mode": "Native built-in ACP client and ACP Registry installer (zed: acp registry)",
     "transport": "JSON-RPC 2.0 over stdio subprocesses",
     "verification_posture": "First-party editor documentation & release announcements",
     "sdk_or_package": "Zed editor (External Agents / zed: acp registry)"
    },
    "telemetry": null,
    "source_url": "https://zed.dev/docs/ai/external-agents"
   },
   {
    "protocol_id": "agents-md",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_b",
    "actor": "Zed",
    "role": "IDE / Editor",
    "status": "Listed",
    "status_display": "Listed · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": null,
    "col4_md": "Named in the compatible coding-agent roster on `agents.md`.",
    "full_detail_md": "Listed on `agents.md` as a compatible AI coding editor (`Your agent definitions are compatible with a growing ecosystem of AI coding agents and tools`); native `AGENTS.md` file discovery and directory-precedence behavior are not independently verified in the cited documentation snapshots.",
    "facets": {
     "discovery_behavior": "Listed on agents.md — implementation behavior not independently verified",
     "hierarchy_precedence": "Not independently verified in cited documentation",
     "fallback_files": "Not independently verified in cited documentation",
     "verification_posture": "Listed on agents.md — implementation behavior not independently verified"
    },
    "telemetry": null,
    "source_url": "https://agents.md/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://zed.dev/docs/ai/external-agents",
  "note": "Native ACP client hosting `External Agents` in the `Agent Panel` with built-in `zed: acp registry`."
 },
 {
  "id": "zep-api-catalog",
  "org_id": "zep",
  "name": "Zep",
  "url": "https://www.getzep.com/.well-known/api-catalog",
  "type": "origin",
  "implements": [
   "api-catalog-rfc9727",
   "cloudflare-markdown-for-agents"
  ],
  "archetypes": [
   "web_discovery"
  ],
  "implementations": [
   {
    "protocol_id": "api-catalog-rfc9727",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Zep",
    "role": "Agent memory API & MCP catalog",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-04",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-04",
    "as_of": "2026-11-04",
    "col4_md": "`application/linkset+json` anchors `https://api.getzep.com/` with `service-doc`, `status`, and `related`, not `item`.",
    "full_detail_md": "On 2026-11-04, `https://www.getzep.com/.well-known/api-catalog` returned HTTP 200 (`content-type: application/linkset+json; charset=utf-8`, `content-length: 642`) with no profile parameter, no `Link` response header, and no `item` array. The anchor `https://api.getzep.com/` links `service-doc` to `https://help.getzep.com`, `status` to `https://status.getzep.com`, and `related` to `https://www.getzep.com/.well-known/mcp/server-card.json`.",
    "facets": {
     "well_known_endpoint": "https://www.getzep.com/.well-known/api-catalog",
     "content_type_or_profile": "application/linkset+json; charset=utf-8 (no profile parameter)",
     "link_relations": "service-doc (https://help.getzep.com); status (https://status.getzep.com); related (mcp/server-card.json); no item array",
     "http_or_link_header": "HTTP 200; no Link rel=api-catalog response header"
    },
    "telemetry": {
     "http_status": 200,
     "content_type": "application/linkset+json; charset=utf-8",
     "link_header_rel_api_catalog": false,
     "has_item_array": false
    },
    "source_url": "https://www.getzep.com/.well-known/api-catalog"
   },
   {
    "protocol_id": "cloudflare-markdown-for-agents",
    "schema_id": "db4.web_discovery.1",
    "archetype_slug": "web_discovery",
    "side": "side_a",
    "actor": "Zep",
    "role": "Product site",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-11-03",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-11-03",
    "as_of": "2026-11-03",
    "col4_md": "Negotiated `text/markdown; charset=utf-8` with `content-signal: ai-train=yes, search=yes, ai-input=yes` (`server: cloudflare`).",
    "full_detail_md": "Fetched with Markdown content negotiation on 2026-11-03, Zep returned `HTTP/2 200` with `content-type: text/markdown; charset=utf-8`, a `vary` list that includes `accept`, `content-signal: ai-train=yes, search=yes, ai-input=yes`, and `server: cloudflare`. The page says Zep unifies business data, documents, and conversations so agents have the context they need to complete tasks correctly.",
    "facets": {
     "negotiation_or_artifact": "Live Accept negotiation of https://www.getzep.com/",
     "response_headers": "HTTP/2 200; vary includes accept (rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding, accept); content-signal ai-train=yes, search=yes, ai-input=yes; server: cloudflare",
     "content_type_or_tokens": "text/markdown; charset=utf-8",
     "verification_posture": "Live HTTP probe checked 2026-11-03 (response date Tue, 03 Nov 2026 21:03:55 GMT)"
    },
    "telemetry": {
     "artifact_kind": "negotiated_markdown",
     "http_status": 200,
     "content_type": "text/markdown; charset=utf-8",
     "content_signal": "ai-train=yes, search=yes, ai-input=yes",
     "vary": "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding, accept",
     "server": "cloudflare",
     "marker": "content-type: text/markdown; charset=utf-8"
    },
    "source_url": "https://www.getzep.com/"
   }
  ],
  "observed": "2026-11-04",
  "date_basis": "source",
  "source": "https://www.getzep.com/.well-known/api-catalog",
  "note": "`application/linkset+json` anchors `https://api.getzep.com/` with `service-doc`, `status`, and `related`, not `item`."
 },
 {
  "id": "zillow",
  "org_id": "zillow",
  "name": "Zillow",
  "url": "https://www.zillow.com/news/zillow-becomes-first-real-estate-app-in-chatgpt/",
  "type": "origin",
  "implements": [
   "openai-apps-sdk-manifests"
  ],
  "archetypes": [
   "harnesses_rpc_ui"
  ],
  "implementations": [
   {
    "protocol_id": "openai-apps-sdk-manifests",
    "schema_id": "db4.harnesses_rpc_ui.1",
    "archetype_slug": "harnesses_rpc_ui",
    "side": "side_a",
    "actor": "Zillow",
    "role": "ChatGPT app",
    "status": "Supported",
    "status_display": "Supported · as of 2025-10-06",
    "support_level": "full",
    "probe_mode": "doc_citation",
    "checked_on": "2026-10-30",
    "as_of": "2025-10-06",
    "col4_md": "Live for logged-in U.S. users on Free, Plus, and Pro, and named in the launch set.",
    "full_detail_md": "Zillow's announcement, datePublished 2025-10-06, says the Zillow App in ChatGPT is live for logged-in ChatGPT users in the U.S. on Free, Plus and Pro plans. The Verge includes Zillow in the apps available inside ChatGPT at launch.",
    "facets": {
     "transport_or_manifest": "Vendor announcement; no plugin.json cited on this row",
     "ui_or_widget_surface": "Zillow App inside ChatGPT",
     "auth_or_permissions": "Logged-in ChatGPT users on Free, Plus, and Pro plans",
     "sdk_or_version": "Live at launch, datePublished 2025-10-06; U.S. availability"
    },
    "telemetry": null,
    "source_url": "https://www.zillow.com/news/zillow-becomes-first-real-estate-app-in-chatgpt/"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://www.zillow.com/news/zillow-becomes-first-real-estate-app-in-chatgpt/",
  "note": "Live for logged-in U.S. users on Free, Plus, and Pro, and named in the launch set."
 },
 {
  "id": "zuplo-as-cimd",
  "org_id": "zuplo",
  "name": "Zuplo authorization server",
  "url": "https://auth.zuplo.com",
  "type": "authority",
  "implements": [
   "oauth-cimd"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "oauth-cimd",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_b",
    "actor": "Zuplo",
    "role": "Authorization server",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "full",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "HTTP 200; flag true; `issuer` `https://auth.zuplo.com/`.",
    "full_detail_md": "The HTTP 200 JSON from `https://zuplo.com/.well-known/oauth-authorization-server` sets `client_id_metadata_document_supported` true, with `issuer` `https://auth.zuplo.com/`, `authorization_endpoint` `https://auth.zuplo.com/authorize`, and `token_endpoint` `https://auth.zuplo.com/oauth/token`. Checked 2026-10-30.",
    "facets": {
     "metadata_flag_or_profile": "client_id_metadata_document_supported true; issuer https://auth.zuplo.com/ differs from the zuplo.com metadata host",
     "auth_method_or_pkce": "code_challenge_methods_supported includes S256 and plain; grant_types_supported includes authorization_code and refresh_token",
     "uri_or_ssrf_rules": "authorization_endpoint https://auth.zuplo.com/authorize and token_endpoint https://auth.zuplo.com/oauth/token",
     "draft_or_spec_version": "Live authorization-server metadata checked 2026-10-30; the JSON does not name a CIMD draft revision"
    },
    "telemetry": {
     "http_status": 200,
     "client_id_metadata_document_supported": true,
     "issuer": "https://auth.zuplo.com/"
    },
    "source_url": "https://zuplo.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://zuplo.com/.well-known/oauth-authorization-server",
  "note": "HTTP 200; flag true; `issuer` `https://auth.zuplo.com/`."
 },
 {
  "id": "zuplo-auth",
  "org_id": "zuplo",
  "name": "Zuplo Auth",
  "url": "https://auth.zuplo.com/",
  "type": "authority",
  "implements": [
   "identity-assertion-authz-grant"
  ],
  "archetypes": [
   "identity_auth_crypto"
  ],
  "implementations": [
   {
    "protocol_id": "identity-assertion-authz-grant",
    "schema_id": "db4.identity_auth_crypto.1",
    "archetype_slug": "identity_auth_crypto",
    "side": "side_a",
    "actor": "Zuplo",
    "role": "Authorization server (auth.zuplo.com)",
    "status": "Live (HTTP 200)",
    "status_display": "Live (HTTP 200) · checked 2026-10-30",
    "support_level": "partial",
    "probe_mode": "http_probe",
    "checked_on": "2026-10-30",
    "as_of": "2026-10-30",
    "col4_md": "`https://zuplo.com/.well-known/oauth-authorization-server` returned HTTP 200. The issuer is `https://auth.zuplo.com/`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer` and `urn:ietf:params:oauth:grant-type:token-exchange`. `client_id_metadata_document_supported` is true.",
    "full_detail_md": null,
    "facets": null,
    "telemetry": {
     "http_status": 200,
     "content_type": "application/json",
     "issuer": "https://auth.zuplo.com/",
     "grant_profile": "urn:ietf:params:oauth:grant-profile:id-jag"
    },
    "source_url": "https://zuplo.com/.well-known/oauth-authorization-server"
   }
  ],
  "observed": "2026-10-30",
  "date_basis": "source",
  "source": "https://zuplo.com/.well-known/oauth-authorization-server",
  "note": "`https://zuplo.com/.well-known/oauth-authorization-server` returned HTTP 200. The issuer is `https://auth.zuplo.com/`. `authorization_grant_profiles_supported` lists `urn:ietf:params:oauth:grant-profile:id-jag`. `grant_types_supported` includes `urn:ietf:params:oauth:grant-type:jwt-bearer` and `urn:ietf:params:oauth:grant-type:token-exchange`. `client_id_metadata_document_supported` is true."
 }
]