by Fluxdyne
Live external data tells an automated system what is happening. A Decision Receipt preserves what it relied on, where it came from, how fresh it was, what was verified and what remained uncertain.
Map © OpenStreetMap · OpenFreeMap · NASA GIBS
Why Dynamic Feed
Important decisions need a record of what information was available, where it came from and when. Dynamic Feed keeps that context attached.
Current reports from named sources, with observed time and freshness state attached.
Know where the response came from and what was checked.
Preserve a signed record and its verification material on supported receipt paths.
Reconstruct the evidence presented when replay artifacts exist.
Project Atlas
Explore current observations with their source, freshness and integrity state still attached. The globe and stream use the same live Dynamic Feed response.
Live observations will appear here when the first response arrives.
Selected observation
Select an item to inspect the evidence trail behind the live observation.
A live Atlas observation is not automatically a receipt. A valid response signature establishes integrity and attribution, not objective truth.
Decision Receipts Preview
Its sources, freshness, checks, integrity state, and the evidence available when it acted. Decision Receipts are in development; the live demonstration is real and verifiable today.
Now live
/verify opens a real receipt and checks its signature in your browser, no account needed. /partners is a bounded 30-day pilot for one consequential machine decision your organization needs to defend later.
How it works
Dynamic Feed keeps current information connected to named sources and its verification state. On supported receipt paths, it preserves a signed record for later inspection.
Decision example
Developer entry point
Connect keyless over MCP, use the REST batch endpoint directly, or use the official MCP client SDK. Each example matches the current public surface.
{
"mcpServers": {
"dynamic-feed": {
"url": "https://dynamicfeed.ai/mcp"
}
}
}curl -s https://dynamicfeed.ai/v1/batch \
-H 'content-type: application/json' \
-d '{"calls":[{"tool":"current_weather","args":{"city":"Sydney"}}]}'import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const client = new Client({ name: "atlas-client", version: "1.0.0" });
await client.connect(new StreamableHTTPClientTransport(
new URL("https://dynamicfeed.ai/mcp")
));Built for consequential decisions
Dynamic Feed is designed for organizations making automated, high-value, real-time decisions from live external data.
Trust through implementation
Publisher, URL, licence and cadence remain inspectable.
Published public keys support independent integrity checks.
Supported evidence objects retain their verification material.
Integrity, lifecycle and proof states remain separate.
Historical reconstruction remains target architecture unless an artifact exists.
A valid signature establishes signed-byte integrity and attribution. It does not establish objective truth about an upstream observation.
Read the trust posture ↗