# A2A Agent Card Monitor – Skills & Contract Changes — workflow

## Choose this tool

For AI integration agencies, agent directory operators and developers maintaining a shortlist of public A2A services.

Useful output columns: `title`, `agentVersion`, `protocolFamily`, `skillCount`, `skills`, `interfaces`, `securitySchemes`, `addedSkills`, `removedSkills`.

## Practical workflow

Read only public well-known Agent Cards, normalize their declared capabilities and compare complete observations before reviewing an integration change.

## Check the fit

Reads public metadata only; it never invokes a skill, performs a payment, or requests a protected extended card. Advertised capabilities and signatures are not executed or cryptographically verified. Only standard and legacy well-known paths, no query strings, redirects, credentials or private-network targets.

## Real output sample

One selected row from a 2026-11-21 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: xmYqtAtOUGgOHnLg8. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "a2a-card:d38c0fb53fd987ffc9d1755bca5e2bfb9d4e022e614a268d425e75fefe3104d9",
  "title": "ACN Preflight",
  "agentVersion": "1.1.0",
  "protocolFamily": "1.x",
  "skillCount": 3,
  "interfacesChanged": null,
  "authChanged": null,
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://preflight.abacore.net/.well-known/agent-card.json",
  "url": "https://preflight.abacore.net/.well-known/agent-card.json",
  "observedAt": "2026-11-21T20:18:42.244Z"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [MCP Registry Monitor - AI Integrations & Version Changes](https://mayd-it.com/data-tools/actors/mcp-registry-change-monitor/)

Maintain separate evidence for A2A agent contracts and MCP server registrations.

1. Review changed skills, versions and interface declarations in the public Agent Card.
2. Run the MCP registry monitor for separately selected relevant MCP servers.
3. Use both exports to maintain an integration inventory with source and observation timestamps.

A2A and MCP are different protocols. A declared capability or registry entry is not proof that execution works; no agent invocation is performed.

### [OpenAPI Contract Monitor - Operation & Schema Changes](https://mayd-it.com/data-tools/actors/openapi-operation-change-monitor/)

Review API contract changes for services that also expose public OpenAPI descriptions.

1. Identify a changed agent's public service interface from your own integration documentation.
2. Provide a verified public OpenAPI document URL to the OpenAPI monitor.
3. Compare the two contract-change reports before testing your integration.

An Agent Card URL is not an OpenAPI document. Do not automatically follow untrusted card links or transmit credentials.
