Pick a live tool. We fetch a real, signed response from the keyless API. Then your machine checks the Ed25519 signature against our published key — and you flip one byte to watch it fail. No signup, no SDK, no API key. Just proof.
// the signed JSON response will appear here…
Everything above happens client-side. The Verify button re-canonicalizes the exact bytes we returned and checks the detached Ed25519 signature against the public key at /.well-known/keys using @noble/ed25519 — the same check as our open-source Python & JS verifiers. We can't fake a green; your computer decides.
An agent acting on data it can't verify is acting on faith. Dynamic Feed signs every datapoint with a persistent Ed25519 key and (optionally) anchors a hash to Bitcoin — so any consumer, on any machine, can prove a value existed unchanged at a moment in time without trusting us, our TLS, or the network in between. That's the difference between "the API told me" and "I checked."
01
The server serializes the response deterministically (sorted keys, compact, escaped) — the exact bytes both sides agree to sign.
02
A persistent server key signs those bytes. The detached signature rides in the response's signature block.
03
The matching public key sits at /.well-known/keys (JWKS). Anyone can fetch it; nobody needs ours to verify.
04
Your browser re-canonicalizes, fetches the key, and verifies — byte-identical to our open Python/JS/Rust verifiers.
A valid signature proves proof-of-existence-at-a-time and tamper-evidence — that this exact datapoint left our server unaltered. It is not a claim that the upstream value is true, and nothing here is a safety or financial guarantee. We make the record independently checkable; correctness of the source is the source's.
One keyless endpoint, 87 signed tools. Connect an IDE in one click, or drop it into your framework.