Forecastr

Get verifiable AI forecasts with RFC 3161 timestamps and on-chain proof registry (BYOM or managed inference)

Actions4

Submit Output

AI-generated

Summary

Submit previously generated predicted values from your own forecasting model to Forecastr's API for verifiable proof with RFC 3161 timestamps and optional on-chain registry.

Inputs

  • Asset (required) — Identifier for the asset whose forecast output you are submitting (e.g., yf_brent, aave, yf_gold).
  • Horizon (days) (required) — Forecast horizon length in days, between 1 and 256 (7 days max for free tier).
  • Point Forecast (required) — Comma-separated list of the predicted values to submit.
  • Model ID — Identifier for your forecasting model (default: 'my-model-v1').
  • Context Hash (required) — SHA-256 hash in hexadecimal (64 characters) representing the input data used by your model for generating the forecast; necessary for proof integrity.

Output shape

a list of JSON objects, each containing the API response for a submitted forecast output

Each output corresponds to one input item processed. Errors are returned in the output JSON if 'Continue On Fail' is enabled; otherwise, the node execution will error.

Examples

Example 1: Submit output for a 7-day forecast on yf_brent

Set 'Asset' to 'yf_brent', 'Horizon (days)' to 7, provide a comma-separated 'Point Forecast' string, specify 'Model ID' if desired, and include the 'Context Hash'.

Links

Discussion