NOTARY · LIVE·WITNESSED · LOGGED · TIMESTAMPED
DATA WITH RECEIPTS · ED25519 · RFC 3161·--:--:-- UTC
THE WITNESS LAYER · PUBLIC LOG · RFC 3161 TIMESTAMPED

Your data,
witnessed.
Provable, even against us.

One call notarizes any payload, or just its hash, into a signed record and a public, append-only transparency log whose head is time-stamped daily by an independent RFC 3161 authority. Like Let’s Encrypt, for data feeds.

# witness a reading from YOUR feed (free key: POST /signup)
$ curl -X POST dynamicfeed.ai/v1/notarize -H "X-API-Key: $KEY" -d '{"payload":{"rain_mm":18.4}}'
$ notary early access — request access ↗ developer quickstart ↗ browse the public log ↗
⬢ TRANSPARENCY LOG · LIVE, entries
…loading the public log…
Browse the full log →
FOUR WAYS IN

Witnessed, your way.

Every mode ends the same place: a signed record, a public log entry, an RFC 3161 timestamped history.

01 · PAYLOADSend the dataPOST your JSON, we hash it canonically, sign a witness receipt, and log it. The record can echo your payload or omit it.● POST /v1/notarize
02 · HASH-ONLYKeep it privateSend only a sha256. We witness the hash, your bytes never leave your infrastructure. Private by construction.● {"payload_sha256": "…"}
03 · BYO-KEYSign it yourselfAdd your own Ed25519 signature over the hash. We verify it BEFORE witnessing: "provider signed, Dynamic Feed witnessed", two-party proof.● provider_pubkey + provider_sig
04 · CONTINUOUSRegister your feedGive us a URL and an interval, every change your feed publishes is fetched and notarized automatically. A standing history of what you served, when.● POST /v1/notary/feeds
THE LOGPublic & append-onlyEvery notarization lands in a transparency log anyone can replay: alter one entry and every hash after it breaks. Hashes only, never payloads.● GET /v1/notary/log
THE TIMESTAMPRFC 3161, dailyThe log head is time-stamped every day by an independent RFC 3161 authority. Instant. Inclusion proofs connect any entry to the time-stamped head, no trust in us required.● GET /v1/notary/log/{i}/proof
WHY A WITNESS LAYER

Because "trust our feed" isn’t evidence.

01
Disputes end in 30 seconds.

When a customer, auditor or insurer asks what your feed said at 09:41 on March 3rd, you point at a signed record in a public log time-stamped by an independent RFC 3161 authority, not at your own database.

02
No signing stack to build.

Key management, canonicalization, transparency logging, RFC 3161 timestamping, done. One API call from any language, verifiers published in Python, JavaScript and Rust.

03
A witness, not an auditor.

A notarization attests that these exact bytes existed at this moment, never that the content is true. That honest line is printed inside every record we sign.

THREE CALLS · FULL CHAIN OF PROOF
# 1) witness it (or send payload_sha256, hash-only)
curl -X POST dynamicfeed.ai/v1/notarize -H "X-API-Key: $KEY" \
  -d '{"payload": {"gauge":"river-7","level_m":2.41},
       "subject": "Acme Sensors Pty Ltd"}'

# 2) see it in the public log
curl dynamicfeed.ai/v1/notary/log

# 3) inclusion proof to the RFC 3161 timestamped head
curl dynamicfeed.ai/v1/notary/log/1/proof
NOTARY BETA

Notary plans: early access.

Cheaper than one hour of the engineer who’d otherwise build your signing stack.

● BETA · SWITCHED ON BY EMAIL · CANCEL ANYTIME

  • 10,000 notarizations a month, payload, hash-only or BYO-key
  • Up to 3 continuous feeds, fetched and witnessed on your interval
  • Every record in the public transparency log, head RFC 3161 timestamped daily
  • Open verifiers (Python · JS · Rust), your customers verify without an account
  • Try it first on any free key’s quota, no card to start
  • Per-receipt enterprise pricing for insurers & platforms
$ join the notary beta ↗ read the full pitch ↗

A notarization witnesses bytes, it is not an endorsement of content · [email protected]