Publish and Share a Forecast
A finished forecast lives in your session, visible only to you. Publishing gives it a permanent public page at futuresearch.ai/app/p/a/your-slug that anyone can open without an account, including search engines and the crawlers behind AI assistants.
Publishing is done in the web app. There is no publish method in the Python SDK, the public API, or the MCP server, so if you ran the forecast from code, open the session in the app to publish the result.
How to publish
- Open the finished forecast in the app. The control only appears once the task has completed.
- Click the globe icon in the results toolbar. The popover is headed Publish results.
- Type a slug. This becomes the URL, so pick something readable:
anthropic-ipo-pricing-datebeatsforecast-run-3. - Publish, then copy the URL from the field that replaces the input.
Slugs are 3 to 80 characters, lowercase letters, digits and hyphens, no leading or trailing hyphen. They are globally unique, so a common word may already be taken.
Unpublishing is one click in the same popover, and it frees the slug for reuse.
What the page shows
A published forecast is the full result, not a screenshot of it. Visitors get the probability or the percentile distribution, the complete rationale, and every source the research agents read, so they can check the reasoning rather than take the number on trust.
The page also carries a generated preview card sized for social embeds, which renders the probability gauge for binary forecasts and the p10 to p90 range for numeric and date ones, plus a canonical URL and article structured data.
What stays private
Publishing exposes the result and its reasoning. It does not expose your input data. The published bundle carries only the parameters needed to render the result, such as forecast_type, output_field and units, and internal fields including trace mappings and analysis metadata are stripped from the artifact and all its children.
If you published a forecast whose question text contains something confidential, unpublish it. The question is part of the page.
Published forecasts feed the world model
This is the part that is easy to miss. Publishing a forecast adds it to FutureSearch's world model, the shared set of drivers reconciled across every forecast the system has made. A published forecast can then help calibrate other people's answers on related questions, and theirs help calibrate yours.
The effect is visible on the page. Published forecasts show what the answer was weighed against, phrased as a note like "weighed against 2 related questions here and 1 public forecast", which expands to show the siblings and the public forecasts consulted. Your own past private forecasts are never shown to visitors, even where they informed the result.
Good slugs
The slug is the URL and, in practice, the headline. A few that work, taken from our published forecasts:
anthropic-ipo-pricing-datespacex-positive-free-cash-flow-by-2027gemini-3-5-pro-context-window-size
Each names the subject and the resolution point, which is what someone searching the question would type. Avoid dates of publication, run numbers, and internal project names.
Built with FutureSearch. See Published forecasts for a curated set, or the forecast documentation for the operation itself. Related guides: Write Resolution Criteria That Hold Up, Turn Claude into an Accurate Forecaster.