machinerealms.com

MachineRealms

Card: https://machinerealms.com/.well-known/agent-card.json
Watched since 2026-10-15, listed by a2aregistry.org.

Last check, 2026-11-01 02:50 UTC: warn

• warn looks like an A2A 0.3 card (top-level url, preferredTransport, additionalInterfaces, protocolVersion); v1.0 lists endpoints in 'supportedInterfaces'
• warn v1.0 JSON uses camelCase; these keys are snake_case: x-machine-realms-a2a-compatibility.canonical_model, x-machine-realms-a2a-compatibility.aliases_are_deprecated_discovery_compatibility_only, x-machine-realms-a2a-compatibility.canonical_protocol_version_source, research_commons, research_commons.h…
• info endpoint https://machinerealms.com/a2a answers JSON-RPC and reports an unknown task correctly (-32001)
• warn endpoint https://machinerealms.com/a2a/v1 answered GET .../tasks/{id} with 404 but no TASK_NOT_FOUND error body, so a client cannot tell a missing task from a missing route

Last 30 days (watched since 2026-10-15): answered on 18 of 18 days checked, probe passed on 18. Our check took a median 0.7s (card fetch plus probes, from our server — not the agent's own latency). Card signature: none.

Daily history, last 90 days

One mark per day we checked: green probe passed, amber card answered, red did not answer. Days without a check are not shown.