OQP
A verification protocol for AI agents
Details
- External ID
- 47758560
- Source
- HN
- Company
- —
- Product
- OQP
- Website domain
- github.com
- Launched
- April 13, 2026
- Cohort
- —
- Upvotes
- 8
- Upvotes percentile
- 0.4813624678663239
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
As AI agents autonomously write and deploy code, there's no standard for verifying that what they shipped actually satisfies business requirements. OQP is an attempt to define that standard.It's MCP-compatible and defines four core endpoints: - GET /capabilities — what can this agent verify? - GET /context/workflows — what are the business rules for this workflow? - POST /verification/execute — run a verification workflow - POST /verification/assess-risk — what is the risk of this change?The analogy we keep coming back to: what OpenAPI did for REST APIs, OQP does for agentic software verification.Early contributors include Philip Lew (XBOSoft) and Benjamin Young (W3C JSON-LD Working Group). Looking for feedback from engineers building on top of MCP, agent orchestration frameworks, or anyone who has felt the pain of "the agent shipped something wrong and we had no way to catch it."Repo: github.com/OranproAi/open-qa-protocol
Enrichment
- Theme
- AI agent frameworks and developer tools
- Vertical
- Horizontal
- Function
- Compliance & governance
- Audience
- Developer
- AI stance
- AI-native
- Project type
- Commercial product
- Normalized one-liner
- verification protocol for ai agents
- Manually corrected
- False
Could you build this?
Yes OQP is a lightweight protocol specification and MCP-compatible server defining four HTTP endpoints for verifying agent outputs. Building a reference implementation and spec is standard API wrapper and schema work easily accomplished with AI coding tools.
Discussion
2 comments analyzed.
Concerns raised: Verification endpoint may not fully capture CI/CD gate requirements, Knowledge Graph business rules model complexity vs. simpler alternatives, MCP compatibility gaps in tool/resource mapping
Feature requests: Clarify /verification/assess-risk request/response schema, Define simpler business rules primitive as alternative to Knowledge Graph, Improve OQP to MCP mapping for tools and resources
Competitors
Other products that read as similar to this one — 368 launches clear the similarity bar, closest 8 shown.
Attention rank: #203 of 369 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 161 days after the earliest competitor.
- OJCP · hn · 2026-08-12 · 39 upvotes · similarity 0.58
- Trust Protocols for Anthropic/OpenAI/Gemini · hn · 2026-02-18 · 40 upvotes · similarity 0.58
- Axiomeer · hn · 2026-02-03 · 13 upvotes · similarity 0.55
- Agent Passport · hn · 2026-02-21 · 14 upvotes · similarity 0.48
- Task Manager for AI Agents (MCP, Opensource) · hn · 2026-04-30 · 6 upvotes · similarity 0.47
- Cq · hn · 2026-03-23 · 225 upvotes · similarity 0.47
- Truelist MCP · ph · 2026-09-10 · 14 upvotes · similarity 0.46
- Halo · hn · 2026-07-07 · 37 upvotes · similarity 0.46
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a compliance & governance tool for Media & entertainment yet.