Adapters and integrations
Protocol adapters
HTTP, WebSocket, EAS, and Weave adapters connect different contracts.
Select the transport or anchor you need
| Adapter | Source | Responsibility |
|---|---|---|
| HTTP TypeScript | openagent-sdk/adapters/http/typescript | Discovery, challenge, proof, sessions and middleware |
| HTTP Rust | openagent-sdk/adapters/http/rust | Rust HTTP protocol binding |
| WebSocket Rust | openagent-sdk/adapters/websocket/rust | Message transport binding for the authentication protocol |
| Weave Rust | openagent-sdk/adapters/weave | Protocol integration with Weave transport/data primitives |
| EAS TypeScript | openagent-sdk/adapters/eas/typescript | EAS anchor integration, separate from authentication transport |
Integration workflow
- Match the peer's protocol and adapter version.
- Configure the exact origin, identity/key provider, supported algorithm and transport.
- Implement persistence and nonce/session lifetime appropriate to that transport.
- Carry verified identity into application policy; do not treat an established channel as unrestricted authority.
- Test disconnect/reconnect, replay, expiry and peer mismatch at the actual transport boundary.
An adapter in source does not imply that a public server has enabled it. HTTP examples cannot be reused as WebSocket frame definitions. EAS is an authority-anchor option only when the verifier's trust policy explicitly accepts the chosen chain/contract and evidence.
Each adapter has a dedicated source package reference. The HTTP API guide documents the concrete TypeScript route contract.