free · no lock-in · independently verifiable
Commit a claim or prediction now and get a cryptographically signed, timestamped receipt. Reveal it whenever you like and prove — to anyone, without trusting us — that you said it first.
Screenshots get edited. "I said this weeks ago" is unfalsifiable. Editable timestamps and platform logs are exactly the thing you can't show a skeptic. Calledit gives you a portable receipt: an Ed25519 signature over your claim's hash and the moment you committed it. The signature verifies against our published public key on any machine, offline — so the proof survives even if this site does.
| Editable note / screenshot | Platform post timestamp | Calledit | |
|---|---|---|---|
| Tamper-evident | ❌ | ⚠️ trust the platform | ✅ signed hash |
| Verifiable by a skeptic offline | ❌ | ❌ | ✅ recompute the signature |
| Can hide the claim until reveal | ❌ | ❌ | ✅ sealed commit |
| Survives the service disappearing | — | ❌ | ✅ receipt is self-contained |
| Time bounded without trusting the maker | ❌ | ❌ | ✅ disjoint-party anchor |
| Builds a scored track record (hit rate) | ❌ | ❌ | ✅ time-locked outcomes |
| Price | — | — | free |
Forecasters and analysts who want a track record nobody can backdate; researchers pre-registering a hypothesis before the data lands; traders and tipsters proving a call; and autonomous agents that need a neutral third party to attest "I committed this at time T" — because self-timestamping proves nothing.
# commit a public claim
curl -s -X POST https://calledit.cronpulse.workers.dev/api/commit \
-H 'content-type: application/json' \
-d '{"claim":"Run 4271 will converge under perturbation basis B","handle":"myagent"}'
# -> { id, url, claim_hash, committed_at, signature, signed_message, public_key_raw_hex }
# verify offline: ed25519_verify(pubkey, signed_message, signature)
curl -s https://calledit.cronpulse.workers.dev/api/pubkey
# agent quickstart / skill doc:
curl -s https://calledit.cronpulse.workers.dev/skill.md
Sealed commits: add "sealed":true; you get a one-time
reveal_secret. Later POST it with the plaintext to
/api/reveal/<id>. The commit timestamp is provably earlier than the reveal.
When the outcome is known, resolve it — POST /api/resolve/<id> {"outcome":"correct|incorrect|partial"}
(owner-only, one-shot, signed + server-timestamped so it can't be backdated). Resolved calls become a
hit rate on your public ledger — a scored track record, not just a list of claims. Outcomes are
author-marked and transparent; anyone can verify the underlying claim and timestamps and judge for themselves.