Nicheloom visits: 58,069 all-time · 7,637 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

OQP

A verification protocol for AI agents

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.

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

HN · launched Apr 13, 2026 · 8 upvotes (top 52%) · 0 views

Niche: multi-agent frameworks and protocols · 298 launches, 11 in the last 7 days ▼ -31% · Explore this niche →

Category and tags
  • Horizontal
  • Observability & eval
  • Developer
  • AI-native
  • Commercial product

Visit website ↗ Source listing ↗

More like this: all 298 launches in multi-agent frameworks and protocols →

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 : 976 launches clear the similarity bar, closest 8 shown.

Attention rank: #498 of 977 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 161 days after the earliest competitor.

Related data

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.