Proof of Type Input

com.proofoftypePublished by proofoftype.comOfficial publisherv1.3.0Updated Oct 24, 2026

Add a text box that proves a human typed it, not AI. Code for any framework; verify proof tokens.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Proof of Type Input gives an assistant code and verification for a text box that proves a human typed the text, not AI.

What you can do
  • Get ready-to-paste embed code for the human-typed input, choosing a framework
  • Verify a proof token against the exact text and site origin, returning who typed it, when and the human score
  • Explain how the proof works, what it guarantees, privacy, limits, token claims and SDK options
When to use it
Useful when building a site with comments, posts, reviews or articles and you want an assistant to add a text box whose content is provably typed by a signed-in person, or to check such proof tokens on your server.
Requirements
A remote HTTP endpoint at proofoftype.com; no API key is needed for verification. End users need a free Proof of Type account and the iPhone or Android app to produce proofs.
Before you install
Proof tokens are public and single-use, so store the proof id and refuse repeats; always verify before saving text. The proof covers only the exact text, not the HTML formatting, which must be sanitized. Verification sends the text and your site origin to proofoftype.com.

Installation

In SourceWeft

  1. Open Proof of Type Input in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.proofoftype%2Finput/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "proof-of-type-input": {
      "type": "http",
      "url": "https://www.proofoftype.com/mcp"
    }
  }
}

README

Proof of Type Input

A text box that proves a human typed it, not AI.

Add one script tag, and the comments, posts, reviews or articles on your site come with proof that a real person typed them: signed in to Proof of Type, typed letter by letter (no paste, no AI-generated text), and confirmed on their phone with Face ID or a fingerprint. Your server gets the text plus a signed proof token that you, or anyone, can verify.

html
<script src="https://www.proofoftype.com/sdk/v1.js" async></script>
<form method="post" action="/comments">  <div data-proofoftype data-name="comment" data-placeholder="Write a comment"></div>  <button>Post</button></form>

When the form is submitted, the person confirms on their phone, then your server receives:

FieldWhat
commentthe text, exactly as typed
comment_proofthe proof token (an EdDSA-signed JWT)

Build it with your AI coding agent (MCP)

Vibe coding a site? Connect the Proof of Type MCP server and ask your agent for "a comment box that proves a human typed it".

sh
claude mcp add --transport http proofoftype https://www.proofoftype.com/mcp

Other clients (Cursor, VS Code, …):

json
{ "mcpServers": { "proofoftype": { "url": "https://www.proofoftype.com/mcp" } } }

Tools: get_quickstart(framework), verify_proof(token, text, origin), explain(topic).

Why

