Status, privacy & help
Know what is available, what is planned and how to resolve common problems.
Available today
The observatory, source integrations, custom context imports, local runtime and OpenAI scenario workflow are implemented. Live access to individual providers depends on availability, credentials and quotas.
Calibrated forecasting, wallet attribution, durable server-side ingestion and historical replay are not implemented. The separate proprietary service is a protocol scaffold.
Omens AI and $OMEN
The intended model is monthly Omens AI membership paid in $OMEN. Checkout is disabled. Pricing, payment network, token contract, payment verification and entitlements are not configured for launch.
You can use OpenAI with your own key today without an Omens membership. Do not treat a roadmap item as an available paid service.
What stays in your browser?
Optional provider keys, the OpenAI key and service tokens stay in tab memory and disappear on reload. Context records and preferences may persist locally in your browser. Context has remove and clear controls.
Requests send the data needed to the chosen provider, sometimes through fixed Omens server routes. An AI scenario sends the evidence snapshot you reviewed. A custom service receives requests directly from your browser.
Common questions
The map is slow or blank.
Enable Low power to switch to 2D. The 3D map needs WebGL, and all maps need access to their tile providers.
A feed is unavailable.
Check its source status, retrieval time and provider access. Retry with the available refresh control. A missing feed does not mean there are no events.
My keys disappeared.
This is expected after reload. Re-enter them through Connect sources or Omens AI.
Model access passed, but generation failed.
Check the error shown in Omens AI. Model access alone does not confirm compatible structured output, quota or billing. Review your key, model and fresh evidence before sending again.
My custom feed will not load.
Use HTTPS, check the record schema and ensure the endpoint permits browser CORS for your app origin.
The local service says the engine is unavailable.
That is the expected scaffold behavior. Select the OpenAI option to use the implemented bring-your-own-key workflow.