Trango ComputeContextIQ

Free tool · No sign-up required

A2A Inspector —
validate any Agent Card in seconds.

Enter any domain and fetch its Agent2Agent (A2A) card from /.well-known/agent-card.json. See the skills, protocolVersion, securitySchemes, and transports another agent would negotiate — exactly as the Linux Foundation spec defines them.

Specs and transports covered

Google A2ALinux FoundationJSON-RPC 2.0gRPCHTTP+JSON / RESTOpenAPI 3 securityOpenID ConnectServer-Sent Events

What it shows you

Agent Card validation

Fetches the card from /.well-known/agent-card.json, verifies it parses as a structurally valid A2A card, and lays out identity, service endpoint, protocolVersion, and transports — everything a client agent reads before first contact.

Skills breakdown

Renders every skill with its id, name, description, and tags — the exact advertisement routing LLMs use to decide whether to engage your agent. Vague skills are the #1 reason working A2A agents get no traffic.

Security scheme parsing

Decodes securitySchemes in their OpenAPI 3 format — openIdConnect discovery URLs, oauth2 flows, apiKey, and HTTP bearer — so you can see exactly how a client is expected to authenticate before opening a task.

Legacy path detection

Also checks the pre-0.3.0 location /.well-known/agent.json and flags cards still served only from the legacy path, so you know when a migration to agent-card.json is due.

Capabilities and modes

Shows declared protocol capabilities (streaming, pushNotifications) and default input/output media types, so integration mismatches surface before the first task fails mid-stream.

Full report download

Download the parsed card, raw JSON, and the complete three-protocol scan result as one report file for partner documentation or integration reviews. Pro feature.

Agent Card fields parsed

protocolVersionnamedescriptionversionurlpreferredTransportcapabilitiesskillsdefaultInputModesdefaultOutputModessecuritySchemesprovider

Who uses it

A2A agent developers

Validate your card from a cold client before announcing it: correct path, parseable JSON, live service endpoint, and skills descriptive enough for routing LLMs to actually select your agent.

Partner integration engineers

About to integrate a partner's A2A agent? Inspect their card first — protocolVersion compatibility, auth expectations, and streaming support — before writing a line of client code.

Agent platform teams

Running a registry or marketplace of agents? Spot-check that listed agents still serve valid cards and that securitySchemes point at resolvable OpenID Connect discovery documents.