UAT: Agent Card discovery endpoint (/.well-known/agent.json) not implemented in ASGI app #4679

Closed
opened 2026-04-08 18:00:11 +00:00 by HAL9000 · 1 comment
Owner

Summary

The A2A protocol requires an Agent Card discovery endpoint at /.well-known/agent.json. The ASGI application in src/cleveragents/a2a/asgi.py only serves health/readiness endpoints and returns 404 for /.well-known/agent.json.

Expected Behavior (from docs/specification.md §Server and Client Architecture)

The connection lifecycle follows the A2A standard: the client discovers the server's Agent Card (capability exchange), authenticates via the declared HTTP auth scheme, and begins sending message/send or message/stream requests.

  1. Client fetches the server's Agent Card (via /.well-known/agent.json or configured URL)
  2. Agent Card declares supported authentication schemes (OAuth2, API key, Bearer token)

The Agent Card should advertise:

  • Supported _cleveragents/ extension methods
  • Automation profiles
  • Tool registries
  • A2A protocol version
  • Authentication schemes

Actual Behavior

src/cleveragents/a2a/asgi.py only handles:

  • GET /{"service":"cleveragents"}
  • GET /live{"status":"alive"}
  • GET /ready{"status":"ready"}
  • GET /health{"status":"ok"}

GET /.well-known/agent.json returns 404 {"error":"not found"}.

The _KNOWN_PATHS set in asgi.py does not include /.well-known/agent.json.

Code Location

  • src/cleveragents/a2a/asgi.py_KNOWN_PATHS frozenset (line ~22) and app() function
  • No AgentCard model exists anywhere in src/cleveragents/a2a/

Impact

  • Third-party A2A clients cannot discover the server's capabilities
  • Server-mode authentication cannot be negotiated
  • The A2A standard's capability exchange mechanism is completely absent
  • IDE plugins and external agents cannot connect to CleverAgents

Steps to Reproduce

# Start the ASGI server
uvicorn cleveragents.a2a.asgi:app --port 8080

# Try to fetch the Agent Card
curl http://localhost:8080/.well-known/agent.json
# Returns: {"error":"not found"} (404)

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Summary The A2A protocol requires an Agent Card discovery endpoint at `/.well-known/agent.json`. The ASGI application in `src/cleveragents/a2a/asgi.py` only serves health/readiness endpoints and returns 404 for `/.well-known/agent.json`. ## Expected Behavior (from `docs/specification.md` §Server and Client Architecture) > The connection lifecycle follows the A2A standard: the client discovers the server's Agent Card (capability exchange), authenticates via the declared HTTP auth scheme, and begins sending `message/send` or `message/stream` requests. > 1. Client fetches the server's Agent Card (via `/.well-known/agent.json` or configured URL) > 2. Agent Card declares supported authentication schemes (OAuth2, API key, Bearer token) The Agent Card should advertise: - Supported `_cleveragents/` extension methods - Automation profiles - Tool registries - A2A protocol version - Authentication schemes ## Actual Behavior `src/cleveragents/a2a/asgi.py` only handles: - `GET /` → `{"service":"cleveragents"}` - `GET /live` → `{"status":"alive"}` - `GET /ready` → `{"status":"ready"}` - `GET /health` → `{"status":"ok"}` `GET /.well-known/agent.json` returns `404 {"error":"not found"}`. The `_KNOWN_PATHS` set in `asgi.py` does not include `/.well-known/agent.json`. ## Code Location - `src/cleveragents/a2a/asgi.py` — `_KNOWN_PATHS` frozenset (line ~22) and `app()` function - No `AgentCard` model exists anywhere in `src/cleveragents/a2a/` ## Impact - Third-party A2A clients cannot discover the server's capabilities - Server-mode authentication cannot be negotiated - The A2A standard's capability exchange mechanism is completely absent - IDE plugins and external agents cannot connect to CleverAgents ## Steps to Reproduce ```bash # Start the ASGI server uvicorn cleveragents.a2a.asgi:app --port 8080 # Try to fetch the Agent Card curl http://localhost:8080/.well-known/agent.json # Returns: {"error":"not found"} (404) ``` --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester
HAL9000 added this to the v3.8.0 milestone 2026-04-08 18:05:19 +00:00
Author
Owner

Closing as duplicate of #4900 — both issues report the same problem: ASGI app missing /.well-known/agent.json Agent Card endpoint. Issue #4900 has milestone v3.5.0, MoSCoW/Must have, and story points (3) assigned.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Closing as duplicate of #4900 — both issues report the same problem: ASGI app missing `/.well-known/agent.json` Agent Card endpoint. Issue #4900 has milestone v3.5.0, MoSCoW/Must have, and story points (3) assigned. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#4679
No description provided.