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 ai.artemisgtm/gtm-engineer's discovery endpoints

ai.artemisgtm/gtm-engineer · 2026-10-25 · 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 verified (unsigned)

EntryGET on the publisher's well-known discovery paths
Actionsserved Agent2Agent (A2A) document
Egressno
Human approval—
Secrets touchedno
Bundlebundles/tr_st_9135a2dae8536e0e_1addecb8 · sha256:d6b2f3497af70aa25e287d898ed03e8085ca8ae0a48345ae1dc5a7e104c33545 · download (JSON)
Chainsha256:5e4daabf2287d3ce484dd35fa006e596b1f6cf67913f5278dc3f29a96370003c
prev sha256:4bed06f126bc3a791c258116a75c659f1d51c9724ee94dab514119ab39d0c916

Transcript

# Probe transcript — ai.artemisgtm/gtm-engineer

Agent `res_9135a2dae8536e0e` · publisher domain `artemisgtm.ai` · 2026-10-25 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://artemisgtm.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3.0 (card 2026-10-25)
- signed: no
- skills advertised: Describe the firm, List the systems, Recommend an engagement, Book an evaluation, Get the guides

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