Trust Protocols for Anthropic/OpenAI/Gemini
Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.
Want to reach these readers? Sponsor an issue.
Much of my work right now involves complex, long-running, multi-agentic teams of agents. I kept running into the same problem: “How do I keep these guys in line?” Rules weren’t cutting it, and we needed a scalable, agentic-native STANDARD I could count on. There wasn’t one. So I built one.Here are two open-source protocols that extend A2A, granting AI agents behavioral contracts and runtime integrity monitoring:- Agent Alignment Protocol (AAP): What an agent can do / has done. - Agent Integrity Protocol (AIP): What an agent is thinking about doing / is allowed to do.The problem: AI agents make autonomous decisions but have no standard way to declare what they're allowed to do, prove they're doing it, or detect when they've drifted. Observability tools tell you what happened. These protocols tell you whether what happened was okay.Here's a concrete example. Say you have an agent who handles customer support tickets. Its Alignment Card declares:{ "permitted": ["read_tickets", "draft_responses", "escalate_to_human"], "forbidden": ["access_payment_data", "issue_refunds", "modify_account_settings"], "escalation_triggers": ["billing_request_over_500"], "values": ["accuracy", "empathy", "privacy"] }The agent gets a ticket: "Can you refund my last three orders?" The agent's reasoning trace shows it considering a call to the payments API. AIP reads that thinking, compares it to the card, and produces an Integrity Checkpoint:{ "verdict": "boundary_violation", "concerns": ["forbidden_action: access_payment_data"], "reasoning": "Agent considered payments API access, which is explicitly forbidden. Should escalate to human.", "confidence": 0.95 }The agent gets nudged back before it acts. Not after. Not in a log you review during a 2:00 AM triage. Between this turn and the next.That's the core idea. AAP defines what agents should do (the contract). AIP watches what they're actually thinking and flags when those diverge (the conscience). Over time, AIP builds a drift profile — if an agent that was cautious starts getting aggressive, the system notices.When multiple agents work together, it gets more interesting. Agents exchange Alignment Cards and verify value compatibility before coordination begins. An agent that values "move fast" and one that values "rollback safety" registers low coherence, and the system surfaces that conflict before work starts. Live demo with four agents handling a production incident: https://mnemom.ai/showcaseThe protocols are Apache-licensed, work with any Anthropic/OpenAI/Gemini agent, and ship as SDKs on npm and PyPI. A free gateway proxy (smoltbot) adds integrity checking to any agent with zero code changes.GitHub: https://github.com/mnemom Docs: docs.mnemom.ai Demo video: https://youtu.be/fmUxVZH09So
HN · launched Feb 18, 2026 · 40 upvotes (top 21%) · 1 view
Niche: ai agent guardrail software · 201 launches, 25 in the last 7 days ▲ +25% · Explore this niche →
Category and tags
- Horizontal
- Compliance & governance
- B2B
- AI-native
- Commercial product
Visit website ↗ Source listing ↗
More like this: all 201 launches in ai agent guardrail software →
Could you build this?
Yes This is an API gateway and middleware proxy that intercepts LLM agent function calls to enforce schemas, rate limits, and audit logs.
Discussion
20 comments analyzed.
Competitors mentioned: Simplio.dev (AI gateway with fallback routing), OPA/Rego (policy engines), Cedar (authorization policy engine), Casbin (authorization framework), Google A2A protocol
Concerns raised: LLM cannot be trusted to follow instructions; vulnerable to prompt injection and confused deputy attacks, Soft instruction sets (training/prompting) insufficient for security; need external, authoritative, enforced controls, Latency overhead of inline monitoring (~1 second) may be prohibitive for some use cases, Model output quality vs. speed/cost tradeoff in monitoring implementation, Scalability concerns as human-in-the-loop thins and autonomous agents increase
Feature requests: Standardized protocol implementations so third parties can build in other languages (Rust, Go) without proprietary SDK, Benchmarks demonstrating ideal use cases and performance improvements, Interactive certificate explorer and hash chain tamper simulation visualizations, Integration with policy engines (OPA, Cedar) for authorization decisions, Proof composition to verify entire session integrity without checkpoint verification
Competitors
Other products that read as similar to this one : 1090 launches clear the similarity bar, closest 8 shown.
Attention rank: #245 of 1091 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).
Launched 110 days after the earliest competitor.
- OQP · hn · 2026-04-13 · 8 upvotes · similarity 0.59
- Agentic Identity Broker, OAuth Delegation for AI Agents · hn · 2026-11-06 · 24 upvotes · similarity 0.56
- Agent Action Protocol (AAP) · hn · 2026-03-03 · 13 upvotes · similarity 0.50
- Axiomeer · hn · 2026-02-03 · 13 upvotes · similarity 0.50
- Keel · ph · 2026-11-14 · 2 upvotes · similarity 0.50
- APC · ph · 2026-10-19 · 1 upvotes · similarity 0.50
- AgentTrust OS · ph · 2026-10-22 · 1 upvotes · similarity 0.50
- TotalHeal AgentGate · ph · 2026-11-10 · 1 upvotes · similarity 0.49
The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.