Skip to content

The trust layer for humans and AI agents

Issue once.
Verify forever.

Turn documents into checkable records.

Teams that own audits get records they can check without trusting us. Software and agents get the same records through an MCP server, an API and SDKs.

Get startedVerify a sample
Works withDocuSignGoogle DriveMCP
CSA STAR Level 1 self-assessment

Sample public record

Our own board consent, as anyone can check it

Captured Oct 19, 2026 · status may change

Contract, post-signing

Secured from DocuSign · issued by Arkova

ACTIVE
Document fingerprint

535598e71856b127ebc593ac25a530420490749bbb551678f4b0df1641f98a24

Public ID
ARK-DOC-2Z5WPG
Status at snapshot
ACTIVE
Network checkpoint
962,299
Issuer
Arkova
Network observed time
Network receipt
cbfcc61f5b86e68ed139cc1685bd83c951ed5919d73ba567468ff1b20c9f98a3

This is a dated snapshot of public record details. Use the verifier to request a status update; cached results may lag recent changes.

Verify a record yourself

Records that can't be altered without a trace. Anchored to a public, permanent ledger.

4M+Records anchored

As published in the Arkova investor deck, September 2026. The live count has moved on since.

Check any one yourself

With real examples

Use cases

Contracts and legal workflows. Changelogs, audit evidence and AI agent logs. Your own documents at home.

  1. 01Contracts
  2. 02Audit and agent logs
  3. 03Individuals

01 Contracts and legal workflows

Show which version was executed.

Arkova secures each executed contract automatically, so anyone can check that the file they hold is the one that existed.

You run legal operations. You connect DocuSign once and set a rule. From then on, every completed envelope is fingerprinted and secured on its own. Nobody uploads anything.

A counterparty sends a revised exhibit. It lands in a watched Drive folder and waits in a review queue. You approve it. The old version is marked Superseded, and both versions link to each other.

A partner reviews the deal. You attach an attestation: reviewed by legal.

Two years later, the other side says the exhibit was swapped. You send opposing counsel the public ID. They open search.arkova.ai, with no account, and compare their copy to the record. Then you export an audit report as PDF or CSV for your file.

Four moments

  • Moment

    Before signing

    What you do

    Secure the draft with the pre-signing API, or drop it in a watched folder.

    What the other side can check

    Whether the draft they were shown is the same file, unchanged since its Observed Time.

  • Moment

    At signing

    What you do

    Nothing. The DocuSign rule secures the completed envelope as a post-signing contract record.

    What the other side can check

    Whether the executed file they hold matches the record: status, fingerprint, Network Receipt, Observed Time.

  • Moment

    After a change or in a dispute

    What you do

    Approve the new version, add an attestation, send the public ID, export the audit report.

    What the other side can check

    Which version came first and which replaced it, shown as linked versions, and the attestation by its own public ID.

  • Moment

    After the matter closes

    What you do

    Keep every record for the matter in one folder and tag it. Later, your agent can list the records by that tag through the MCP server and check each one by public ID.

    What the other side can check

    Each record in the set by its public ID. Folders and tags stay private; they never appear on the public proof.

A real example: our own board consent

On 2026-08-13, Arkova secured a completed DocuSign package as record ARK-DOC-2Z5WPG. It held our own contractor agreement and a board consent. Two weeks later, outside counsel asked for the executed consent. We sent the public ID so they could check the record at search.arkova.ai.

HakiChain, a legal technology company in Kenya, is a paid pilot customer securing legal records through the API.

What this does and does not prove

It proves
  • This exact file existed, unchanged, at the Observed Time.
  • Anyone can check that against a public permanent ledger, with no account.
It does not prove
  • Who signed, that the contents are true, or that the contract has legal effect.
  • That a file was never changed. A changed file will not match the record. That is tamper-evident. It does not stop anyone changing a file.
Connect DocuSignCheck a public ID

02 Changelogs, audit evidence and AI agent logs

Prove what changed, and when

Secure your changelogs, audit files and agent logs now, so anyone can check them against a public record later.

It is six weeks before your audit. The auditor will ask what changed in production and when. You do not want to rebuild that answer from memory.

So you connect the folder where your team keeps its changelog and change-management exports. Every new file is fingerprinted and secured. When someone edits a file, Arkova spots the change and holds it in a review queue. You approve it. The new version is secured and the old one is marked Superseded, with links both ways.

