The evidence underwriters need to price AI risk.
With little loss history, AI risk gets priced on governance and evidence. Dynamic Feed gives underwriters a third-party, tamper-evident signal on the provenance and freshness of any Dynamic Feed data an applicant uses — an input you can require and re-check, not take on trust. Dynamic Feed attests to its own data; it can't see the applicant's systems.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# REST (free key)
curl -H "X-API-Key: $KEY" "https://dynamicfeed.ai"
# MCP (keyless) — point any client at https://dynamicfeed.ai/mcp, then call:
Sample response
{ "value": "...", "provenance": { "source": "...", "license": "...",
"measured_at": "...Z", "age_seconds": 42 },
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-4cb32e72f333" } }Why live data
AI cover is being written with thin actuarial history, so underwriters lean on governance and evidence to price and to set conditions. A recurring gap is the input data. Dynamic Feed makes its own data verifiable: every datapoint carries a provenance envelope — source, licence, exact time, age — and an Ed25519 signature, so an applicant can demonstrate, and you can independently re-check, the provenance and freshness of the Dynamic Feed data they use. It does not record or verify what an applicant's system did, or that the data is true. Dynamic Feed supplies the evidence; it does not price risk, and how you draft any requirement or policy condition is your decision and your counsel's. Not insurance or legal advice.
Use it for
- A verifiable data-provenance & freshness signal you can add to your own AI evaluation of an applicant
- A requirement you may set: the insured uses signed, current Dynamic Feed data where applicable — verifiable by you
- Evidence that an applicant uses verifiable, current third-party data — one input you may weigh
- A third-party input that doesn't depend on the applicant's word
FAQ
How does this fit into how I assess AI risk?
It closes part of the black box. Instead of trusting that an applicant used good, current data, you get a third-party, tamper-evident record of the provenance and freshness of the Dynamic Feed data they use — which you can require and re-check. Dynamic Feed makes its own data verifiable; it doesn't record what the applicant's system did or assert the data is true.
Can I make it a requirement?
You can require that the insured use signed, provenance-stamped Dynamic Feed data where applicable and retain the records, giving you something verifiable to check. How you draft that requirement or any policy condition is your decision and your counsel's — Dynamic Feed provides evidence, not legal or insurance advice.
Does Dynamic Feed underwrite or price anything?
No. Dynamic Feed is a data-evidence layer only. It supplies verifiable inputs; all underwriting, pricing and coverage decisions — and any advice — stay with you.