Is there any example for AgentExtension workflow ?

[fernando-torres-blip-ai]

I am interested in using the AgentExtension capability to provide additional requirements when serving my remote agents. However, the specification does not yet provide any illustrative examples of interactions using extensions.

Therefore, I am looking for guidance on how to implement a compliant extension workflow.

Consider the following use case: "Providing previous context to an Agent".
In order to start a new conversation with my remote agent, the client should be able to provide previous user context, including past exchanged messages (not necessarily with the same agent).

What would be the appropriate example workflow in this case?

Initial questions:

• What is the extension uri for?
• Should the client make a request to the extension uri? If so, which HTTP verb should be used, and what should the expected response be?
• Is the extension identifier the URI itself? If so, in the SendMessageRequest.Message.extensions, should I list the URIs?
• Are the extension parameters static key-value pairs, or is it a JSON API schema representing a possible request body?

Any insights or recommendations would be greatly appreciated!

[darrelmiller]

Can you take a look at the examples in the recently updated specification and let us know if these examples make the usage clearer?
https://a2a-protocol.org/latest/specification/#46-extensions

The extension Uri is just a globally unique identifier that can be used as the key in the metadata dictionary. There is no required for that extension URI to be be dereferenceable.