The history nobody else can backfill.
Live data is ephemeral — once a value changes, the old one is usually gone. So Dynamic Feed continuously appends the datapoints it serves to a durable, append-only archive as they're served, each row carrying the same source, exact timestamp and Ed25519 signature it was served with. The result is a growing record of what was on the wire, and when — the one asset a competitor can't manufacture later, because they didn't capture the past and the past doesn't come back.
You can't prove what was true last Tuesday.
Almost every live API hands back the value right now and overwrites the last one. Ask it what the air quality, the exchange-listed status, the CVE count or the river level was at 14:00 last Tuesday, and it can't tell you — that reading was never kept. For anything that's later contested — a claim, an audit, an AI decision, a model's training cutoff — the input that mattered has already evaporated.
Backfilling doesn't fix it. A scrape gathered after the fact is just a guess about the past dressed up as a record. The only trustworthy history is one that was captured at the moment it existed — and signed so any later rewrite would be detectable.
Capture it once, keep it on record.
Values Dynamic Feed serves are continuously appended to a durable, append-only store — partitioned by tool and date, written as we serve them. Nothing already written is overwritten or deleted.
Written, never rewritten
Each served datapoint is appended as a new immutable object. The archive only ever grows — there's no edit path, and any change to a written row would break its signature, so a value can't be silently changed without detection.
Tamper-evident rows
Each row carries the same Ed25519 signature and provenance envelope it was served with — verifiable against the published key, so you can confirm a record hasn't been altered since it was written.
A moat that grows daily
The longer it runs, the deeper the record — and the further behind anyone starting today falls. The past is the one dataset that can't be bought or re-collected.
See what's on record — right now.
This reads live from /v1/history. Pick any tool and you'll see the days Dynamic Feed has captured for it — pulled straight from the archive, not a mock-up. Teal means a partition exists for that day.
This is an availability index: which days are on record for a tool. The signature on the response lets you confirm it came from Dynamic Feed and hasn't been altered since it was written. It does not assert the underlying values were objectively true — many are model forecasts, and signing proves a record existed and is intact, not that it's correct. The day-level point-in-time values (the exact value we served on a given day) are retained in the archive and available as a premium export — talk to us.
One keyless call to the availability index.
List what's captured
GET /v1/history returns the set of tools on record, with a count. Keyless.
Inspect one tool
GET /v1/history?tool=earthquakes returns its captured date partitions, earliest, latest and day count.
Verify the response
The response is Ed25519-signed — re-check it on the verify page or with the open-source verifier. Trust nothing on our say-so.
Three moats lock together here.
Permanence is the asset: a record of the past that grows every day and can't be back-collected. Proof makes it trustworthy: every row is signed, so the history is verifiable, not just asserted. Ubiquity makes it reachable: the same archive sits under a keyless API and MCP server any agent can call. A competitor can copy the code in a week — but on day one their history is empty, and ours is months deep. That gap only widens.
A faithful record — not a claim of truth.
The archive records what Dynamic Feed served, and when — captured as it happened and signed so it can be re-checked. A valid signature shows a record existed at a time and has not been altered since (tamper-evident, not tamper-proof); it does not prove the value was objectively true, complete, or that acting on it was correct. Many readings are model forecasts, not measurements. Treat the history as one independent, verifiable input — never the sole basis for a decision. This is data and provenance, not financial, legal, medical or safety advice.
Start your own record.
Call a feed today and the value is captured the moment it's served. The longer you wait to start, the more history you'll never get back.