feat(example): search agent example #647
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR provides an example for how to implement a search agent to extend on the basic agentverse search functionality. The search agent will get a general list for agents potentially satisfying the search request from agentverse search engine and then verify additional agent specific attributes with each agent individually. This allows for example to search for all EV charging stations in a certain area (search engine) that are below a given price limit (search agent).
There are two implementations for the search agent: The async implementation uses the common message handler-based approach and potentially scales better. The sync implementation makes use of the new
send_and_receive
feature, which makes it easier to follow the code for people unfamiliar with asynchronous communication.