generated: '2026-08-13'
method: probed
source: https://docs.segmentstream.com/.well-known/agent-card.json
discovery:
  path: /.well-known/agent-card.json
  canonical: true
  host: docs.segmentstream.com
  note: >-
    Served from the documentation host, not the apex or the MCP host. The apex
    (segmentstream.com), the MCP host (mcp.segmentstream.com) and the API host
    (api.segmentstream.com) all 404 both the canonical
    /.well-known/agent-card.json and the legacy /.well-known/agent.json.
conformance:
  spec: A2A 1.0.0
  grade: flavored
  protocol_version: '0.3'
  preferred_transport: HTTP+JSON
  hard_checks:
    capabilities_is_object: true
    protocol_version_present: true
    skills_is_array: true
  deviations:
    - supported-interfaces-not-additional-interfaces
    - protocol-version-0.3-not-1.0
  note: >-
    All three A2A 1.0.0 hard checks pass (capabilities is an object,
    protocolVersion is present, skills is an array) and every optional field the
    grade considers is present (preferredTransport, defaultInputModes,
    defaultOutputModes). It is graded `flavored` on the enrichment rubric
    because the card declares its transports under `supportedInterfaces`, the
    pre-1.0 key, rather than the A2A 1.0.0 `additionalInterfaces`, and pins
    protocolVersion 0.3. Renaming that one key and bumping protocolVersion would
    make this a conformant card.
card:
  name: SegmentStream
  url: https://docs.segmentstream.com/
  version: 1.0.0
  organization: SegmentStream
  documentation_url: https://docs.segmentstream.com/
  capabilities:
    streaming: false
    pushNotifications: false
  default_input_modes: [text/plain]
  default_output_modes: [text/plain]
  skills: 1
  file: segmentstream-agent-card.json
skills:
  - id: segmentstream
    name: Segmentstream
    url: https://docs.segmentstream.com/.well-known/agent-skills/segmentstream/skill.md
    description: >-
      Use when building marketing attribution models, analyzing campaign
      performance, optimizing budget allocation across channels, configuring
      event tracking and data sources, or querying attribution data through
      natural language via MCP.
    note: >-
      This skill URL resolves (HTTP 200, text/markdown, 15,102 bytes) and is
      saved verbatim at skills/segmentstream-provider-skill.md. The agent card
      is therefore a working discovery chain, not a dangling pointer.
x-evidence:
  fetched: '2026-08-13'
  url: https://docs.segmentstream.com/.well-known/agent-card.json
  http_status: 200
  content_type: application/json
  bytes: 932
  negative_probes:
    - url: https://segmentstream.com/.well-known/agent-card.json
      http_status: 404
    - url: https://segmentstream.com/.well-known/agent.json
      http_status: 404
    - url: https://mcp.segmentstream.com/.well-known/agent-card.json
      http_status: 404
    - url: https://mcp.segmentstream.com/.well-known/agent.json
      http_status: 404
    - url: https://api.segmentstream.com/.well-known/agent-card.json
      http_status: 404
    - url: https://docs.segmentstream.com/.well-known/agent.json
      http_status: 404