A2A icon

A2A

A2A (Account to Account) transfers, account management, and Agent2Agent protocol communication
Join our community

Actions12

Overview

This node interacts with an A2A (Account to Account) agent endpoint, specifically supporting the Agent2Agent protocol communication. The Get Agent Card operation fetches the agent card metadata from a specified agent URL. This is useful for discovering and retrieving public information about an agent in the Agent2Agent ecosystem, such as its capabilities or identity details.

Typical use cases include:

  • Integrating with decentralized agent networks where agents communicate via standardized protocols.
  • Retrieving agent metadata to verify or display agent information before initiating further interactions.
  • Automating workflows that require querying agent capabilities or status.

For example, you might provide the base URL of an agent’s API endpoint, and this node will retrieve the .well-known/agent-card JSON document describing that agent.

Properties

Name Meaning
Agent URL The base URL of the A2A agent endpoint. This should be the root URL where the agent is hosted, e.g., https://agent-api.example.com. The node appends /.well-known/agent-card to this URL to fetch the agent card.

Output

The output is a JSON object representing the agent card retrieved from the agent endpoint. This typically includes metadata about the agent such as its identifier, supported protocols, services, and other descriptive information.

The output structure corresponds directly to the JSON returned by the agent’s .well-known/agent-card endpoint and can be used downstream in your workflow for decision-making or display purposes.

No binary data output is produced by this operation.

Dependencies

  • Requires an HTTP-accessible A2A agent endpoint that exposes the .well-known/agent-card resource.
  • The node uses standard HTTP GET requests without authentication headers for this operation.
  • No additional credentials or environment variables are required specifically for this operation, but the node generally requires an API key credential for other operations.

Troubleshooting

  • Invalid Agent URL: If the provided Agent URL is incorrect or unreachable, the HTTP request will fail. Ensure the URL is correct and accessible from the n8n instance.
  • Non-JSON Response: The agent card endpoint must return valid JSON. If the response is malformed or not JSON, the node will throw an error.
  • Trailing Slash Issues: The node automatically removes any trailing slash from the Agent URL before appending /.well-known/agent-card. Providing URLs with multiple trailing slashes or unusual formatting may cause issues.
  • Network Errors: Timeouts or network connectivity problems will cause the request to fail. Verify network access and proxy settings if applicable.

Links and References

Discussion