How does Arkova verify documents without seeing them?

Arkova uses cryptographic fingerprinting (SHA-256) that runs entirely in your browser. We only store the fingerprint, a one-way mathematical proof, never the document itself. This fingerprint is then anchored to a permanent public record.

Can anyone verify a credential?

Yes. Verification is completely open. Anyone with a verification link or QR code can confirm a document's authenticity and timestamp independently. No account or software required.

What types of documents can I anchor?

Any digital file: PDFs, images, spreadsheets, presentations, contracts, certificates, transcripts. If it has a file, it can be fingerprinted and anchored.

How is this different from DocuSign or other e-signature tools?

E-signature tools prove who signed a document. Arkova proves that a specific document existed at a specific time and has not been altered since. These are complementary. You can anchor a signed document to prove it hasn't changed after signing.

Can I integrate Arkova into my existing systems?

Absolutely. Our Verification API lets you verify credentials programmatically with a single API call. Batch endpoints support up to 100 verifications per request. Webhook notifications provide real-time events.

Your documents never leave your device. That's our foundational privacy guarantee, not just a feature. Fingerprints are anchored to a public, independently verifiable network. Even if our servers were compromised, your documents remain private because we never had them.

How does Arkova work with our existing ATS or background check workflow?

Arkova's Verification API integrates with any system that can make an HTTP call. Your ATS, HRIS, or background screening platform calls our endpoint and receives a structured, verified response. We also support webhooks for real-time status updates and batch endpoints for bulk verification.

Quickstart — Verify your first credential in 5 minutes

Last updated: March 2026

1. Prerequisites

Note

Arkova is currently in beta. Request early access at arkova.ai.

What you need

A modern browser — Chrome, Firefox, Safari, or Edge
An email address for account creation

No software installation required — Arkova runs entirely in the browser.

For API integration: any HTTP client or one of our SDKs (Python, TypeScript).

2. Create an Account

Go to app.arkova.ai and click "Create Account"
Enter your email and password
Verify your email address

Tip

For organization accounts, you'll be prompted to create or join an organization after signing in.

3. Upload Your First Credential

Navigate to Documents from the sidebar
Click "Secure Document"
Select or drag-and-drop your document (PDF, image, or other file)

Important

Your document never leaves your device. Arkova generates a SHA-256 fingerprint entirely in your browser using the Web Crypto API. Only the fingerprint and PII-stripped metadata are sent to the server.

If AI extraction is enabled, Arkova will automatically extract metadata (issuer, dates, credential type) from the document.

Review and confirm the extracted metadata, then click "Anchor" to submit the credential for network anchoring.

4. Anchor to the Network

Once submitted, your credential enters the anchoring pipeline. You can track it through these status stages:

PENDING — Queued for the next anchoring batch
SUBMITTED — Anchor transaction broadcast to the network
SECURED — Transaction confirmed in a network block. Your credential now has an immutable timestamp.

Note

Anchoring batches run every 5 minutes. Multiple credentials are combined into a single network transaction using a Merkle tree, keeping costs low while maintaining individual verifiability.

Each anchor contains: ARKV prefix (4 bytes) + Merkle root hash (32 bytes) written via OP_RETURN.

Once SECURED, your credential gets a public verification page. Share it via: direct link, QR code, or embed.

Anyone can verify without an account — they see: verification status, issuer, timestamp, anchor transaction reference, and lifecycle timeline.

Download a PDF proof certificate for offline verification.

text

https://app.arkova.ai/verify/ARK-2026-XXXXX

6. Integrate via API

For programmatic verification, use the Verification API.

bash

# Verify a credential
curl https://app.arkova.ai/api/v1/verify/ARK-2026-00091

# With API key for higher rate limits
curl -H "Authorization: Bearer ak_live_your_key" \
  https://app.arkova.ai/api/v1/verify/ARK-2026-00091

typescript

import { ArkovaClient } from '@arkova/sdk';

const client = new ArkovaClient({ apiKey: 'ak_live_...' });
const result = await client.verify('ARK-2026-00091');

console.log(result.verified);  // true
console.log(result.status);    // "ACTIVE"

See the full API Reference and SDK documentation for more details.

7. Next Steps

Set up webhooks to receive real-time notifications /docs/webhooks
Explore the full API Reference /docs/api
Install the Python or TypeScript SDK /docs/sdks
Connect AI agents via MCP /docs/mcp
Read the Whitepaper for the full architecture /whitepaper
Dive into the Technical Wiki for security details /wiki