Agent ExplorerBeta

AgentCard Validation

Agent Explorer validates AgentCards against the A2A specification and reports both errors and warnings.

Validation Levels

Errors

Errors indicate invalid AgentCards that violate the spec:

  • Missing required fields (name, url, version)
  • Invalid field types
  • Malformed JSON
  • Empty or invalid skills array

Warnings

Warnings highlight potential issues:

  • Missing recommended fields (description, skills)
  • Empty capabilities object
  • Missing input/output modes
  • Deprecated fields

Validation Process

When you create or refresh a project:

  1. Agent Explorer fetches the AgentCard from {base-url}/.well-known/agent-card.json
  2. The JSON is parsed and validated against the A2A Zod schema
  3. Errors and warnings are surfaced in the project overview
  4. The AgentCard details are displayed in a structured view

Viewing Validation Results

In the project overview:

  1. Look for the validation status badge (green check or red error count)
  2. Expand the validation details panel
  3. Review any errors or warnings with descriptions

Common Issues

CORS Errors

If the AgentCard cannot be fetched, you may see a CORS error. Solutions:

  • Ensure the agent allows cross-origin requests from your Agent Explorer origin
  • Use the Proxy API (/api/proxy) to route the request server-side

Invalid JSON

Check for syntax errors, ensure UTF-8 encoding, and validate with a JSON linter.

Missing Capabilities

While not an error, missing capabilities mean streaming, push notifications, and state history won't be available.