Skip to main content
A2A lets external agent runtimes discover and talk to AIDA. Discovery and per-agent calls use the Document Assistant REST surface under /assistant/api/v1. Use the same regional base URL and authentication as the rest of the AI API. This page covers the three endpoints most integrators need. Full request and response schemas live in the OpenAPI playground.

​
Agent cards and per-agent A2A

​
Host-level agent card

No tenant appears in the path. Use this when you build a multi-tenant integrator that discovers a single host-level card and then selects a tenant at runtime.
The host-level card does not bind a tenant. Your client must choose the tenant itself. If that guess is wrong, AIDA returns no useful answer and the end user cannot correct the tenant from the agent UI. Prefer the tenant-scoped card unless you truly need multi-tenant discovery.
Recommended for most customers. Replace {tenant} with your AODocs tenant identifier. The card is already scoped to that tenant, so callers do not have to guess which tenant to use.

​
Call a specific AODocs agent

Use this path when you already know the AODocs agent_id and want to call that agent directly under the given tenant.
Prefer tenant-scoped discovery (.../tenants/{tenant}/.well-known/agent.json) unless you are building a multi-tenant integrator or targeting a known agent_id. For MCP tool clients, see MCP.