Editors and publishers
Resolving an InkID before a piece runs. Verifying a writer's claim against the publisher's catalogue. Settling authorship disputes between co-writers without depending on the platform's arbitration.
InkVerify — Public resolver · Live at inkverify.co
InkVerify
/ˈɪŋk-vɛr-ə-faɪ/
noun.
The public resolver for the InkID protocol. Any record. Any reader. No account.
Any InkID. Any reader. No account.
InkVerify is the public surface of the protocol. Anyone with an InkID can paste it into the resolver and see the underlying record — the anchor, the evidence, the writer's chosen disclosure. No account. No fee. No platform sitting between the proof and the person checking it.
Why it's free
The proof of authorship belongs in the open.
Verification systems live and die on the question of who verifies the verifier. A protocol that controls its own resolver controls its own truth. A protocol that resolves in public, on a surface anyone can use without permission, is a different kind of claim.
InkVerify exists because the protocol could not exist without it. Every InkID resolves the same way for every reader — journalist, lawyer, publisher, casual subscriber, or skeptic. The record is the record. The protocol does not get to choose what it shows.
No account. No login. No fee. No gate. No identity-attached tracking. The resolver makes a direct, anonymous read against the public record; InkID does not see who is checking what. The verification surface is itself the protocol's commitment.
Open verification is not a feature of the protocol. It is the protocol.
The InkID protocol commitment · §1
Voice, verified
A pact between the writer and the reader, restored.
For a serious writer, the voice is the work. It is what took years to find and what distinguishes one page from another in a world drowning in pages. In the age of AI slop, that voice is being mass-imitated — and the reader, increasingly, cannot tell.
InkVerify is how the voice gets back.
For the writer, every InkID is a record of the work — proof, when proof is needed, that the line was theirs. For the reader, every resolved InkID is a moment of clarity — a way to know, when knowing matters, that the page in front of them was made by a person.
The pact between writer and reader has always been simple. The writer brings their attention, their craft, their hours. The reader brings their attention back. Both sides assumed the other was human.
That assumption is no longer free. The InkID protocol gives the writer a way to make their half of the pact provable. InkVerify gives the reader a way to check it — without paying, without signing up, without anyone's permission to consult the record.
The voice is yours. The proof is public. The pact stands.
What you see
Three things, in the open.
When you resolve an InkID at inkverify.co, you see exactly what the writer chose to publish. The record is structured to be readable by a human in under thirty seconds and parseable by a machine for editorial or legal review.
-
i · The anchor
The anchor
The independent RFC 3161 timestamp, with the Time-Stamp Authority named (FreeTSA at launch; redundant anchors planned). The token can be verified against the TSA directly, outside InkID's platform. If the protocol disappeared tomorrow, the anchor token would still resolve.
-
ii · The evidence
The evidence
The behavioral dimensions captured during the writing session — what was recorded, when, and how. The methodology is public. The per-author calibration is not. Kerckhoffs's principle, applied to authorship.
-
iii · The author's choices
The author's choices
The writer's chosen disclosure state. What they made public. What they did not. The protocol respects the writer's selection; the resolver shows only what the writer made available.
For
The reader. The editor. The lawyer. The skeptic.
InkVerify gets used by people the protocol could not have designed for in advance — and by design.
Journalists
Checking a source's claim of authorship. Verifying a quote attribution. Reading the session timeline behind a published essay.
Lawyers
Pulling the underlying timestamped record for evidence. Comparing co-writer attribution against split-sheet claims. Documenting authorship in pre-litigation discovery.
Readers
The Substack subscriber. The novel reader. The publisher's contract counterparty. The person who saw an InkID reference on a piece and wanted to know what was behind it.
Skeptics
The reporter writing about authorship infrastructure. The competitor reviewing the protocol. The academic studying verification systems. The resolver is open to them, too. By design.
Try it here
The embedded widget on the InkID homepage is InkVerify.
The verification widget at the top of inkid.io's homepage is InkVerify. Paste any InkID into that field — or open inkverify.co directly — and the record resolves inline. Same resolver. Same record. Two surfaces for the same protocol commitment.