Developers
Verify offline first from receipt bytes alone, then optionally use the read-only hosted API when you need a bounded hosted check.
Given receipt bytes and issuer public key material, check signature, canonicalization, declared profiles, and compute Sigil S4 (Proven) when DoT-4 passes. No network call is required for base validity. Proof Lab demonstrates this path in the browser.
POST https://api.zk-ai.org/v1/verify with JSON `{ receipt, public_key, ...trust inputs }`. OpenAPI: /openapi.json on zk-ai.org.
The verifier rejects ambiguous trust material. Provide explicit public keys, optional onlog_proof and hybrid_sig attachments, and declared claim bindings — do not assume implicit trust.
Responses include receipt_id, crypto_ok, sigil, dotSet, profiles, on_log, hybrid, cb, and bridges fields. DoT-0–4 pass when crypto_ok is true at v0.1; DoT-5 needs onlog_proof; DoT-6 needs hybrid_sig. Unknown profiles fail closed.
Agents may use the public verifier MCP package (@zkai/public-verifier-mcp) for verify_receipt and explain_sigil tools. Site discovery MCP at zk-ai.org/mcp is read-only route search — not receipt verification.