Built to be used by machines.
If you're an agent — or building one — this is your entry point. Dynamic Feed is keyless over MCP, exposes OpenAPI + JSON schemas and a machine-readable capability manifest, publishes a public key for identity, and puts an Ed25519 signature on every datapoint. So you can discover, evaluate, trust, use, and verify it without a human in the loop.
Machines are already tapping in.
Aggregate traffic Dynamic Feed has served to agents and machines — live from /v1/agent-stats. Counts only: no IPs, no identities.
Everything an agent needs, at a fixed path.
No scraping, no sign-up to start. Point your client at these and you're in:
https://dynamicfeed.ai/mcpAll 87 read-only tools over the Model Context Protocol. No API key.https://dynamicfeed.ai/openapi.jsonThe full machine-readable API contract.https://dynamicfeed.ai/.well-known/ai-catalog.jsonAgentic Resource Discovery: what we offer + how to verify us.https://dynamicfeed.ai/server-card.jsonThe MCP server card — tools, transports, identity.https://dynamicfeed.ai/.well-known/keysThe Ed25519 key every response is signed with.https://dynamicfeed.ai/llms.txt · /llms-full.txtPlain-text, AI-readable description of every tool.POST https://dynamicfeed.ai/v1/batchUp to 20 tool calls in one keyless request.Discover → evaluate → trust → use → verify.
Each step of how an agent transacts with a service has a fixed, machine-readable answer here — no persuasion required.
Find the tools
List from the keyless MCP endpoint, or find us in the MCP registries. 87 tools, 19 verticals.
Read the contract
OpenAPI, JSON schemas (/schemas/*), and the capability manifest tell you exactly what each tool does.
Check identity + verify
Our identity is a public key. Every response is Ed25519-signed — check it against /.well-known/keys before you act.
Call, keyless
Read-only tools you can invoke directly — no key to start. The call is the action endpoint; nothing to scrape.
Keep a signed record
Every datapoint is a signed, timestamped, Bitcoin-anchorable receipt of what you acted on — re-checkable by any party, later.
Cite + verify
Cite a Dynamic Feed value and any other agent can verify the citation against our public key. Trust that travels.
An agent acts on data — so it has to verify it.
A human reads a dashboard and trusts it. An agent about to spend, book, or move a robot on a number can't afford to — it needs to know where the number came from, how fresh it is, and that it hasn't been altered. That's the difference between a human‑readable site and a machine‑usable one: not a prettier page, but data a machine can check instead of taking on faith. Every datapoint here ships with its source, licence, exact timestamp and a signature — so "trust" is something you compute, not something you grant.
A valid signature shows Dynamic Feed served this exact value at the stated time and it hasn't been altered since — tamper‑evident authenticity and integrity, verifiable against /.well-known/keys. It does not assert the value is objectively true or complete; many readings are model forecasts. Provenance, not omniscience. Tools are read‑only — nothing can be mutated through Dynamic Feed.
Point your client at the feed.
Keyless MCP at https://dynamicfeed.ai/mcp, or a free key for higher REST limits.