Concept preview — non-production.
This console is a public, non-authenticated demo surface for time-and-temperature style queries and narrative
fixtures. It is not a production Textmetrics, Trusaic, or settlement report path; do not use it for regulated
data or payout evidence.
Run requests below; JSON responses appear in the panel at the bottom.
Using This Console for Smoke and Integration Checks
Ping — Confirms the TimeFox route is reachable (routing, TLS, process health). Use first in any runbook.
About — Returns service metadata; pair with Ping to prove the public compatibility lane end-to-end.
Stub time-temp — Deterministic, narrative-friendly JSON without calling external weather APIs. Best for CI, demos, and proving your client parses the contract.
Live time-temp — Fetches real conditions via Open-Meteo. Requires mode=live, outbound network from the edge runtime, and valid latitude / longitude (decimal degrees).
Internal process testing — Chain: Ping → About → stub time-temp with your usual tz and style. Only then try live with coordinates you expect (e.g. office location) to validate weather plumbing.
Protected report workflow — Not shown here by default. Open this console with ?mode=protected&origin=…&flow_id=… (after a valid origin handoff) to exercise Temporal Tech report APIs and return URLs.
Quick Links
One-click samples. Each issues a GET and fills the response panel. Use them to compare with your own Custom Time-Temp parameters.
Builds GET /flicker-fox/time-temp with query parameters. The API validates mode, style, and tz; invalid combinations return a JSON error envelope with a stable code.
