May’d It
A2A Agent Card Monitor — illustrative workflow

DATA TOOLS / ai

A2A Agent Card Monitor – Skills & Contract Changes

Monitor public A2A Agent Cards for skill, interface, version and advertised authentication changes. Export source-linked contract snapshots without invoking agents or accessing protected cards.

JSON / CSV outputLimited permissionsSource: maydit/a2a-agent-card-change-monitor

FROM SOURCE TO A USEFUL RESULT

A practical workflow

Choose this tool when…

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

titleagentVersionprotocolFamilyskillCountskillsinterfacessecuritySchemesaddedSkillsremovedSkills

Did a remote AI agent change its public skills, interfaces or authentication contract?

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

Check the fit and source limits

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.

Download this workflow as Markdown · Configure a small first run

REAL RUN · DATED EVIDENCE

See an actual saved result

Captured 2026-11-21. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.

{
  "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"
}

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health. Run reference: xmYqtAtOUGgOHnLg8. Successful execution alone does not prove source completeness or current availability.

START SMALL

Example input

Historical evidence for this exact JSON was recorded 2026-11-21 on its original build. This is not a fresh source-availability test. Adjust targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.

{
  "cardUrls": [
    "https://preflight.abacore.net/.well-known/agent-card.json",
    "https://www.agentcard.net/.well-known/agent-card.json"
  ],
  "maxResults": 2
}
Download input.json

CHOOSE A STARTING POINT

3 ready-to-use inputs

Pick a focused example, copy or download its JSON, then review the inputs and current pricing in your own Apify account. Downloading a configuration does not start a run.

Default input · Input schema · Saved output capture

Compare two public Agent Card contracts

Read ACN Preflight and AgentCard.net Toolkit public metadata. This does not call any advertised skill.

{
  "cardUrls": [
    "https://preflight.abacore.net/.well-known/agent-card.json",
    "https://www.agentcard.net/.well-known/agent-card.json"
  ],
  "maxResults": 2
}

Saved run evidence: 2026-11-21 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Inspect a domain’s public discovery card

Resolve AgentCard.net to its standard well-known card and export its declared skills and interfaces.

{
  "cardUrls": [
    "https://www.agentcard.net"
  ],
  "maxResults": 1
}

Saved run evidence: 2026-11-21 UTC · 1 saved row. This is a historical check, not live data or a guarantee that every query will succeed today.

Start a public agent contract change watch

Establish a private baseline for the two public example cards; later complete runs identify skill and contract changes.

{
  "cardUrls": [
    "https://preflight.abacore.net/.well-known/agent-card.json",
    "https://www.agentcard.net/.well-known/agent-card.json"
  ],
  "maxResults": 2,
  "comparePrevious": true,
  "snapshotName": "agent-contract-watch"
}

Saved run evidence: 2026-11-21 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Download all example inputs and evidence references

A CLEAR DATA CONTRACT

Inputs you can configure

FieldTypeMeaning
cardUrlsarray

Public HTTP(S) domains resolve to /.well-known/agent-card.json; explicit URLs may use that path or legacy /.well-known/agent.json. No query strings, credentials, custom ports or private-network targets. Empty uses two documented public example cards.

maxResultsinteger

Limit validated saved rows. If lower than the selected source count, the run is incomplete and does not advance history.

comparePreviousboolean

A complete first run establishes a private baseline. Incomplete sources, output, time or spending limits preserve previous history. Avoid overlapping runs for the same watchlist.

onlyChangesboolean

Enables comparison. An unchanged run may legitimately save zero rows. First complete run saves all observations. No removal inference from missing sources.

snapshotNamestring

A stable name for this watchlist: 1–80 letters, numbers, underscores or hyphens.

maxRunSecondsinteger

Network requests honor the remaining budget. Smaller watchlists improve completeness. Platform timeout is also respected.

Output fields

titleagentVersionprotocolFamilyskillCountskillsinterfacessecuritySchemesaddedSkillsremovedSkillsinterfacesChangedauthChangedcomparisonStatussourceUrl

These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.

Input schema JSON

KNOW THE COST

Event pricing

Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.

EventUSD per eventWhat is charged
Actor Start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Saved observation$0.002One validated observation confirmed saved to the dataset.

BUILD A REVIEWED WORKFLOW

Use this with companion tools

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

Parallel research context

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.

Read the companion guide →

Parallel research context

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.

Read the companion guide →

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Source contract captured from build 1.0.1. Presentation refreshed 2026-11-21. Example outputs retain their original sample context; they are not live results.

A2A Agent Card Monitor – Skills & Contract Changes

Did a remote AI agent change its public skills, interfaces or authentication contract?

Spot public AI agent contract changes before you update your integration. Keep skill additions, removed skills, interface changes and advertised authentication changes in source-linked JSON or CSV.

Start with a small useful result

