generated: '2026-08-30'
method: probed
source: live HTTP probes of https://agentgateway.dev/.well-known/*
description: >-
  Well-known document probe for the agentgateway host. Every path returned HTTP 404 with the site's
  Next.js 404 page. No /.well-known document is served, so NO WellKnown or SecurityTxt pointer is
  emitted in apis.yml - this file records a verified absence, not a presence. Note that agentgateway
  itself GENERATES /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server
  responses for the MCP servers it fronts (see conformance/agentgateway-conformance.yml); those are
  served by a user's own deployment, never by agentgateway.dev.
hosts:
  - host: agentgateway.dev
    documents:
      - path: /.well-known/security.txt
        status: 404
        file: null
      - path: /.well-known/openid-configuration
        status: 404
        file: null
      - path: /.well-known/oauth-authorization-server
        status: 404
        file: null
      - path: /.well-known/oauth-protected-resource
        status: 404
        file: null
      - path: /.well-known/api-catalog
        status: 404
        file: null
      - path: /.well-known/ai-plugin.json
        status: 404
        file: null
      - path: /.well-known/agent-card.json
        status: 404
        file: null
      - path: /.well-known/agent.json
        status: 404
        file: null
related:
  - path: /llms.txt
    status: 200
    note: Served, and captured verbatim at llms/agentgateway-llms.txt. Not a /.well-known document.
  - path: /robots.txt
    status: 200
  - path: /sitemap.xml
    status: 200
  - path: /schema/config
    status: 200
    note: >-
      First-party JSON Schema (draft 2020-12, title LocalConfig, 302 $defs) for the agentgateway
      configuration file. Saved verbatim to json-schema/agentgateway-config-schema.json.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com