Writermark
Open protocol to help prove text is human-written
Last verified:
What is Writermark?
Writermark is an online certification and verification service that assesses whether a piece of writing meets a high standard of human-produced, plain-language composition and interactional authenticity. It runs a lightweight client-side editor and telemetry-based analysis that records typing behaviour (keystroke timing, total time on document, and other non-identifying metrics) as evidence that text was produced through natural human composition rather than pasted or generated instantly. When a submission attains a high enough behavioural score, Writermark issues a cryptographically signed certificate that can be stored locally and later verified via the service’s verification endpoint. The service is designed to be integrated into other apps (there is an SDK) and also to be used through partner apps (for example, desktop writing apps that include automatic certification). Writermark positions itself for writers, publishers, organizations needing provenance for authored text, and developers who want to add human-authorship proofing into their platforms. Key features include a live try-it demo, an SDK for developers, a verification page to validate certificates, and an approach that keeps servers stateless by storing certification data locally in signed tokens.
Writermark pricing
Pricing model: Freemium
The website describes Writermark as an open protocol and provides free tools such as an in-browser demo and an SDK for developers; partner applications (like some free desktop writing apps) include Writermark support at no cost to the user. The service emphasizes local, client-side certificate creation and provides verification services; formal paid plan details or subscription tiers are not listed on the public site documentation, suggesting core functionality (try/demo, SDK, verification) is available without a published paid plan on the site.
Writermark pros
- Telemetry-based detection of human typing behaviour
- Issues cryptographically signed certificates for verified documents
- Certificate verification endpoint for later validation
- Client-side, privacy-preserving storage of certification data
- Stateless server design that stores no user documents centrally
- Live demo to test the process in-browser
- SDK available for easy developer integration
- Works with partner apps and desktop clients
- Records non-identifying metrics like total time on document
- Prevents simple paste-and-submit cheating attempts
- Supports export and verification of standard document formats in partner apps
- Clear developer documentation and npm package availability
- Certificate format bundled with documents in supported apps
- Provides a measurable score indicating authenticity
- Designed for both single-document and integrated workflows
Writermark cons
- Relies on keystroke telemetry which can be affected by atypical typing patterns
- May not distinguish well between assisted human editing and genuine full-generation
- Requires user acceptance of local telemetry collection during writing
- Certification depends on achieving a threshold score which can exclude valid human work
- Not a universal proof against sophisticated synthetic workflows
- Integration requires developer implementation (SDK integration work)
- Partner app support needed for seamless document embedding
- Does not store full documents on server so centralized archival is not provided
Frequently asked questions about Writermark
How does Writermark prove text was written by a human?
Writermark collects non-identifying telemetry—keystroke timings, total time spent on the document, and similar behavioural metrics—while the user composes text; it analyses that behaviour to produce a score and, if the score meets the threshold, issues a cryptographically signed certificate that proves the document was composed through interactive typing rather than instant pasting or simple automated generation.
Where is my text stored when I use Writermark?
The Writermark approach keeps the server stateless: the certificate and necessary verification data are stored locally on the user’s machine inside a server-signed token or bundled file, so the service does not retain full documents centrally.
Can I verify a certificate later?
Yes—Writermark provides a verification endpoint (a verify page) that allows anyone with the certificate or token to confirm the certificate’s authenticity and that the document met the required behavioural score at the time of certification.
Is there an SDK to add Writermark to my app?
Yes—Writermark publishes an SDK package (for example via npm) and developer documentation so applications can integrate the telemetry capture, scoring, and certificate issuance flow into their own editors or workflows.
Does Writermark collect personally identifying data?
No—the service describes telemetry as anonymous and non-identifying; it focuses on behavioural metrics (timings, durations, keystroke patterns) rather than storing personal content on servers, and certificates are produced in a privacy-preserving manner.
What happens if my document doesn’t reach the score threshold?
If the behavioural analysis score does not meet the threshold required for issuance, Writermark will not issue a certificate; users can revise and continue composing to generate stronger interaction evidence or retry the process to attempt to meet the threshold.
Can Writermark detect pasted or imported text?
Yes—the telemetry and heuristics are designed to detect behavioural patterns consistent with pasting or rapid import of text so that such content will typically fail to reach the certification threshold unless further legitimately typed interaction occurs.
Which file formats and apps support embedding Writermark certificates?
Writermark is designed to integrate with partner apps and toolchains; example partner workflows bundle certificates with documents (some desktop apps export certified .wtxt packages and support export/verification for .docx, .md, and .rtf), while direct integration into other platforms is possible via the SDK.
Does Writermark require an account?
No persistent user account is required for the core certification flow because certificates are produced and stored locally; integration models may vary if partner applications add user-account layers, but the protocol itself emphasizes a stateless, local-first model.
Is Writermark intended as proof against advanced AI-assisted writing?
Writermark aims to provide behavioural evidence that text was produced interactively by a human, which raises the bar against simple automated or pasted content; however, the system does not claim absolute immunity to sophisticated mixed human＋AI workflows and focuses on providing verifiable provenance rather than an infallible detector.