Runnable example: examples/server-verify-node — minimal Node http proxy that forwards a posted proof to the hosted verifier and responds 200 / 403.

OpenAPI specification

The full machine-readable spec lives at zkrune.com/openapi.yaml (OpenAPI 3.1, MIT-licensed). Use it to:

• Import into Postman — Import → Link → paste https://zkrune.com/openapi.yaml. Generates a ready-to-run collection.
• Generate clients — openapi-generator-cli, oazapfts, orval, or any OpenAPI 3.1-compatible tool.
• Lint your integration — drop the spec into your editor's OpenAPI plugin to type-check requests/responses.

The reference below is the human-readable summary; the YAML is authoritative.

POST /api/verify-proof

Verify a Groth16 proof against a trusted verification key stored on the server. The client never sends the vKey — the server loads it from its own filesystem based on circuitName.

Endpoint

POST https://zkrune.com/api/verify-proof

Request Body

{
  "circuitName": "age-verification",
  "proof": {
    "pi_a": ["123...", "456...", "1"],
    "pi_b": [["789...", "012..."], ["345...", "678..."], ["1", "0"]],
    "pi_c": ["901...", "234...", "1"],
    "protocol": "groth16",
    "curve": "bn128"
  },
  "publicSignals": ["1"]
}

Response — Success

{
  "success": true,
  "isValid": true,
  "circuitName": "age-verification",
  "message": "Proof cryptographically verified!",
  "timing": 2
}

Response — Errors

Supported Circuits

age-verification · balance-proof · membership-proof · range-proof · private-voting · hash-preimage · credential-proof · token-swap · signature-verification · patience-proof · quadratic-voting · nft-ownership · anonymous-reputation · whale-holder

Self-Hosting

To run the verifier on your own infrastructure:

1. Clone the repo and deploy to Vercel / Node.js.
2. Circuit artifacts (WASM + vKey) are in public/circuits/.
3. The endpoint at app/api/verify-proof/route.ts loads vKeys from the server.
4. Point verifierUrl in your SDK/widget config to your deployment.