Conformant servers claim a conformance level via their /.well-known/webgcp descriptor. Levels are self-declared and externally verifiable against the public fixtures.
| Implementation | Operator | Status | First attained |
|---|---|---|---|
| webgcp.org | webgcp.org spec maintainers | L0 — first publicly-deployed SVCB host (self-conformant) | 2026-05-16 |
| news.energypager.com (formerly the-ai-news.web.app) | The AI News (independent operator) | L0 — first non-author full-L0 implementation | 2026-05-16 |
webgcp.org is both the spec host AND the first publicly-deployed host honoring §5.1.1's DNS-layer SVCB MUST. Its own spec-host descriptor at https://webgcp.org/.well-known/webgcp declares this_host_svcb_status: "live 2026-05-16". The spec is self-conformant — the L0-003 fixture verifies against itself. An agent doing a DNS query at _webgcp.<any-domain> can find webgcp.org as a webGCP authority in sub-millisecond, no HTTPS round-trip needed for discovery.
Verifiable via Cloudflare DoH (the primary verifier; Google DoH has been observed to return empty Answer for SVCB):
curl -H 'Accept: application/dns-json' \ 'https://cloudflare-dns.com/dns-query?name=_webgcp.webgcp.org&type=64' | jq .Answer
Because webgcp.org is the spec host (role: specification_authority), not a knowledge server, its descriptor does not carry conformance_level: Lx. The §5.1.1 SVCB MUST applies to any host serving the descriptor — spec hosts included. See /dns-setup/svcb-at-squarespace/ for the operator-facing setup guide derived from this deployment.
The first independent (non-author) host to satisfy every L0 MUST, including the §5.1.1 DNS-layer SVCB MUST. Operated by The AI News (an arm's-length internal team), it serves an RSS-aggregated AI-news corpus. It began as the-ai-news.web.app at L0-restricted-domain (Firebase's .web.app zone gives no authoritative DNS control, so SVCB could not be published); on 2026-06-26 the operator attached the DNS-controllable custom domain news.energypager.com and published the SVCB record, clearing the restricted-domain caveat and upgrading to plain L0. the-ai-news.web.app now 301-redirects here; the former urn:webgcp:the-ai-news.web.app:* contract URIs are retired in favor of urn:webgcp:news.energypager.com:*.
What news.energypager.com ships at L0:
news-kb-v0.1 (AI news corpus, RSS-aggregated, 15-minute refresh)news-article-retrieval-v0.1POST https://news.energypager.com/webgcp/v0/query_webgcp.news.energypager.com → news.energypager.com (priority 1, ServiceMode)Maintainer verification (2026-06-26). The spec maintainers independently verified all three L0 fixtures against news.energypager.com: the descriptor returns 200 application/json; POST /webgcp/v0/query returns a typed bundle with _meta provenance (and out_of_scope / manifest_mismatch typed failures per §6.7); and the SVCB record resolves at _webgcp.news.energypager.com via Cloudflare DoH (type 64). This completes the second-implementer test (a non-author full-L0 server) — see spec §13. During an earlier window (2026-05-21–06-25) the query endpoint was briefly offline; the operator's descriptor honestly flagged query_endpoint_status: offline-temporary rather than overclaiming — the conformance discipline this registry expects.
Try it:
curl -X POST https://news.energypager.com/webgcp/v0/query \
-H 'Content-Type: application/json' \
-d '{
"bundle": {"contract_uri": "urn:webgcp:news.energypager.com:news-article-retrieval/v0.1"},
"filter": {"query": "transformer", "max_results": 3},
"scope": {"allow_kbs": ["urn:webgcp:news.energypager.com:*"]}
}' | jq
curl -H 'Accept: application/dns-json' \ 'https://cloudflare-dns.com/dns-query?name=_webgcp.news.energypager.com&type=64' | jq .Answer
The-ai-news also runs a separate Commerce layer (x402 USDC settlement, agent marketplace, graph-authority routing) — per spec §0.5, Context (this protocol) and Commerce are composing layers that share an operator but neither subsumes the other.
| Implementation | Operator | Status | Gating event |
|---|---|---|---|
| MyParallel catalog (BigQuery-backed) | The Network catalog team | in-build | M3a backend MCP server deployment |
| mpos — OS provisioning (agenticOS L4 writer) | The Network / agenticOS | in-build | writer-core port + provision() contract |
The catalog operates a publicly readable BigQuery dataset (webgcporg.catalog, 19 tables, 230 agencies + 29 skills with 3072-d embeddings) that targets L1 conformance. The substrate is live; the query endpoint is in active build.
agenticOS is the reference substrate implementing webGCP across two surfaces. The catalog (above) is the matching / knowledge plane. mpos is the OS-provisioning plane: it treats a signed OS image as an ordinary webGCP content-addressed artifact with a typed urn:webgcp: node identity, fetched and verified the same way a knowledge bundle is — fetch + verify, with a device as the write target. Its verify-before-write step (the TrustRoot seam) implements webGCP's signed-bundle / provenance requirement. This requires no new profile: OS provisioning is an L4 write-target adapter over the existing v0.1 Context / artifact contract — the protocol spec is unchanged.
Ship a conformant server, host a /.well-known/webgcp descriptor on it, then open an issue via the contact in webgcp.org's own descriptor. The second non-author implementation completes the second-implementer test — the gating event for v1.0 promotion.