For AI integration agencies, agent directory operators and developers maintaining a shortlist of public A2A services. No API key, account login or proxy is required. Press Start to collect at most two real public observations. Leave comparison off for the first exploration. Every row includes a stable recordId, title, url, sourceUrl and observedAt.

What you can do with the results

Each row represents one validated public card and includes skills, interfaces, capabilities, input/output modes, provider metadata and selected security scheme declarations, including API key location, advertised OAuth scopes, flow endpoint URLs and PKCE flags. skillCount counts advertised skills, not successful calls. Modern supportedInterfaces and legacy url/preferredTransport fields are normalized, while cardLayout keeps their origin visible and protocolFamily derives from the declared versions. Interface preference order and tenant routing values are preserved. Extra custom fields, call examples, signatures and secret-like scheme values are not copied.

Three practical input recipes

Compare two public Agent Card contracts

Read ACN Preflight and AgentCard.net Toolkit public metadata. This does not call any advertised skill.

{
  "cardUrls": [
    "https://preflight.abacore.net/.well-known/agent-card.json",
    "https://www.agentcard.net/.well-known/agent-card.json"
  ],
  "maxResults": 2
}

Inspect a domain’s public discovery card

Resolve AgentCard.net to its standard well-known card and export its declared skills and interfaces.

{
  "cardUrls": [
    "https://www.agentcard.net"
  ],
  "maxResults": 1
}

Start a public agent contract change watch

Establish a private baseline for the two public example cards; later complete runs identify skill and contract changes.

{
  "cardUrls": [
    "https://preflight.abacore.net/.well-known/agent-card.json",
    "https://www.agentcard.net/.well-known/agent-card.json"
  ],
  "maxResults": 2,
  "comparePrevious": true,
  "snapshotName": "agent-contract-watch"
}

Changes you can verify

On complete subsequent observations, addedSkills, removedSkills and changedSkills describe card-level changes. interfacesChanged, authChanged and capabilitiesChanged identify contract differences. Removed skills mean removed from the newly retrieved complete card; an unavailable card never establishes that an agent or skill was removed. Authentication requirements absent from a card remain null; an explicit empty list remains distinct.

Set comparePrevious: true and a stable snapshotName to retain a private baseline for the selected scope. The first complete run marks observations new; later runs mark them changed or unchanged with changedFields and the previous normalized observation. The baseline belongs to the account running the Actor. A different source list or comparison scope creates separate history.

onlyChanges: true enables comparison and suppresses unchanged rows; a successful repeat can legitimately save zero rows. Source failures, truncated output, a deadline or a spending limit preserve the prior baseline. A concurrent-history change detected before commit is reported rather than overwritten; avoid overlapping runs for the same watchlist because the storage service does not provide an atomic compare-and-swap transaction.

Coverage and limits

  • The default reads ACN Preflight and AgentCard.net Toolkit, two independent public examples. They are third-party services, not Mayd It services. Their metadata can change.
  • Supply public domains or the exact /.well-known/agent-card.json path. Legacy /.well-known/agent.json is supported only when explicitly selected; no hidden fallback requests.
  • Each source uses a read-only GET. Standard HTTP(S) ports only; URL credentials and query strings are refused. All resolved IP addresses must be public, and validated addresses are pinned for the connection to prevent DNS rebinding.
  • Response bodies are limited to 512 KiB before and after decompression. Redirects are not followed; correct the public source URL when a card moves.
  • A declared private interface is recorded with a warning and never contacted. A signature count is presence metadata only: signatureVerification is always not_performed.
  • This is a bounded contract monitor, not a complete A2A conformance validator, agent marketplace, trust score, security audit, or uptime guarantee.
  • At most 20 targets and 20 saved observations per run. Requests use a 120-second maximum run budget and the platform’s earlier deadline.
  • All-source failure fails honestly. Source errors and access problems are written to SUMMARY, never fabricated as paid dataset rows. A partial run retains useful rows and clearly reports incomplete coverage.

Output, pricing and scheduling

Export the dataset as JSON, CSV or Excel. Read SUMMARY for source coverage, limits and history status; open RUN_REPORT for a readable overview. For nested checks or skills, JSON preserves the full structure.

Base pricing is $0.002 per confirmed saved observation, plus $0.00005 per Actor start at the default 256 MB. Standard plan-tier discounts may apply to results. A row containing several checks or skills is still one observation. Failed sources and unchanged results suppressed by onlyChanges do not incur a result charge. Apify platform usage may also apply under your plan. The Actor checks remaining result allowance before saving, and the last accepted row at the limit is counted correctly.

For recurring checks, save a task with your watchlist and use Apify Schedules at a cadence appropriate to the upstream source. Configure integrations yourself if you need to deliver results elsewhere; this Actor sends no messages and creates no schedules.

Source and interpretation

The A2A specification defines public Agent Card discovery and metadata. ACN Preflight card and AgentCard.net card are the documented examples. This is an independent tool, not an official A2A product.

Use the Actor’s Issues tab to report source changes or request a supported input example.

Companion workflows

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

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

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.