generated: '2026-08-13' method: probed source: https://www.vidyard.com/.well-known/agent-card.json discovery: path: /.well-known/agent-card.json canonical: true host: www.vidyard.com note: > Served from the Vidyard marketing origin (WP Engine behind Cloudflare) with content-type application/json and access-control-allow-origin *. The same path 404s on api.vidyard.com and developer.vidyard.com; the legacy /.well-known/agent.json path 404s on every Vidyard host. conformance: spec: A2A 1.0.0 grade: near-conformant protocol_version: 1.0.0 preferred_transport: null hard_checks: capabilities_is_object: true protocol_version_present: true skills_is_array: true deviations: - no-preferredTransport - url-is-a-contact-page-not-an-agent-endpoint note: > All three hard checks pass. Graded near-conformant because the optional preferredTransport field is absent. A second, more consequential deviation: card.url resolves to https://www.vidyard.com/contact-us/ — a human sales contact page, not a JSON-RPC agent endpoint — so the card is a capability declaration and discovery manifest rather than a callable A2A surface. No A2A transport endpoint is advertised anywhere in the document. card: name: Vidyard description: > Vidyard is an AI-powered video platform that helps sales, marketing, and customer success teams create, automate, and track personalized video across the customer journey. url: https://www.vidyard.com/contact-us/ version: 1.0.0 provider: organization: Vidyard url: https://www.vidyard.com capabilities: streaming: false pushNotifications: false default_input_modes: - text/plain default_output_modes: - text/html - text/markdown skills: 8 skill_ids: - record-video-messages - ai-avatar-videos - automated-video-sends - video-hosting - video-embeds - engagement-tracking - crm-engagement-sync - video-personalization file: vidyard-agent-card.json x-evidence: fetched: '2026-08-13' url: https://www.vidyard.com/.well-known/agent-card.json http_status: 200 content_type: application/json; charset=utf-8