OpenA2A/specs
Lab/ATX

Verify a credential locally, with cached keys

ATX is the credential face: AIP proves the key, ATP logs the trust, and ATX packs all of it into one signed, self-contained credential the agent carries and any verifier checks locally.

Interactive lab · 3 of 5 in the familystart
the problem

Before the spec: the usual way

The usual way: on every call, ask a central authority 'is this agent still trusted?'. The request blocks on the network, latency climbs, and if the authority is down, trust breaks.

Network monitoroutbound
→ trust-registry.example/verifyblocking call, every single request
verification latency (illustrative)~180 ms
Local, no network

nothing yet

What is real here

The credential is the ATX 1.1 baseline fixture of the atx-conformance suite, byte for byte. Its Ed25519 signature is verified for real in your browser over JCS(TBS), the bytes core.md §1.3a.2 defines, against the issuer key the suite pins, so tampering any signed field fails. This fixture carries no ML-DSA-65 post-quantum signature; a hybrid credential adds one over the same bytes, and the Adversary Console verifies it. Revocation is a locally cached list plus a short credential lifetime, not a live lookup. A declared purpose (declaredPurpose) is an optional ATX 1.1 field; a 1.0 verifier ignores it.

Copy as codeVerify an ATX with @opena2a/atx-verify (published), no network
import { LocalAtxVerifier } from "@opena2a/atx-verify";

// Local check against injected anchors: version, expiry, revocation, issuer trust
// and the Ed25519 signature. The library does no I/O.
const verifier = new LocalAtxVerifier({
  trustedIssuers: ["did:opena2a:authority:opena2a.org"],
  publicKeys: cachedIssuerKeys,  // e.g. from the issuer's DID Document, 1-hour TTL
  crl: localRevocationCache,     // 5-minute TTL
});
const result = verifier.verify(credential);
if (result.valid) proceed();     // local check against the cached keys and revocation list
Next in the chain4 of 5: Make trust auditable, so an edit breaks the root→