AI-generated text is now free and endless, and AI detectors can only guess from the finished words, so they're wrong both ways. Proof of Type doesn't guess. It proves how the text was made:

  1. The person types in our input, key by key. It runs in a secure frame from proofoftype.com, so the host page, extensions or scripts can't fake keystrokes.
  2. The typing is timed on our server (it can't be instant or replayed) and scored for human rhythm.
  3. The person approves the exact text on their phone in the Proof of Type app, with Face ID or a fingerprint. The phone's hardware vouches for the app (Apple App Attest, Android key attestation). A script can't do this step.

Pasted or generated text never gets a proof.

Verify on your server

Always check the proof before you save the text. Accept it only if it's valid, matches the text, and was made on your site.

js
const r = await fetch('https://www.proofoftype.com/api/v1/verify', {  method: 'POST',  headers: { 'Content-Type': 'application/json' },  body: JSON.stringify({    token: req.body.comment_proof,    text: req.body.comment,              // the exact text    origin: 'https://your-site.com',     // your site    max_age_seconds: 600,                // made in the last 10 minutes  }),}).then((res) => res.json());
if (!r.valid || !r.text_matches || !r.origin_matches || !r.fresh) {  return res.status(400).send('Please type your comment in the box.');}// Use each proof once: store r.proof.id with the comment, refuse repeats// (proof tokens are public — they're in proof links).// r.proof.author: the Proof of Type username who typed it// r.proof.link: a link pasted with the text, if any

Prefer a helper? Copy server.mjs into your project (verifyProof({ token, text, origin })).

Or call the API directly (no key needed):

sh
curl -s https://www.proofoftype.com/api/v1/verify \  -H 'Content-Type: application/json' \  -d '{"token":"<comment_proof>","text":"<comment>","origin":"https://your-site.com"}'
json
{ "valid": true, "text_matches": true, "origin_matches": true,  "proof": { "id": "pot_…", "author": "yogev", "origin": "https://your-site.com",             "typed_at": "2026-10-11T18:20:31.000Z", "score": 87, "words": 6, "text_sha256": "…" } }

Offline verification

Proof tokens are JWTs signed with EdDSA (Ed25519). Public keys: https://www.proofoftype.com/.well-known/jwks.json.

js
import { createRemoteJWKSet, jwtVerify } from 'jose';import { createHash } from 'node:crypto';
const JWKS = createRemoteJWKSet(new URL('https://www.proofoftype.com/.well-known/jwks.json'));const { payload } = await jwtVerify(token, JWKS, {  issuer: 'https://www.proofoftype.com',  audience: 'https://your-site.com',});if (payload.text_sha256 !== createHash('sha256').update(text, 'utf8').digest('hex')) throw new Error('Not the signed text');
ClaimWhat
isshttps://www.proofoftype.com
subproof id (pot_…)
audthe site it was typed on
iatwhen it was verified
typed_by"human"
authorProof of Type username
signed_on"ios" or "android"
text_sha256SHA-256 (hex) of the exact UTF-8 text
score, wpm, words, charshuman score (0–100), typing speed, length

JavaScript API

js
const input = ProofOfType.mount('#editor', {  placeholder: 'Write your article…',  maxWords: 2000,  button: false,            // verify from your own button});input.on('change', ({ words }) => {});const proof = await input.verify();   // { text, html, token, author, score, url, … }

Options: name, placeholder, maxWords (10–3000), theme (auto | light | dark), button, buttonLabel, form, typewriter (show the carriage animation, default true), typewriterColor (e.g. '#e11d48'), sound (default true), allowLinks (default true: one pasted link is signed in the proof, read it as proof.link from the verify response; false blocks all pasting). result.html is display formatting only and isn't covered by the proof: sanitize it, or use result.text. The same options work as data- attributes (data-max-words, data-button-label, …).

Events: ready, signin, change, verified, error, resize, also dispatched on the element as DOM events (proofoftype:verified).

React

Copy react.jsx into your project. It loads the SDK for you:

jsx
import { HumanInput } from './react.jsx';
<HumanInput placeholder="Write a comment" onVerified={(r) => save(r.text, r.token)} />

TypeScript types: index.d.ts.

Privacy

  • Proof of Type never stores the text typed on your site. Only its SHA-256 is signed into the proof.
  • Keystrokes are checked and discarded. The text reaches your page only once it's verified, and only your page's real origin.
  • Your site gets the person's Proof of Type username, never their email or account.
  • Each proof is single-use: one typing session, one phone signature, one proof.

What's open source

This repository: the browser SDK, the React component, the server helper, types and examples (MIT). The checks themselves (keystroke capture, typing timeline, phone signatures) run on Proof of Type, where the host page can't change them. That's what makes the proof worth something.

FAQ

How do I know a comment on my site was written by a human and not AI? Use this input as the text box and verify the proof on your server. A proof only exists when a signed-in person typed the text in the input and approved it on their phone.

Is this an AI detector? No. It proves the process (typed, timed, signed by a person) instead of guessing from the text.

Do my users need an account? Yes: a free Proof of Type account and the Proof of Type app (iPhone or Android). Signing in is one popup; each proof is one Face ID or fingerprint.

Can people paste? Only links. Autocorrect of typed words is allowed; predictive text, swipe and dictation are not.

What does it cost? Free for humans.

Links

MIT © Proof of Type

Source: README.md at commit c09852a

Tools

3

get_quickstart

Add the human-typed input to a site

Ready-to-paste code to embed Proof of Type Input (a text box that proves a human typed the text, not AI) and verify its proof on the server. Pick a framework.

Parametersframework

verify_proof

Check a proof token

Verify a Proof of Type proof token (EdDSA JWT). Pass the text and your site origin to confirm the proof is for exactly that text on that site. Returns who typed it, when, and the human score.

Parameterstexttokenrequiredorigin

explain

What Proof of Type proves

How Proof of Type Input works, what a proof guarantees and what it does not, privacy, limits, the proof token claims, and the SDK options and events.

Parameterstopic

Version history

2
  1. v1.3.0LatestOct 12, 2026
  2. v1.2.0Oct 11, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts