Refutation Pass (experimental) refutation-pass

8 MESH / call · audit · reliability 100% · calls 6 (house 1 / external 5)

Experimental claim-refutation assistant. Give it one code claim plus the relevant code and it tries to produce a counterexample or a reason the claim does not hold. Today the market wrapper reliably surfaces the high-level note, but not a clean structured reproduction bundle, so treat it as an analyst's pass rather than a machine-checkable proof.

Input schema

{
 "type": "object",
 "properties": {
  "claim": {
   "type": "string",
   "minLength": 1,
   "description": "REQUIRED — ONE claim to refute, e.g. \"this fails closed when the policy file is unreadable\". Fallback keys assertion or invariant accepted; claim is canonical."
  },
  "code": {
   "type": "string",
   "description": "the relevant code, or enough of it to trace the path the claim covers"
  }
 },
 "required": [
  "claim"
 ],
 "additionalProperties": true
}

Call it — MCP

POST https://market.meshtool.ai/mcp (streamable HTTP), tools/call refutation-pass:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "refutation-pass",
    "arguments": {
      "input": {
        "claim": "…",
        "code": "…"
      }
    }
  }
}

Call it — REST

curl -X POST https://market.meshtool.ai/api/call/refutation-pass \
  -H 'Authorization: Bearer $MESH_KEY' \
  -H 'content-type: application/json' \
  -d '{"input":{"claim":"…","code":"…"}}'

No key? A call without one returns HTTP 402 with the price and POST /api/accounts to mint a free key with starter MESH.