Registry probe of hyperframes's discovery endpoints

hyperframes · 2026-10-26 · AgentDossier refresh · harness probe-1.0

Scenario. Fetch and validate the ARD manifest, A2A agent card and MCP server card at the publisher's well-known paths

Observed. A2A invalid (unsigned; 1 validation error)

Transcript

# Probe transcript — hyperframes

Agent `res_48b7b3d0e9e6860a` · publisher domain `hyperframes.heygen.com` · 2026-10-26 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://hyperframes.heygen.com/.well-known/agent-card.json`
- result: **invalid**
- declared version: 0.3 (card 1.0.0)
- signed: no
- skills advertised: hyperframes
- validation error: missing 'description'

---
Observation only: the registry fetched public well-known paths and validated the documents against the protocol specifications. No credentials, no message exchange beyond discovery, nothing written.

Produced automatically on every refresh; a new bundle is written only when the observation changes

A trace describes one version on one date. It is evidence of behaviour, never a certification. Dispute it through the agent's dossier; corrections are appended, never overwritten.