Skip to content
Nappai Documentation

A2A Card Reader

The A2A Card Reader is a simple tool that lets you pull card data from one or more remote agents. You just give it the URL(s) of the agents, and it fetches the card information for you.

How it Works

When you enter a URL, the component sends a quick HTTP request to that address, looking for a file called agent.json in the well‑known location (<URL>.well-known/agent.json). It then reads the JSON data returned by the agent and turns it into a structured format that other parts of your workflow can use. If you list several URLs separated by commas, it will do this for each one and give you a list of results.

Inputs

  • URL: The web address of the remote agent you want to read.
    Enter a single URL or a comma‑separated list of URLs. This field is required.

Outputs

  • A2A Card Result: A list of Data objects that contain the card information retrieved from each URL. These objects can be passed to other components in your workflow for further processing or display.

Usage Example

  1. Drag the A2A Card Reader component onto your canvas.
  2. In the URL field, type https://example.com (or any other agent URL).
  3. Connect the A2A Card Result output to a component that can display or store the data, such as a table viewer or a database writer.
  4. Run the workflow. The component will fetch the card data from the specified agent and make it available for the next steps.
  • Data Viewer – Shows the card data in a readable table.
  • Database Writer – Saves the card data to a database for later use.
  • Alert Trigger – Sends a notification if the card data meets certain conditions.

Tips and Best Practices

  • Keep the URLs short and reliable; the component will fail if the agent is unreachable.
  • Use a single URL per workflow if you only need one card; listing many URLs can slow down the process.
  • Combine the A2A Card Reader with a Data Filter component to only keep the card fields you actually need.

Security Considerations

  • The component makes HTTP requests to the URLs you provide, so only use trusted sources.
  • If the agent requires authentication, you’ll need to add the necessary headers or tokens in a separate component before calling the A2A Card Reader.
  • Be aware that the data returned is whatever the remote agent exposes; validate it before using it in sensitive parts of your system.