Releases: agent-network-protocol/AgentConnect
Releases · agent-network-protocol/AgentConnect
0.3.5
agent-connect has been upgraded by two versions, resolving the previous issue of excessive dependencies.
0.3.4
- Remove the default installation of dependencies such as
fastapi
- Add an implementation for generating the DID-WBA HTTP authentication header
0.3.2
Support integrity verification of Agent description specification Json-LD documents.
0.3.1
Support for the latest version of the did:wba HTTP header format
The latest version of the did:wba HTTP header format uses snake_case for field names.The latest version of the did:wba HTTP header format uses snake_case for field names.
0.3.0:Support for the did:wba method
This release supports the did:wba
method.
You can use the agent-connect
library to create did:wba
DID documents, generate HTTP authorization headers, and authenticate HTTP requests using the did:wba
method.
0.2.0
AgentConnect now supports metaprotocols and application-layer protocol frameworks.
Using metaprotocols, two agents can negotiate the communication protocol format via natural language. They can then leverage large language models (LLMs) to generate protocol-handling code and directly process protocol data.
The application-layer protocol framework provides protocol management functionality. Currently, it only manages protocols generated by AgentConnect. In the future, it will support features such as preloading, deleting, and updating protocols.
0.1.5
Add a new mode: simple node, which enables peer-to-peer identity verification and encrypted communication without relying on any third-party services.
For detailed usage, please refer to the code in examples/simple_node.
0.1.4
Complete basic functionalities, supporting the generation and registration of DID documents, short-term key agreement between two DID users, and end-to-end encrypted communication.
Code has been submitted to PyPI.