Introducing /verify and /partners.

LAUNCH · 2026-07-18

1What /verify does

/verify opens a real Dynamic Feed receipt — signature, sources, freshness, integrity state and known limitations — and re-checks the Ed25519 signature in your own browser, not on our word. You can load a live example (NOAA space weather, CISA KEV, NWS alerts), paste your own receipt JSON, upload a file, or fetch one by URL. A tamper laboratory lets you alter one field at a time and watch verification fail, so the failure mode is as inspectable as the success case.

A valid signature proves the signed receipt has not been altered and identifies the signing key. It does not, by itself, prove objective truth, completeness or safety. /verify states that boundary on the page, not just here.

2What /partners does

/partners is Bring us one AI decision: a bounded 30-day pilot on a single consequential workflow. You describe one automated or AI-supported decision and the external data it consumes; we map the evidence chain, identify what can be cryptographically verified today, wire signed evidence for those inputs over REST or MCP, and hand you the same verification path published on /verify. Typical engineering effort on your side is hours, not weeks, and the exit criteria are agreed up front — a receipt exists, it verifies independently, and it honestly records freshness and stale/unavailable states.

3Get started in three steps

1. Verify something first. Open /verify, load a live example, and confirm the signature yourself before trusting anything else on this page.
2. Call the API keyless. POST one batch call to /v1/batch or connect the MCP endpoint — no account required to start (examples below).
3. If a decision depends on it, apply as a design partner. Describe the decision on /partners; the pilot exists to find out whether the evidence chain closes for your case, in 30 days.

4Integration examples

MCP — initialize, then list tools (keyless, streamable HTTP):

{ "mcpServers": { "dynamic-feed": { "url": "https://dynamicfeed.ai/mcp" } } }

// Raw JSON-RPC over the same endpoint, if you are not using an MCP client SDK:
// 1) initialize
curl -sX POST https://dynamicfeed.ai/mcp -H 'content-type: application/json' -d '{
  "jsonrpc":"2.0","id":1,"method":"initialize",
  "params":{"protocolVersion":"2025-03-26","capabilities":{},
            "clientInfo":{"name":"my-agent","version":"1.0.0"}}
}'
// 2) tools/list
curl -sX POST https://dynamicfeed.ai/mcp -H 'content-type: application/json' -d '{
  "jsonrpc":"2.0","id":2,"method":"tools/list","params":{}
}'

Receipt verification via REST — paste or URL input (this is exactly what /verify does when you paste JSON or fetch a URL):

curl -sX POST https://dynamicfeed.ai/v1/batch \
  -H 'content-type: application/json' \
  -d '{"calls":[{"tool":"space_weather","args":{}}]}' > receipt.json

pip install dynamicfeed-verify
dynamicfeed-verify - < receipt.json   # re-canonicalizes + checks Ed25519 against the published key

# or paste receipt.json's contents directly into the textarea at https://dynamicfeed.ai/verify —
# it never leaves the page; verification runs client-side

Source inspection panel (what /verify's "Evidence inspector" shows once a receipt is loaded):

// every verified result carries a provenance + freshness envelope; the inspector renders
// exactly these fields — nothing else is inferred:
{
  "source": "NOAA Space Weather Prediction Center",
  "observed_at": "2026-07-18T02:14:00Z",
  "freshness": "fresh",
  "integrity": "valid",
  "key_id": "df-ed25519-6ca0de29113b",
  "known_limitations": ["forecast confidence not independently re-derived"]
}

JavaScript / Node / Python verifiers and the Trust Receipt v1 conformance verifier are documented in full, with copy-paste code, on /verify itself under "Verify from your own code" — this page does not duplicate them.

5Documentation and further reading