Reference implementation Data compiled from public sources as of 2026-10-26. Not an assessment, certification or recommendation. Confirm current status with the vendor and the issuing body.
Trace · registry probe · T1 reproducible run

Registry probe of kortix's discovery endpoints

kortix · 2026-10-12 · 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. ARD invalid (1 validation error)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agentic Resource Discovery (ARD) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_1d3a09de74569615_e790785b · sha256:4c72215837bbdce8692571826f32348a1b8dfc8a0ab3657b25193f3f3f376820 · download (JSON)
Chainsha256:493b587f67bbc88ca7556911bf6da1a2c67044e2575ec02288fc3d17a715e5e9
prev sha256:145a5cf6c01643d6496bb64663f7b3e0a53afe35a2e6ce346ca8048415074cad

Transcript

# Probe transcript — kortix

Agent `res_1d3a09de74569615` · publisher domain `kortix.com` · 2026-10-12 · harness probe-1.0

## Agentic Resource Discovery (ARD)

- requested `https://kortix.com/.well-known/ai-catalog.json`
- result: **invalid**
- validation error: missing required term 'displayName'
- warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search)

---
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.