generated: '2026-08-13'
method: probed
source: >-
  live GET of /.well-known/* against every host named in apis.yml and in the
  OpenAPI servers[] blocks, 2026-08-13
note: >-
  developer.goacoustic.com is a ReadMe-hosted single-page docs site (meta
  readme-deploy 5.846.0) whose catch-all answers HTTP 200 with a 740,863-byte HTML
  shell for ANY unknown path — /openapi.json, /swagger.json, /.well-known/security.txt,
  /.well-known/agent-card.json and /.well-known/agent.json all return that same shell.
  Exactly ONE /.well-known/ path on that host returns a real document: /.well-known/api-catalog,
  served as application/linkset+json. Everything else recorded below as status 200 with
  hit:false is the SPA shell and is a MISS, not a presence. No SecurityTxt pointer and no
  AgentCard artifact were written.
hosts:
- host: https://developer.goacoustic.com
  documents:
  - path: /.well-known/api-catalog
    status: 200
    content_type: application/linkset+json
    file: silverpop-api-catalog.json
    hit: true
    note: >-
      A genuine RFC 9727 linkset with six anchors — acoustic-connect, acoustic-campaign,
      acoustic-content, acoustic-exp-analytics, acoustic-exchange and
      acoustic-personalization. Acoustic Campaign is the direct descendant of the
      Silverpop Engage API this profile covers. Each anchor advertises a per-product
      service-desc at /<product>/.well-known/api-catalog; the acoustic-campaign one was
      probed and returns 404, so the catalog resolves one level only and never reaches a
      machine-readable service description.
  - path: /.well-known/security.txt
    status: 200
    content_type: text/html
    hit: false
    note: SPA shell, not an RFC 9116 document.
  - path: /.well-known/agent-card.json
    status: 200
    content_type: text/html
    hit: false
    note: SPA shell. Not an A2A AgentCard — no a2a/ artifact written.
  - path: /.well-known/agent.json
    status: 200
    content_type: text/html
    hit: false
    note: SPA shell. Legacy pre-0.3 AgentCard path also a miss.
  - path: /.well-known/ai-plugin.json
    status: 200
    content_type: text/html
    hit: false
    note: SPA shell.
  - path: /.well-known/openid-configuration
    status: 404
    hit: false
  - path: /.well-known/oauth-authorization-server
    status: 404
    hit: false
  - path: /llms.txt
    status: 404
    hit: false
    note: >-
      Also probed /acoustic-campaign/llms.txt — 404. The developer portal publishes no
      llms.txt; llms/silverpop-llms.txt in this repo is GENERATED by API Evangelist, not
      served by the provider.
- host: https://api-campaign-us-1.goacoustic.com
  note: >-
    The production API pod. Every /.well-known/* path returns HTTP 404 from the Engage
    error page (text/html;charset=ISO-8859-1). This host does serve a real legacy service
    description at /restdoc/<resource> (Swagger 1.1) — see conformance/silverpop-conformance.yml.
  documents:
  - path: /.well-known/security.txt
    status: 404
    hit: false
  - path: /.well-known/openid-configuration
    status: 404
    hit: false
  - path: /.well-known/oauth-authorization-server
    status: 404
    hit: false
  - path: /.well-known/api-catalog
    status: 404
    hit: false
  - path: /.well-known/ai-plugin.json
    status: 404
    hit: false
  - path: /.well-known/agent-card.json
    status: 404
    hit: false
  - path: /.well-known/agent.json
    status: 404
    hit: false
- host: https://www.acoustic.com
  note: >-
    The corporate site the silverpop.com domain now 301s to. Serves a real llms.txt but
    no /.well-known/ documents.
  documents:
  - path: /.well-known/security.txt
    status: 404
    hit: false
  - path: /security.txt
    status: 404
    hit: false
  - path: /.well-known/agent-card.json
    status: 404
    hit: false
summary:
  paths_probed: 18
  real_documents: 1
  soft_200_html_shells: 5
  security_txt: false
  openid_configuration: false
  agent_card: false