a2a_.well_known_agent.json_retrieve

Deprecated

GET

/v1/a2a/.well-known/agent.json

const url = 'https://historical-api.invalid/v1/v1/a2a/.well-known/agent.json';
const options = {method: 'GET'};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://historical-api.invalid/v1/v1/a2a/.well-known/agent.json

HISTORICAL REFERENCE — this snapshot describes the previous developer API. It is not the current contract. See https://docs.exepad.com/interfaces/rest/ for supported routes. App creation and publishing currently use Studio.

GET /.well-known/agent-card.json (and the legacy /.well-known/agent.json).

The A2A spec’s discovery mechanism: the AgentCard served UNAUTHENTICATED at a well-known URI so a client can discover the agent (and its authenticated endpoints) before it holds any credentials. The card carries no secrets. On a2a.exepad.com the host dispatcher rewrites /.well-known/* to this route; the a2a feature flag still gates it (404 when off), and a rate limit on a2a.exepad.com covers abuse.

a2a_.well_known_agent.json_retrieve

Authorizations

Responses

200