Predict Here
Prediction-market research terminal
A connected research workflow from market observation to rules, comparison, evidence and portfolio context.
SAMPLE WORKSPACE — synthetic data. The public terminal contains 48 fictional events and 112 contracts at a fixed scenario clock. It grants no organization, venue, wallet or trading access.
Monitor
Observe selected events, charts and source age.
Open workflow →Inspect
Open terms, rules, depth and source evidence.
Open workflow →Compare
Review eligibility and contract differences.
Open workflow →Retain evidence
Save inputs, review changes and export a sample briefing.
Open workflow →
Monitor
Linked charts, watchlists, saved column views and three adjustable workspaces.
Open this workflow →Screener
Filter events or contracts by category, probability, movement, quality, dates and reviewed comparability.
Open this workflow →Events
Read the proposition, window, rules, visible depth and source evidence together.
Open this workflow →Compare
Inspect two to four contracts. Numerical gaps require current reviewed equivalent terms and independent books.
Open this workflow →Calendar
Separate catalyst, observation, close, expected resolution and settlement dates; unknown precision stays unknown.
Open this workflow →Alerts
Create browser-local rules, simulate a deterministic change and acknowledge its evidence. No external delivery.
Open this workflow →Research
Save conclusions with retained inputs and version references. Export a clearly labeled sample brief.
Open this workflow →Portfolio
Private beta: fixed-USD long sample positions, known payoff and bounded manual shocks. Partial scope is explicit.
Open this workflow →Watchlists & saved views
Keep event membership separate from saved table filters, columns and sorting.
Open this workflow →Data & API
Inspect the synthetic provider, field definitions, access states and the matching sample response.
Open this workflow →Help
Open the task guide, replay the tour, and find shortcuts without blocking the workspace.
Open this workflow →Settings
Change browser-local theme, density and timezone preferences; organization access stays separately gated.
Open this workflow →The workflow, inside the application
Actual application captures from an isolated synthetic sample. Open each workspace to work through the same tools.
Read the event and its rules together
Observed history, contract terms, review state and visible depth share one workbench.
Actual application · synthetic sample · fixed scenario clock
Compare meaning before comparing numbers
The descriptive matrix separates proposition, timing, payout and resolution. Numerical results require current reviewed eligibility.
Actual application · synthetic sample · fixed scenario clock
Retain the inputs behind the conclusion
Save a local sample record with evidence, observation and term versions. Reopen it or export a labeled briefing.
Actual application · synthetic sample · fixed scenario clock
Capability and availability
- Working sample
- 11 workspace destinations plus watchlists, saved views, local research and alerts, liquidity analysis and the public synthetic API. No live market data.
- Organization workspace
- Access is scoped to your organization, plan and permitted sources. Ask for an evaluation to confirm the workflows and datasets available to your team.
- Conditional source availability
- Collection support does not establish rights or activation. Production availability depends on approved organization, plan, venue and delivery permissions.
- Not implemented in this terminal release
- New organization research persistence, authorized artifact exports and external notification delivery. Portfolio demonstrations remain bounded sample scenarios. No execution or custody.
Access and analytical limits
Organization data remains behind the existing sign-in, plan, tenant and source permission checks. International, US and Kalshi source rights are independent. Sample availability is not evidence of a production license.
Current composite inputs cannot exceed the shared 10-minute quote age. Missing, stale, one-sided or unsupported inputs produce explicit unavailability. Visible depth does not guarantee execution; economic payoff offsets do not establish operational netting.