generated: '2026-08-23'
method: probed
source: live GET of each /.well-known/ path on every Kargo host in apis.yml
hit_count: 3
hosts:
- host: https://www.kargo.ai
  documents:
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/oauth-authorization-server
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/ai-plugin.json
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
- host: https://api.kargo.zone
  documents:
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/oauth-authorization-server
    status: 404
  - path: /.well-known/oauth-protected-resource
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/ai-plugin.json
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
- host: https://docs.kargo.ai
  documents:
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/openid-configuration
    status: 404
  - path: /.well-known/api-catalog
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
  - path: /.well-known/agent.json
    status: 404
  - path: /llms.txt
    status: 404
- host: https://mykargo.us.auth0.com
  note: 'Kargo''s own Auth0 tenant. This is the authorization server Kargo''s
    authentication documentation instructs every API client to call
    (https://mykargo.us.auth0.com/oauth/token, audience
    https://api.kargo.zone/public_graphql). The discovery documents below are served
    on Kargo''s behalf by Auth0 at Kargo''s tenant hostname, not on a kargo.ai or
    kargo.zone domain.'
  documents:
  - path: /.well-known/openid-configuration
    status: 200
    file: kargo-openid-configuration.json
  - path: /.well-known/oauth-authorization-server
    status: 200
    file: kargo-oauth-authorization-server.json
  - path: /.well-known/jwks.json
    status: 200
    note: 'Served (HTTP 200). Not saved: signing keys rotate and a snapshot would be
      stale and misleading.'
  - path: /.well-known/security.txt
    status: 404
  - path: /.well-known/agent-card.json
    status: 404
findings:
- 'No security.txt on any Kargo-controlled host.'
- 'No /.well-known/api-catalog on any host.'
- 'No A2A agent card at either /.well-known/agent-card.json or the legacy
  /.well-known/agent.json on any host, so no a2a/ artifact was written.'
- 'No llms.txt published by Kargo; llms/kargo-llms.txt in this repo is generated by
  API Evangelist, not served by Kargo.'
- 'www.kargo.ai returns a soft-404 SPA shell body (198,104 bytes) with an HTTP 404
  status on every /.well-known/ path, so no path there was treated as a hit.'