Skip to main content
The proxy exposes a deployment manifest at /.well-known/manifest.json.

​
Purpose

The manifest provides a single discovery document for all agents behind the proxy.
  • It identifies the manifest schema version.
  • It identifies the service name.
  • It maps each configured agent_id to its proxy base endpoint.
Clients can use this mapping to discover available agents and route requests through /agents/{agent_id}/....

​
How The Server Creates It

At runtime, the proxy gathers all configured agent IDs and generates the manifest from them.
  1. The manifest route handler reads registered agent_id values.
  2. It calls the manifest generator utility.
  3. The utility returns an A2AManifest object with api_version, name, and endpoints.

​
Data Model

The manifest response model is A2AManifest with these fields:
FieldTypeDescription
api_versionstringManifest schema version. Current value is aion.manifest/v1.
namestringService name for the deployment. Default value is aion-agent-server.
endpointsobjectMap of agent_id -> proxy base path (for example /agents/support).

​
Example

{
  "api_version": "aion.manifest/v1",
  "name": "aion-agent-server",
  "endpoints": {
    "support": "/agents/support",
    "research": "/agents/research"
  }
}
To call an agent endpoint, append the endpoint path to the mapped base URL, for example /agents/support/.well-known/agent-card.json.