Public API for automated workflows

Your agent can create verifiable file proofs.

Server-side AI agents can use Verifyum without an account, wallet, payment, API key or Bearer token. The agent hashes the file locally and sends only a privacy-preserving commitment.

Read the agent guide OpenAPI 3.1 llms.txt

Local inputFile bytes, raw hash and nonce

Public requestCommitment and idempotency key

Public resultProof URL and Solana transaction

AuthenticationNo key for current public access

Required flow

Hash locally. Anchor the commitment. Poll one proof.

The API does not accept file uploads. An agent must calculate the version 2 commitment before it calls Verifyum.

Prepare locally

SHA-256 hash the exact file bytes, generate a fresh 32-byte nonce, build the private manifest and canonicalize it with RFC 8785 JCS.

Submit safely

Hash the domain-separated manifest and send only the final commitment plus a stable idempotency key to the public anchor endpoint.

Resume and verify

Poll the returned status URL until finalized. Keep the same proof ID during delays and save the public metadata with the private local evidence.

Public creation request

No Authorization header.

POST https://api.verifyum.com/v2/anchor
Content-Type: application/json

{
  "commitment": "sha256:<64 lowercase hex characters>",
  "idempotency_key": "agent-run-unique-request-0001"
}

Poll https://api.verifyum.com/v2/proofs/{proof-id}. Honor HTTP 429, HTTP 503 and every Retry-After header.

Model Context Protocol

One URL for MCP agents.

Agents that speak the Model Context Protocol can reach the same service through one hosted endpoint. The HTTP API above remains the complete contract. The endpoint accepts only a commitment, an idempotency key or a public proof ID, and file hashing stays on your machine.

https://api.verifyum.com/mcp

Example for Claude Code: claude mcp add --transport http verifyum https://api.verifyum.com/mcp

The tools are verifyum_get_proof, verifyum_verify_public_proof and verifyum_anchor_commitment. Anchoring through MCP follows the same limits and current free policy as the HTTP API. The endpoint is listed in the official MCP registry as com.verifyum/mcp.

Executable reference

Use the published protocol.

The browser module contains the exact manifest construction, JCS canonicalization and domain-separated commitment algorithm.

verifyum-protocol.js

Service protection

Keep automation controlled.

The hard ceiling is ten new reservations per rolling hour per IP. Lower daily and global safety limits may apply. Do not parallelize retries.

Current cost

Free public use.

AI SENSE AS currently pays the Solana fee. This is a current service policy, not a permanent pricing guarantee.