dynamicfeed.ai publishes an Agentic Resource Discovery manifest at /.well-known/ai-catalog.json, declaring what an AI agent can call on this domain. Everything below is read from that file. First seen by our crawler on 31 August 2026.
| Declared resource | Type |
|---|---|
| Dynamic Feed: keyless live-data MCP serveranswers in 340msv1.0 Keyless Model Context Protocol server for live, verifiable real-world data. Every datapoint is returned in a provenance envelope (source, licence, exact measurement timestamp, age) and Ed25519-signed; records can be independently time-stamped by an independ... endpoint: https://dynamicfeed.ai/.well-known/mcp/server-card.jsonidentifier: urn:ai:dynamicfeed.ai:mcp:dynamic-feedpublished to be found for: What changed in the world since my training cutoff? · Does this software package and version have a known CVE? · What is the live weather, forecast, or air quality at a location? · Which CVEs are being actively exploited right now? live-data-retrieval verifiable-provenance ed25519-signing rfc3161-timestamping exploited-vulnerability-inte weather-and-hazards ai-model-pricing geospatial-positioning trust identity: https://dynamicfeed.ai | application/mcp-server-card+json |
| Dynamic Feed REST API (OpenAPI)answers in 386msv1.0 REST interface to the same live, signed data layer. Batch-fetch many datapoints in one call via POST /v1/batch, or call per-feed endpoints. Includes a signed go/caution/no-go situational-awareness verdict for robots and agents at a location. Optional X-API-... endpoint: https://dynamicfeed.ai/openapi.jsonidentifier: urn:ai:dynamicfeed.ai:api:restpublished to be found for: Batch-fetch multiple live signed datapoints in one call · Get a signed go/caution/no-go awareness verdict for a robot at a locat live-data-retrieval verifiable-provenance batch-queries robot-situational-awareness trust identity: https://dynamicfeed.ai | application/vnd.oai.openapi+json |
| Dynamic Feed Witness: signed receipts for machine-to-machine transactionsanswers in 381msv1.0 A neutral third-party WITNESS for agent-to-agent transactions. POST /v1/witness records a transaction (or just its sha256) as an Ed25519-signed, transparency-logged receipt (txn-receipt/v1) whose hash is time-stamped by an independent RFC 3161 authority and... endpoint: https://dynamicfeed.ai/openapi.jsonidentifier: urn:ai:dynamicfeed.ai:api:witnesspublished to be found for: Witness an agent-to-agent transaction and return a signed receipt · Prove which AI model actually answered a request (ProofOfModel inferen · Get a black-box receipt for a robot decision, or a notarized un-retuna · Get a tamper-evident, RFC 3161 time-stamped audit trail for agent acti transaction-receipts machine-to-machine-audit-tra ed25519-signing rfc3161-timestamping agent-identity-attestation tamper-evident-record trust identity: https://dynamicfeed.ai | application/vnd.oai.openapi+json |
https://dynamicfeed.ai/.well-known/ai-catalog.json, this publisher's own file. Identifiers are reproduced exactly as published.
Note: this is the pre-v0.91 path. The specification renamed the manifest to /.well-known/ard.json, and most of the ecosystem still serves the older name.
Of the resources listed, 3 have been probed for reachability.
"Answers" and "no response" describe only whether an endpoint replied when last probed:
services go down and come back, and an entry is demoted rather than removed. None of this
is a trust, quality or safety rating.
https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp.
If this is your domain, the free console shows what a registry
sees when it reads your manifest.