FAQ
Frequently asked questions
The research platform, the public sample and the separate requirements for organization data.
What can I try without an account?
The public sample terminal connects eleven workspace destinations plus watchlists, using 48 fictional events and 112 contracts at a fixed scenario clock. Explore charts, screening, comparison, calendar, local alerts, retained-input research and a bounded portfolio demonstration. Saved sample data stays in this browser. It does not grant real organization data, source licenses, trading or external notification delivery.
What is Predict Here?
Predict Here is a read-only event-risk intelligence and research platform for prediction markets. It connects contract meaning, market-quality signals, visible-liquidity analysis and provenance so a research conclusion can be traced to its inputs.
Who is this for?
Hedge funds, market makers and prop desks, risk and research teams, data and quant teams, and brokers/FCMs — professional research, risk, and trading workflows.
Does Predict Here operate a prediction market itself?
No. Predict Here Institutional is a read-only data and intelligence product. It does not list markets, custody client funds, take the other side of a trade, or execute orders. The published release profile marks Polymarket US and Kalshi production collection as disabled. A code-level integration or separately described workspace does not by itself confirm current production activation or organization rights.
Which venues are currently available?
The published release profile marks Polymarket US and Kalshi production collection as disabled. Polymarket is marked enabled in the maintained profile, but that is not a runtime activation or tenant-entitlement check. Any delivery depends on current source rollout and organization-specific rights. Cross-source comparison additionally requires two entitled sources, eligible observations, and a current human-reviewed mapping. See the docs for details.
What does "verified contract semantics" mean?
Two venues can describe what sounds like the same event with contracts that resolve differently. Every mapping we publish carries an explicit semantic-equivalence state — VERIFIED, PARTIAL, NOT_EQUIVALENT, or UNREVIEWED — derived from the underlying relationship's review status, never assumed equivalent by default. See the methodology for the full definitions and how the two vocabularies relate.
How does price-at-size analysis work?
Top-of-book displays one visible level; it does not show how much depth is available beyond that point. Where the source and organization have the required rights, a direction-specific price-at-size calculation can walk a timestamped visible-book snapshot and report the amount covered and any shortfall. It is a research estimate for that snapshot—not an order, firm quote, or promise of a later fill.
Is the data real-time?
No feed on this site is labeled real-time. Published methodology describes canonical Monitor observations as delayed polling data, not a continuous stream. Derived figures carry their applicable provenance and version identifiers. The published release profile marks Polymarket US and Kalshi production collection as disabled; a separately described read-only workspace remains subject to rollout and source rights. See the methodology and trust and security for current Monitor details.
How are source-data rights handled?
Each venue's data carries its own entitlement — a licensing/legal-rights question, kept independent of any product tier or plan. A feature being available in the product does not by itself authorize delivery of a given source's data; access is checked server-side against what's actually entitled, every request.
How do I get access?
Predict Here Explore workspace signup is self-service with a verified email. Real event data requires current organization source rights; signup does not grant those rights. An Institutional Evaluation is a manually approved trial with the full execution ladder and authenticated data routes, subject to source rights: request access and tell us about your workflow. An ongoing Institutional relationship is commercial, by agreement.
How do I get API access?
A Developer Sandbox key is self-service and returns synthetic fixtures. Canonical production data routes currently use authenticated organization sessions; production API-key transport for those routes is not implemented. Any source delivery requires separate current organization and source rights plus production controls, regardless of plan. See the docs for the data model, then request access to discuss an integration.
How do I get in touch?
See contact for data licensing, support, security reports, and general inquiries.
WORKING SAMPLE · SYNTHETIC DATA
Follow the research from observation to evidence.
Open Monitor, screen the universe, inspect contract terms, compare eligible outcomes and retain a research brief. Watchlists, saved views and adjustable workspaces keep the same event in context.
No account required for the sample. Its fictional records, local alerts and research stay separate from organization data. Portfolio scenarios are a bounded private beta; organization access still requires sign-in, plan and source permissions.
Still have a question?
Tell us about your event set and workflow and we'll answer it directly.