For AI agents · community beta
Let your agent deliver a file anyone can check.
Your agent makes the final file, computes its SHA-256 fingerprint and records that fingerprint with ClearedBadge. You get the file, a receipt and a Verify link. The file itself does not go to ClearedBadge.
A real example. On 29 October 2026, ChatGPT made this PDF from one plain request and recorded it through this website: antwerpen-in-3-tips.pdf (44.5 kB).
Open its Verify link and drop the PDF on it: it matches. Change one byte and it no longer does. Checking needs no account and records nothing.
Beta Free, small limits. Records made now are real ClearedBadge records.
No ClearedBadge account is needed for the website route or your own code. The connector needs a ClearedBadge account; only a limited number are available during the beta.
You use an AI assistant
ChatGPT (Work mode, with its cloud browser)
Nothing to install, no ClearedBadge account.
Make [your result] as a PDF and record the final file via https://clrbadge-web.vercel.app. Give me the PDF, the receipt and the verification link.
ChatGPT asks you once to confirm the registration, because it accepts the Beta Terms and the Privacy Policy for you. In our tests, saying so in advance did not remove that question. Tested on 29 October 2026 with an account that already knew ClearedBadge; a completely new user has not been tested yet. The receipt arrives as text in the chat; the receipt file stays in ChatGPT's cloud browser.
Claude (claude.ai or the desktop app)
Once: add the ClearedBadge connector and sign in (setup). Beta accounts are limited.
Make [your result], save the final file and record it with ClearedBadge. Give me the file, the receipt and the Verify link.
Claude asks you to allow the ClearedBadge tool before it records. Tested in production on 29 October 2026.
You build an agent or app
From your own code: any language
No account, no key, no secret in your code.
Compute the SHA-256 of the final file and send only {"sha256":"…"} to
POST https://clrbadge-seven.vercel.app/record-file-hash. Keep the answer as the receipt and build the
Verify link from its badge_id. A small working example (Python, standard library):
record_file.py ·
README.
Beta limits for this public route (shared with the website's Record page): 5 registrations per connection per hour, 20 per day, and 500 per day in total; agents that share an IP address share its limit. Never retry a registration automatically: after a timeout or 5xx, a record may exist.
As an MCP tool: Claude Code, Gemini CLI, other MCP clients
Remote MCP server with sign-in: https://clrbadge-mcp.vercel.app/mcp
Tools: register_file_fingerprint (a file's SHA-256), register_event (a final JSON
result) and verify (compares, never records). Claude Code:
ClearedBadge plugin (currently describes
JSON results). Gemini CLI: setup.
Each account has a small registration quota, separate from the website's limits. Tested: Claude (desktop and claude.ai), the Claude Code plugin (sign-in and verify), Gemini CLI (sign-in and verify). Other MCP clients have not been tested.
What a match shows
That the file you compare has exactly the bytes whose fingerprint was recorded, at the recorded time. Not that its content is true, who made or sent it, or that anyone received it. With a fingerprint route ClearedBadge never receives the file, so it cannot tell which file a fingerprint belongs to. New records are currently not anchored on Arweave: the recorded time is ClearedBadge's own, without an independent external timestamp.
Tell us what happened
Worked, failed, or confusing? Open an issue on GitHub: your AI or client, the route you used, what you tried, and what happened. A non-confidential record ID helps. Never post tokens, passwords, confidential files or raw session logs.
Setup details and rules for agents
Connector setup
The connector URL is https://clrbadge-mcp.vercel.app/mcp. You sign in once with your e-mail address;
no API key needed. The beta admits a limited number of accounts, each with a limited number of registrations.
If no new accounts are available, your client may show only a general connection error.
Claude (desktop app or claude.ai)
- Add the connector. Customize → Connectors → + Add → Add custom connector (in some versions Settings → Connectors). Name it ClearedBadge, paste the connector URL, keep Use Claude's published identity, and add it.
- Sign in in the browser window that opens, or create an account.
- Ask, with ClearedBadge switched on in the chat (+ → Connectors), for example: “Make [your result], save the final file and record it with ClearedBadge.”
Gemini CLI
- In PowerShell or a terminal, once:
gemini mcp add --scope user --transport http clrbadge_mcp https://clrbadge-mcp.vercel.app/mcp - Start Gemini (restart it if it was open), then type
/mcp auth clrbadge_mcpand sign in in the browser. - Ask, as a normal prompt, to record the final result with ClearedBadge.
Your login only controls access. It is not a signature, and it is never part of a record or receipt. By connecting and signing in you accept the Beta Terms and the Privacy Policy.
Rules for agents
- Make the final file first, then register once, not for every step. Compute the SHA-256 with code over exactly the file you hand over.
- Never invent, rebuild or retype a record ID, hash or Verify link. Report what the service returned. If you cannot pass on the receipt file, copy the receipt text from the page exactly and say that it is copied.
- Say “recorded” only after a real successful answer, and “matches” only after a real comparison.
- If the outcome is unknown (for example a timeout), a record may exist: do not register again; report it. Registering again on purpose is the user's decision.
- If the file changes after recording, it no longer matches. Ask before recording the new version.
- No secrets, and personal data only if the user may share it with a third-party service.
A JSON event (register_event) is compared by its content (RFC 8785), not as a file. Machine-readable
instructions: llms.txt. API details: Docs → Record.