Your AI agent writes a log for each run: what it read, what it decided, what it changed. It pushes each log through the API itself, with its own key. Tag the logs for one system, and when a question comes up the agent can list them by that tag through the MCP server and check each one by public ID.

At audit time you export a report as a PDF or CSV. The auditor picks a sample and checks each file by its public ID, with no account. Each file either matches its record or it does not.

See how versions link

Three moments

  • Moment

    A file or log arrives

    What happens automatically

    It is fingerprinted and secured. It gets a public ID and a timeline entry. An agent can do this itself through the API or MCP.

    What the auditor can check

    The file against its public ID, with the Observed Time and Network Receipt.

  • Moment

    A file changes

    What happens automatically

    The change is detected and queued for review. After approval, the new version is secured and the old one is marked Superseded.

    What the auditor can check

    Every version in order, and when each one was secured.

  • Moment

    Audit day

    What happens automatically

    Export a report per record or per organization. See which controls your secured records evidence.

    What the auditor can check

    A sample of records, checked in one batch.

Three kinds of logs this fits

  • Product changelogs: Secure each CHANGELOG and set of release notes, so you can show what was published and when.
  • Change-management and access logs: Secure change tickets and access reviews as they are exported, so the evidence still holds up long after it was made.
  • AI agent run logs: Secure the log of each run, so a record of what the agent read, decided and changed exists outside the agent.

What this does and does not prove

It proves
  • A file existed, unchanged, at its Observed Time.
  • A later copy either matches the record or it does not. Any edit is tamper-evident.
It does not prove
  • That a log is complete, or that what it says is true.
  • That your controls pass an audit. Your auditor decides that.
Connect a folderSee how a public ID check works

03 For individuals

Keep a dated copy of what matters

Show that the copy you hold existed on a date and has not changed since.

Only 24% of Americans have a will (Caring.com, 2025).

Your will, every version

You revise your will or trust over the years. Each time, secure the new version. Arkova fingerprints the file in your browser, so it never leaves your device. You get a dated record with a public ID. Add it as a new version, and the old one stays checkable. Later, your family can check which version existed when. Keep it in a personal folder, private even from Arkova staff.

Your tax year, as a dated set

When you file, put your return and its supporting documents in one folder for that year. Secure each file. Each gets a public ID and a dated record. If a question comes up later, you can show that your copies existed on those dates and have not changed. Add a corrected form as a new version. The first stays checkable beside it. Arkova does not file anything or give tax advice.

Your credentials, in one place

Diplomas and licenses come up for proof every few years. Add them to My Credentials. Import from Credly or Accredible, or secure a file yourself. Each record gets a public ID that anyone can check with no account, and imports are labelled as account-linked evidence. Share your portfolio link with an employer or a licensing contact. Log CLE and CPE credits as you go. Arkova shows your copy is unchanged. It does not confirm a license is current.

How it works for you

  1. 01Add a file. It is fingerprinted in your browser and never leaves your device.
  2. 02Get a dated record with an Observed Time and a public ID.
  3. 03Share the ID or your portfolio link. Change one word later and it won't match.

What this does and does not do

Does
  • Shows that the copy you hold existed by its Observed Time and has not changed since.
  • Lets anyone check a record by public ID, with no account.
Does not
  • Replace a lawyer, a notary, a will registry or a filing with the IRS.
  • Make a document legally valid, or give legal or tax advice.
Start free: 3 records a monthCheck a record by public ID

Individual Verified adds 10 records a month and an identity checkmark.

DocuSign integration

Connect DocuSign and give selected completed documents a fingerprint, a public ID, and a Network Receipt. Signing shows who agreed. A fingerprint comparison shows whether a copy still matches what was signed.

How the connector works

Google Drive integration

Connect a Drive source and choose the documents to record. Each selected file is fingerprinted in server memory, discarded, and given a public record with an Observed Time. Nothing is copied out of your Drive.

How the connector works

Audit trail and version history

Every change, on the record. Every version, still provable.

When a document is updated, the earlier record is retired, not erased. The new version links back to the one it replaced, each keeps its own proof, and every action in between lands in an audit trail you can export.

Version history · Master services agreement3 versions
  1. v1
    OriginalApr 2 · 14:12 UTCARK-DOC-9Q1HTASUPERSEDED
  2. v2
    Updated versionMay 14 · 09:40 UTCARK-DOC-3F8Q2MSUPERSEDED
  3. v3
    Current · signedJun 30 · 16:05 UTCARK-DOC-M4K2VTSECURED
  • Nothing is overwritten. Each version keeps its own fingerprint, Network Receipt and Observed Time.
  • Links go both ways. The newer record names the one it replaced; the older one says what replaced it.
  • Changes are reviewed. A new version detected in a connected source waits for approval before it is anchored.
