Adapters and integrations
OpenAgentIDDocumentation
Protocol adapters
HTTP, WebSocket, EAS, and Weave adapters connect different contracts.
Select the transport or anchor you need
| Adapter | Availability | Responsibility |
|---|---|---|
| Current SDK verification | SDK 0.7.2 | Possession proofs, delegation, owner/self-root policy and replay |
| HTTP TypeScript | npm 0.1.1, with limitations | Older challenge/session protocol; not recommended for new identity integrations |
| EAS TypeScript | npm 0.1.1 | Optional authority-anchor adapter; configured chain, contract and trust required |
| HTTP/WebSocket/Weave Rust | Source-only availability | Separate retained transport implementations, not published crates |
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 published package reference. The HTTP API guide documents the concrete TypeScript route contract.