Nice read. Trust intelligence layer sounds buzzwordy at first but the examples helped. Any plans to open source parts of it?
Web Agent Bridge v3.6.0 — The Trust & Intelligence Layer for Sovereign AI Agents We just shipped one
3 Comments
@[Aulia Ika Savitri] Thank you Aulia, glad the examples helped clarify the concept
You’re right — “Trust Intelligence Layer” can sound like marketing buzz at first. The goal is actually quite practical: giving AI agents a standardized, cryptographically verifiable way to discover what a website can do and how much they can trust it, without relying on centralized APIs or blind scraping.
Regarding open source:
Yes — the core of Web Agent Bridge (WAB) is already open source:
→ https://github.com/abokenan444/web-agent-bridge
We follow an Open Core approach:
• The protocol, DNS discovery, basic trust layer, and most APIs are fully open.
• Some advanced parts of the Truth Layer (e.g. certain Reputation Score algorithms and Semantic Memory implementation details) are currently selective-release for security reasons, but the specifications and integration docs are public.
The aim is to balance transparency with responsible disclosure, especially since we’re dealing with trust and agent capabilities.
Would love to hear your thoughts — are you working on AI agents or sovereign infrastructure yourself?
@[Aulia Ika Savitri] Thank you Aulia, great question!
Yes, we are committed to Open Source, and the core of Web Agent Bridge is already fully open:
• The protocol specification
• DNS-based discovery
• Cryptographic trust layer (Ed25519)
• Most of the Truth Layer and Advanced Features
You can find it here:
https://github.com/abokenan444/web-agent-bridge
However, we follow an Open Core model. Some advanced components (particularly parts of the Reputation Score algorithm, certain Semantic Memory implementations, and Enterprise-tier features) are not fully open-sourced yet.
Why?
Because WAB deals with trust and agent capabilities inside websites. Releasing everything immediately could allow bad actors to reverse-engineer and abuse the system before proper safeguards are in place. We prefer responsible disclosure — opening what benefits the community while protecting critical parts until they are mature and secure.
We regularly open more parts as the project matures and as we implement stronger security measures. The direction is toward increasing openness, not the opposite.
If you’re interested in specific modules or want to contribute/review certain parts, feel free to let me know. We’re always open to serious collaboration.
Appreciate your interest!
Please log in to add a comment.
Please log in to comment on this post.
More Posts
- © 2026 Coder Legion
- Feedback / Bug
- Privacy
- About Us
- Contacts
- Premium Subscription
- Terms of Service
- Refund
- Early Builders
More From WAB
Related Jobs
- Customer Success Associate | A-Players BAjobgether · Full time · Switzerland County, IN
- Head of Data Intelligence Productsjobgether · Full time · Kingdom of Spain
- Customer Success Associate | A-Players BAjobgether · Full time · Kingdom of Spain
Commenters (This Week)
Contribute meaningful comments to climb the leaderboard and earn badges!