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 BlitzAPI's discovery endpoints

BlitzAPI · 2026-10-19 · 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_2a2c3011f4749d28_06a3b725 · sha256:64177f3abb54a33b28f60158550e889557c508c862d2eabafe460cad741399bb · download (JSON)
Chainsha256:98fd4b55a63289cf0ad5684b5a528c910bf0cef2ef9bd3089c4619a238d53df3
prev sha256:f600d7e28af284932c6f0b679b1be8723944d5c4fd98a82c11e841afd1a0d73d

Transcript

# Probe transcript — BlitzAPI

Agent `res_2a2c3011f4749d28` · publisher domain `docs.blitz-api.ai` · 2026-10-19 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://docs.blitz-api.ai/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3 (card 1.0.0)
- signed: no
- skills advertised: blitzapi

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