The A2A AgentCard export is a public-discovery surface that projects a Mnemom-composed canonical alignment card into the A2A AgentCard v1.x envelope. The endpoint is unauthenticated: any consumer can fetch it; per-agent opt-in keeps the surface explicit. The export is one-way. Mnemom doesn’t accept inbound A2A registration in v1; that’s deferred to a future phase. The export pattern is the standard “publish for discovery” half of A2A.Documentation Index
Fetch the complete documentation index at: https://docs.mnemom.ai/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
| Property | Value |
|---|---|
| Auth | None — public surface |
| Per-agent gate | agents.a2a_export_enabled — when false, the endpoint returns 404 (not 403) to avoid leaking which agents exist on the platform |
| Caching | Cache-Control: public, max-age=60, stale-while-revalidate=300 |
| ETag | "sha256:<canonical content_hash>" — clients can issue If-None-Match for cheap revalidation |
| CORS | * — the endpoint is intentionally cross-origin |
What the projection includes
| Field | Source |
|---|---|
name | principal.identifier from the alignment card; falls back to agent_id |
description | Care-framed summary of the first six declared values |
version | 1.<canonical version>.0 (semver shape) |
skills | First 50 entries of autonomy.bounded_actions |
extensions[aap/attestation] | Present when AAP_ATTESTATION_SIGNING_ENABLED=true; soft-omits on signing error |
extensions[aap/alignment] | Public-safe subset of the canonical card |
What the projection deliberately excludes
The public-discovery surface filters operator-internal fields:card_id(smolt-internal)_composition.source_card_id/_composition.source_policy_idfield_provenance(caller-aware redaction is server-side; A2A consumers don’t get a redacted view, they get no view)- Internal connector grants beyond the bare tool name surface
GET /v1/agents/{id}/state under an authenticated principal.
Opt-in
Agents default to opted out. An org admin flips the per-agent flag:Verifying the embedded attestation
Any A2A consumer can extract theextensions[aap/attestation].body.token and verify it offline against the published JWKS. The mnemom verify-card CLI does this for you in one command:
See also
- AAP attestation tokens — the JWS extension
- Transparency log — durable historic verification
mnemom verify-card— offline verification CLI- Card lifecycle — where the export fits in the lifecycle