Audit trailPDFCSV
  1. Jun 30 16:05anchor.secured · v3 confirmed on the network
  2. Jun 30 15:51attestation.created · signed, DocuSign envelope
  3. Jun 30 15:50anchor.superseded · v2 retired by v3
  4. May 14 09:40anchor.created · v2 approved by J. Okafor
  5. May 13 22:10version.detected · new fingerprint in Drive, pending review
  6. Apr 2 14:20record.folder_changed · filed under Vendors / Acme
  7. Apr 2 14:12anchor.created · v1 uploaded by M. Reyes

Who did what, when, to which version. Export the report for your GRC platform or hand it straight to the auditor.

Link, tag, organize

Records that know how they relate

A proof on its own is a fact. A proof with its versions, its attestations, its folder and its tags is evidence you can actually use.

Linked records
Versions point at the record they replaced. Attestations point at the record they verify, endorse or audit. Follow the chain in either direction.
Private and organization tags
Tag a record for yourself or for the whole organization. Tags stay private. They never appear on the public proof.
Folders that mirror your sources
Nested folders, per person or per organization. Point a folder at a Drive location and new files are filed and secured as they arrive.
Attestations
Add a signed statement to any record: reviewed, approved, witnessed, audited. Attestations have their own proof and can be revoked with a reason.
Records/Vendors/Acme/Master services agreement
Status
SECURED · v3
Organization tags
acmemsafy26sox-302
Private tags
renewal-q3needs-legal
Source
Google Drive · Vendor contracts / Acme
Linked records
Attestations
  • Signed · counselACTIVE
  • Reviewed · J. OkaforACTIVE
Public proof
Shows status, fingerprint, time, issuer and lineage. Never shows tags, folders or the file.

Everything a record can do

The full map, in one place

A timestamp service gives you a date. Arkova gives the record a life: secured, organized, attested, proven, audited and automated.

See how it works
01 · Secure

Get a proof for anything

  • Fingerprinted in your browser; the file stays with you
  • Queue for free; records are secured in the next scheduled batch
  • Bulk upload from a spreadsheet, with per-row results
  • On-device text reading suggests fields; private details are stripped first
  • Revoke a record with a reason when it should no longer stand
02 · Organize

Keep the history straight

  • Nested folders, personal or organization-wide, with strict privacy
  • Private and organization tags that never appear publicly
  • Version history and supersede links in both directions
  • Conflict review when a connected file changes
  • Lifecycle timeline on every record
03 · Attest

Say something about a record

  • Attestations: reviewed, approved, witnessed, audited, with revocation
  • Credential templates for verified organizations
  • Import existing badges from Credly, Accredible or the Credential Engine registry
  • Public portfolios, issuer registry pages and member profiles
04 · Prove

Let anyone check, with or without us

  • Public Verify page: no login, no copy of the file
  • Drop a file to check it; it is fingerprinted on the visitor’s device
  • Verify without Arkova, with an open-source checker
  • Verification certificate PDF with a machine-readable proof packet
  • Every proof states what is measured, asserted and not asserted
05 · Audit

Hand the auditor what they asked for

  • Audit pack export, PDF or CSV, per record or whole organization
  • Framework coverage: which controls your records evidence
  • Audit My Organization scorecard with history
  • Auditor batch checks for SOC 2 and ISO 27001 samples
  • CLE and CPE logs and exports
06 · Automate

Make it happen without a person

  • Google Drive and DocuSign connectors feeding a rules engine
  • Signed webhooks with delivery history and resend
  • REST API, single and batch verify, scoped API keys
  • SDKs for TypeScript and Python
  • Hosted MCP server and per-agent keys for AI agents

How it works

Fingerprint. Anchor. Verify.

Three steps from a file to a checkable public record. Direct uploads stay on your device. No account is needed to check a record.

  1. 01

    Fingerprint

    A SHA-256 fingerprint of the document is computed in your browser for direct uploads, so the file stays on your device. Documents selected from a connected source are fingerprinted in server memory and discarded.

  2. 02

    Anchor

    The fingerprint is linked to an anchor on a public, permanent ledger that no single company controls, Arkova included. The public record shows a Network Receipt, a Network Checkpoint, and an Observed Time.

  3. 03

    Verify

    Anyone with the public ID can look the record up on this page, through the API, or with their own tooling. With a copy of the file, compare fingerprints to check whether it matches. No account required.

