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
Aamir21•7h ago
1. Does the /verification/assess-risk endpoint capture what you'd actually need in a CI/CD gate? What's missing from the request/response schema? 2. The Knowledge Graph as the source of business rules, does this model make sense for your stack, or is there a simpler primitive we should define first? 3. MCP compatibility, are there gaps in how OQP maps to MCP's tool/resource model?