Your account
Keep your stamps in one journal and carry the desk to another browser. Sign in with a one-time e-mail link, or Google or Microsoft where available — there is no password. Qualified timestamps depend on your balance and an answering provider. Checking a stamp is free and never needs an account.
A cart is waiting on this device
A plan or a block is in the cart. Pay from checkout, or edit it first.
Sign in
Use a one-time e-mail link. It works once, for 15 minutes, and signs in the device that opens it. No password exists to reset.
or
- Up to 21 qualified stamps to try, once per address, subject to qualified-provider availability — no card needed.
- Every stamp kept in your journal, so a cleared browser loses nothing.
- Checking stays free and anonymous, with or without an account.
New here? The seven-step quick start
A stamp shows that a file's fingerprint existed inside a time window; it never dates the original capture or says the content is true.
Signed in
Account
You are signed in. Your saved cloud workspace cannot safely be opened yet. It has not been imported, changed or deleted. Contact support for help.
Balance
—
Recent activity
All stampsNothing here yet. Drop a file on Stamp a file above: your first stamp shows here a few seconds later.
Storage
VaultVault — files kept beside their stamps
—
Desk saved to this account
—
Encrypted on your device before it is stored. Backed up every night.
Your stamps
Every stamp this account made, newest first. Open one to check it again on this device, download its .cts, or keep the original file in your own storage; hosted vault uploads are temporarily unavailable.
What the journal keeps
For a browser stamp, the sealed envelope itself — the .cts file — so a cleared browser is not the end of it. For an API stamp, the authorities' tokens only: the machine that sealed it holds the file and the envelope. Never the file, never a place.
Opening a stamp checks it again on this device against the pinned authorities; no server of ours grades it. Every night at 02:00 UTC all journal entries are folded into one root and that root is stamped the same way, so a later change to an entry would no longer match the anchored root. Browser stamps are renewed before their authorities' keys lapse (the switch is under Settings); API stamps are not renewed here.
Plan & billing
Change plan, buy a block of qualified stamps, or open Stripe for invoices, cards and cancelling. Prices exclude VAT: Stripe adds it once you enter your billing address.
In the United Kingdom OpenStamps is sold to businesses: Stripe's page will ask for your GB VAT number and the invoice is reverse-charged. A UK address without one is refused after payment and the money returned.
You are on a plan already, so moving up or down — and moving between monthly and yearly — happens on Stripe's pages, where the change is prorated against what you have paid.
Cards, Revolut Pay, invoices, receipts, VAT numbers and cancelling are all on Stripe's own pages: this site never sees a card number. A top-up block never expires.
More seats — add-ons on this plan; vault terms unavailable
Changed here, prorated by Stripe on the next invoice, at this plan's cadence. Up to the stated units each. Removing one at 0 takes it off the next invoice.
This deployment cannot take payment yet, so nothing here can be bought. The account still works and the stamps it makes still seal: they ask the free authorities, binding the new envelope to a beacon round and to the free timestamps that come back, without the qualified token a plan adds or proof of original capture time.
Stamps by month from your journal
| Month | Stamps | Bracketed | One-sided | Browser | API |
|---|
Counted from the journal, so only stamps made while signed in or through a key are here. The balance is the meter's own count and is what a plan is charged against; the two agree from 16 September 2026 on, and a bracketed stamp in a month with a qualified authority supplying tokens is a qualified stamp.
What else the plan carries seats, mailbox, backup
| What | On this plan |
|---|
Desk & suppliers
The desk is where you build a due-diligence file: products, suppliers' plot records, and the statement. While you are signed in it saves itself to this account, so it opens on any browser.
Synced to this account
Earlier versions the five before the latest write
Restoring a version makes it the account's current desk; every signed-in browser takes it on board the next time its desk syncs. The version you replace joins this list.
Up to 2 MB. Two browsers editing at once keep the later save per record. The bundle is stored as sent and read by nobody.
Requests to suppliers
A request's mailbox lives on this site for 14 days; the desk collects the replies. A supplier answering one never sees a balance or a price: your balance closes their stamp's time window.
The vault
Hosted vault uploads are temporarily unavailable. Keep originals and local exports. Eligible existing files remain readable. Plan sizes are nominal allowances, not available upload capacity. For files already stored, the vault shows the existing five-year storage term; choose the retention period required for your records and market. A stamp or vault does not itself establish regulatory compliance. The file is encrypted on this device with a passphrase only you hold; we store ciphertext and can decrypt nothing. A forgotten passphrase is a lost vault.
Where it is held: …
The passphrase never leaves this device. Write it down where the company keeps such things: it cannot be reset, only replaced while the vault is empty.
Saved companies
Your company and your suppliers' details, typed once. The desk fills its forms from them, and a stamp can name one in your journal. They never go into a stamp or a .cts, and nothing here is published.
EORI, VAT and registry numbers are checked for their shape only; nothing looks them up. Up to 25 companies, 8 addresses each.
Team
Several people on one balance. The owner's plan pays for every member's stamps; each member keeps their own sign-in, keys, journal and vault. Studio seats three, Works ten, Mill twenty-five, Plant seventy-five — the owner included.
Two devices in one room? Phone sync shows they were together. It does not locate a plot.
API & agents
Connect a script, an AI app or a browser assistant. Each uses a different route; checking an existing stamp needs no key.
Which connection do I need?
- API — your own software. Create a key below and keep it on your server. Request timestamps for a file's SHA-256 fingerprint. See the request and current limits.
- MCP — an AI app with MCP support. Run the local OpenStamps server in that app. The same API key can fund its timestamp requests; checking existing stamps needs no key. Setup below.
- WebMCP — an assistant in your browser. A compatible assistant can use tools on an OpenStamps page. No API key or MCP server setup. How to use it.
For a one-off file, Stamp & check is the simplest route.
API keys
Hosted API and MCP stamping requires a paid Stand plan or higher. Qualified tokens use your included allowance or bought blocks. Browser stamping and checking existing stamps stay free.
A key authorizes machine requests against this account, including timestamp requests and reading its saved company profiles. Anyone holding a key can spend this account's available balance. Use a separate labelled key per integration and revoke it below when it is no longer needed. Never put a key in a public page, URL or shared screenshot. It is shown once; only its SHA-256 is stored.
Copy this key now. It will never be shown again, and anyone holding it can spend this balance.
From an AI agent (MCP)
This is a local MCP server, not a hosted MCP URL. To connect it:
- Install Node.js 20 or later on the machine running your MCP app.
- Download the server linked below and keep it in a folder on that machine.
- In your app's MCP settings, add the command below with the file's full path. For requests funded by your account, add an API key from this page as
OPENSTAMPS_API_KEYin the app's private configuration. - Restart or reconnect the MCP server in your app, list its tools and try
verifyon a sample stamp first. This check is offline and spends nothing.
An agent that writes a report, a contract or a build can stamp it itself: openstamps-mcp.mjs is one file, Node 20 or later, no dependencies. Five tools — stamp, verify, balance, anchors, list_company_profiles (the companies saved on this account, so a stamp names one by id; its details go into the journal row, never into the .cts). The original file stays on the agent's machine; timestamp requests send its SHA-256. The .cts is written beside the file; verify is offline. With a key, the API records the request in your journal for the next Bitcoin batch. Without a key the agent still seals, one-sided, and the answer says so.
{ "mcpServers": { "openstamps": {
"command": "node", "args": ["/path/to/openstamps-mcp.mjs"],
"env": { "OPENSTAMPS_API_KEY": "osk_…" } } } }
The agent signs each seal with a P-256 key it keeps at ~/.openstamps/device-key.json (created once, readable only by you, never replaced — every OpenStamps agent process on the machine signs with that one key); its key hash is printed on every stamp and can be enrolled on the desk's reader roster like a phone's. Beside it, sequence.json numbers every coded record the agent seals (a stamp call with record) in one device sequence, so a missing number shows as a gap; keep the sealedText each answer returns, because that is what the stamp commits. File, text and digest stamps are never numbered. A stamp fixes bytes and time; it never says the content is true.
From a browser assistant (WebMCP)
Open Stamp & check or the reader, then use your compatible assistant's page-tool interface to choose openstamps_check_stamp. Give it the stamp text and, to compare an original, that file's SHA-256. The page checks locally; no API key is needed.
Other page tools read prices, explain where to go or prepare a problem report for you to send. They do not buy, spend your balance or submit the report. Availability depends on your browser and assistant exposing WebMCP; an ordinary chat window is not enough. If no page tools appear, use the page's normal controls or the local MCP server above.
Your API key, the MCP machine's signing key and your browser's signing key are different things. WebMCP does not connect accounts or transfer those keys.
Settings
E-mail from us, a copy of everything on your own drive, the app on your phone, signing out and closing the account.
Connecting software or an AI assistant? API, MCP and WebMCP setup explains which connection to use and what an API key allows.
E-mail from us off unless you switch it on
These billing preferences cover plain-text receipts and statements sent to this account's address. Sign-in and security messages are separate, as are any lifecycle email choices shown here.
A copy on your own drive
One zip with everything this account holds: every stamp's .cts from your journal, the desk as saved to the account, your saved companies, and the vault's files beside their stamps when the vault is unlocked. A README inside says what each part is and how to check a stamp.
Put together on this device from what your account already shows you, and written only where you choose: nothing is uploaded anywhere. This browser keeps the date of your last copy and nothing about the folder; Chrome and Edge may open the picker where you saved last time, which the browser remembers on its own.
Whisp FAO's deforestation-risk tool, from the desk
Reading…
What happens to your key. It is kept in this browser's own storage and nowhere else: not on your account, not on our servers, not on your other devices. When you press Screen with Whisp on the desk, this browser sends it with the plot outline to our /api/whisp, which hands it to Whisp for that one request and drops it. We never store it, never log it and never show it back. With your own key our daily allowance does not apply; Whisp's own limits do (30 requests a minute, two jobs at once). A key is free: sign in on Whisp's site (whisp.openforis.org), open your account and create an API key.
Identity check optional
This is optional: nothing about your stamps, your desk or your plan depends on it.
Who runs it. Didit, an identity-verification company, on its own pages, as our processor. You photograph an identity document and take a short selfie video; Didit reads the document, checks that the selfie is a live person and compares the face with the document's photo. Didit processes your face and document images, which are biometric and identity data. Read Didit's verification privacy notice and its end-user terms before you start.
What OpenStamps keeps. Only the result (approved, declined, in review, expired or abandoned), its date and time, Didit's session number, which checks ran, the issuing country and document type if Didit returns them, a SHA-256 fingerprint of Didit's decision, and when Didit deleted its copy. Never your images, face data, document number, date of birth, name or address.
What it does not say. That a document was read and a live face matched it, once, at Didit. Nothing about who made, approved or is responsible for any record. Didit's copy is deleted as soon as we receive the result: once Didit has decided, we keep the record above and ask Didit to delete the session, its images and its decision; if Didit does not answer, we ask again. Removing it deletes our record too (and asks Didit to delete the session if it still holds it); the button appears here once a check exists. See the privacy notice.
Display currency
Prices are shown in this currency on this browser. Conversions are indicative; checkout always charges euro.
Admin
You are an owner of this site. Open the admin · Operating numbers
Something wrong?
A person reads every report. Report a problem · Report a security concern
On your phone
Install the OpenStamps app: the plot page and the checker then open without signal. How to install it
Signing out clears the session on this device only. A subscription is cancelled on Stripe's own pages through Invoices, cards and cancelling under Plan & billing, or ends with the account below.
Close this account everything we hold, deleted
Closing deletes the journal, the desk on the account and its kept versions, every API key and the account record itself — at once, and for good. It also removes forecast-board account links, salted openings, their keys and linked envelopes; unlinked statistical rows remain in aggregate counts. A subscription runs to the end of the period already paid and is not renewed; Stripe keeps the invoices, as tax law obliges both of us. The records and .cts files you hold yourself are yours and are untouched. The same address may sign in again later and starts a fresh account, without a second trial.