See the APIBook a demo

Why Arkova

Trust used to be assumed. Now it has to be shown.

Arkova fits the document workflows you already run and gives each record a reference that holds up later, in front of an auditor, a court, or a counterparty.

01
No single point of control
The anchor is recorded on a public ledger outside Arkova’s infrastructure. No vendor, Arkova included, can edit it or take it offline.
02
Simple, secure integration
A REST API, HMAC-signed webhooks, DocuSign and Google Drive connectors, and an MCP server for agent workflows. From one lookup to batch checks of 100 records a call.
03
Private by construction
Direct uploads are fingerprinted on your device. Arkova retains the fingerprint and limited metadata, not the original file.
04
Anyone can check
Looking up a public record is free and needs no account. A changed byte produces a different fingerprint, so a copy either matches the record or it does not.
05
Published security controls
Our controls are documented in the Cloud Security Alliance STAR Registry. CSA STAR Level 1 is a published self-assessment, not a third-party audit or certification. View our STAR Registry listing

Team

Built by people who have lived this problem

  • Carson Seeger, Founder & CEO at Arkova

    Carson Seeger

    Founder & CEO

    10+ years in technical product and program management across regulated industries. Built Arkova to give organizations verification infrastructure that outlasts any single vendor.

    LinkedIn
  • Sarah Rushton, Founder & COO at Arkova

    Sarah Rushton

    Founder & COO

    Over 20 years launching products through compliance-heavy supply chains taught Sarah one thing: documentation verification is broken at every level.

    LinkedIn
  • Dr. Yaacov Petscher, Founder & Advisor at Arkova

    Dr. Yaacov Petscher

    Founder & Advisor

    20 years Research & Data Science experience. Senior Member of the National Academy of Inventors.

    Google Scholar
  • Uyiosa Israel, Business Development, Africa at Arkova

    Uyiosa Israel

    Business Development, Africa

    Leads Arkova's business development across Africa. Represented Arkova at Decentralized World in Lagos in August 2026 and is building the Africa pipeline and the first Arkova Africa newsletter.

    LinkedIn

Partners and demo

Trusted for critical records

  • Legal technology · Kenya

    HakiChain

    HakiChain has announced Arkova for document-integrity checks in its HakiDocs workflow.

    Visit HakiChain
  • Agent identity · staging integration

    ComputeID

    ComputeID says its credential-revocation webhook integration with Arkova is moving into staging.

    Visit ComputeID
  • Digital finance · planned integration

    Certen Protocol

    Certen has announced plans to connect Arkova document checks to its authorization workflow.

    Visit Certen Protocol

Verify a real record

Don't take our word for it. Check one yourself.

Every record has a public ID. Look one up here or with a single API call to see the reported issuer, status, Observed Time, and Network Receipt. No account, and no copy of the original file, required. The lookup reports record details; it does not compare a file you hold.

Understand what a record can prove

Pre-filled with a real record — hit Verify to check it live, or see it on search.arkova.ai. Paste any Arkova public ID — no account needed.

Developers

Built for the systems you already run

Look up a public ID over REST, receive record events through signed webhooks, or let an agent call Arkova over MCP. From one lookup to batch checks of 100 records a call.

Discuss an integration
  • Single-call and batch lookup over REST. SDK arkova on npm and PyPI; command-line client arkova-api-cli on npm.
  • HMAC-signed webhooks and API keys
  • DocuSign and Google Drive connectors
  • MCP server for agents: arkova-mcp-server on npm. Confirm available tools with your account.

One public ID, one call

Run the same lookup the verifier makes, through the marketing-site proxy, and see the selected fields that come back.

API v2 is current. v1 stays supported until 23 April 2027.

GET https://api.arkova.ai/api/v1/verify/{publicId}

A single lookup needs no key. Batch checks (up to 100 public IDs a call) need an API key. This demo runs the lookup for ARK-DOC-HKUK9N through the marketing-site proxy.

Selected response fields
Press “Run it” to request this public ID through the marketing-site proxy.

These are selected fields from the response, not the complete API payload. A successful request is not a verdict about the document.

This page uses a same-origin proxy to request a public record. Responses may be cached, and requests may be logged.

Or get the event pushed to you

Webhooks can notify your endpoint about supported record events. The illustration below shows the handoff; it does not send an event or check a signature.

Webhook flow illustration

Example record details, not an exact webhook payload or API schema.

Public ID
ARK-DOC-2Z5WPG
Status at snapshot
ACTIVE
Network observed

In an integration, a webhook can notify your service about a record event. This example only illustrates the handoff.

Explore the handoff without sending a request.

Field notes

Notes from the field

All field notes
Article · Carson Seeger

The Missing Gap in the Agentic IAM Discussion

Agent identity and document integrity are separate checks. A public record and file fingerprint can help a reviewer trace a version without certifying its contents or issuer.

Read more →
Download the PDF
Arkova Monthly · September 2026

What we shipped, who we are working with, and what is next

Product, security, and partnership updates in Arkova Monthly. One email a month. The September 2026 issue is a dated archive of what the team was building then.

Read the issueSubscribe by emailPDF archive

Open a free account today

Create your first records in minutes. Looking up a public record stays free and needs no account.

Get started

Investor or partner? View the pitch deck or write to founders@arkova.ai.

Pitch deck

Arkova for investors and partners

The current deck, hosted on DocSend. Opens in a new tab.

Open the deck

Contact

Uphold the integrity of your records

Talk to the team about adding Arkova to your document workflow, your compliance program, or your product.

Talk to our teamfounders@arkova.ai

What skeptics ask

Common questions

What does Arkova actually do?

Arkova gives a document a fingerprint, public record ID, and network anchor reference. Anyone can look up the record. Someone with a copy of the file can compare fingerprints to check whether it matches. That comparison does not establish whether the document’s contents are true or who was authorized to issue it.

How is this different from DocuSign, a notary, or a timestamp service?

Electronic signatures, notarization, and timestamp services each address different parts of a document workflow. Arkova adds a public record and fingerprint reference for later file comparison. It can complement those services; a fingerprint match alone does not establish a signature’s validity, a signer’s identity, or a legal conclusion.

Do you store my documents?

We do not retain original documents. Files you upload directly are fingerprinted in your browser and stay on your device. If you select a document from a connected source such as DocuSign or Google Drive, Arkova fingerprints it in server memory and discards the file immediately. We retain the fingerprint and limited metadata. See our Privacy Policy for the full processing details.

Can my document be reconstructed from the fingerprint?

SHA-256 is designed to be one-way; the fingerprint is not a copy of the file. Someone with a candidate document can compute its fingerprint and compare it with a recorded value when available. A match alone does not establish whether the document’s contents are true or who issued it.

What does “tamper-evident” actually mean?

Compare a copy of the file with its recorded fingerprint when that value is available. A different fingerprint indicates different content. A public record lookup alone does not compare a file or establish that its contents are true.

What happens if Arkova goes away?

You do not need us to check a record. Each Network Receipt is recorded on a public permanent ledger outside Arkova, and anyone can confirm it on a public explorer with no Arkova access. Records secured since 24 April 2026 also offer a downloadable proof bundle from the verify page and the API, which can be checked independently with the steps on the Verify Without Arkova page at app.arkova.ai/verify/independent. Older records can be checked against their receipt and recorded fingerprint. For records secured from an upload, a copy of the file plus the record details is enough to check integrity; records pulled from a connected source such as DocuSign or Google Drive are checked against the record’s own retrieved artifact, since a copy downloaded again later may not match.

What is the “public network” you anchor to?

Arkova connects a public record to an anchor on a network outside Arkova’s infrastructure. The public record shows a network checkpoint and receipt. Those details help locate the anchor; they do not by themselves confirm a document’s contents or issuer.

How does someone verify a record?

Enter its public ID to review the reported status, issuer label, network observed time, checkpoint, and receipt. With a copy of the file, compare its fingerprint against the recorded one to check integrity. A lookup alone does not prove the contents are true or the issuer was authorized.

Can a record be revoked or corrected after it’s anchored?

The network anchor remains, while a record’s reported status can change. Arkova serves the current reported status, including revoked and superseded, on the verify page and through the API; cached results may lag recent changes. The issuer decides whether to revoke a record or replace it with a new version.

Can I integrate it with my systems?

Yes. The DocuSign and Google Drive connectors are live, so completed envelopes and watched folders are secured automatically. For your own systems there is a REST API, SDKs for TypeScript and Python, signed webhooks, and an MCP server for agents. Any of them can look up a record by its public ID.

Is it available now?

Yes. Arkova is live. Anyone can create an account at app.arkova.ai today: the free tier needs no payment, and paid plans are on the pricing page. Pilots and enterprise terms are a conversation; contact us.

Last updated: October 2026