A2A discovery
The current A2A card is available at:
https://api.exepad.com/v1/a2a/.well-known/agent-card.jsonThe public card does not require authentication. An authenticated card is also available at GET /v1/a2a/agent-card.
Current capability boundary
Section titled “Current capability boundary”The card currently advertises an empty skills array. Streaming, push notifications, and state-transition history are disabled. Although POST /v1/a2a/message/send is registered, no app-building skill is implemented by the current A2A service.
Read the returned card before deciding what an integration can do. Do not infer create, edit, publish, or long-running task support from the presence of an A2A endpoint or an older example.
Which path should I use?
Section titled “Which path should I use?”Use MCP for the available read-only account tools, REST for documented key and billing operations, and Studio to create and publish apps.
This is separate from agents you build into an app for research, support, or other tasks. Those experiences need their own context, permitted actions, and review behavior.