[Feature]: Handle runtime A2A card generation #5
Description
Problem Statement
Currently, our system processes agent configurations only from physical JSON files. However, as many modern agents generate their configuration cards at runtime, this static approach limits our library's utility.
To better serve a wider range of organizations, we should develop a new method to handle runtime agent cards. This will enable seamless integration with dynamic agent environments, making our library more adaptable and accessible.
Proposed Solution
A new API endpoint could be implemented to accept agent configurations directly as a payload, rather than relying on static JSON files. This endpoint would parse the incoming data, validate it against a predefined schema, and then generate an in-memory AgentCard object. The system could then process this object just as it would with a card loaded from a file.
For example /agents/configure
Alternatives Considered
No response
Component
Signing
Additional Context
No response