Help with Verifyum. Write to us.

Before you write

The answer may already be here

The FAQ covers how proofs work and how to check one with no Verifyum software. The agent guide covers the API, the MCP endpoint and the limits. The Verify on Solana page checks a proof against the chain in your browser.

What to include

Enough to find the public record

If your question is about a proof, send its proof ID, the 26 characters in its address. Add the time in UTC, the error message or HTTP status you saw, and the client you used: the website, the HTTP API, the hosted MCP endpoint, or the npm package verifyum-mcp and its version.

Never send your file, its hash, the nonce or your private draft. We never need them, and the proof ID is enough to find the public record.

Limits and errors

When a request is refused

HTTP 429 means the anchor limit is reached. Wait for the time in Retry-After, then retry with the same commitment and idempotency key. Never retry in parallel. HTTP 503 means a backing service is unavailable for a moment. Retry later in the same way.

Security

Reporting a vulnerability

Report a security issue to the contact in our security.txt. Please do not test it against other people's proofs.

Who answers

AI SENSE AS

Verifyum is operated by AI SENSE AS, Oslo, Norway. Messages are read on Norwegian working days. The terms of use are on the Terms page.