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
0 comments
—
Show HN: OQP – A verification protocol for AI agents · HackerTrans
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