We are opening Web Agent Bridge (WAB) to deeper technical review, testing, and critical feedback from developers, security researchers, browser automation engineers, AI-agent builders, and privacy-focused infrastructure communities.
WAB is an open AI ↔ Web protocol and agent interoperability layer designed to reduce brittle DOM automation and replace guesswork with signed, machine-readable capability contracts.
The project currently includes:
- DNS-based discovery (_wab)
- /.well-known/wab.json
- Signed trust profiles (Ed25519)
- Ring 4 trust verification
- Agent capability negotiation
- Intent-aware routing
- Governance and audit layers
- Privacy budget declarations
- Refusal and constitutional invariant handling
- Cross-agent verification flows
- SDKs and framework adapters
- MCP and browser-agent integrations
The broader goal is simple:
Create a predictable, inspectable, privacy-aware interface between AI agents and the web — without requiring centralized control, invasive tracking, or fragile scraping logic.
We are specifically interested in feedback regarding:
- protocol design
- security assumptions
- trust boundaries
- abuse resistance
- privacy implications
- interoperability
- schema clarity
- agent discoverability
- edge-case behavior
- failure modes
- governance architecture
- machine-readability
- developer ergonomics
We are not looking for hype.
We are looking for:
- serious testing
- architectural criticism
- implementation review
- adversarial thinking
- interoperability experiments
- independent verification
If parts of the design are flawed, we want to know.
If assumptions break under real-world conditions, we want to see it.
If there are better approaches, we are open to them.
The protocol, SDKs, and specifications are public and reviewable.
Repository:
https://github.com/abokenan444/web-agent-bridge
Documentation:
https://webagentbridge.com/docs
Architecture:
https://webagentbridge.com/ring4
The long-term health of agent ecosystems will likely depend on open, inspectable, privacy-respecting standards rather than opaque automation layers.
Constructive criticism is welco