> For the complete documentation index, see [llms.txt](https://docs.hilomarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hilomarket.com/legal-and-regulatory-positioning.md).
# Legal and Regulatory Positioning
Legal and regulatory uncertainty has been one of the primary constraints on the growth of traditional prediction markets. Because most platforms rely on wagering, odds, and financial exposure tied to event outcomes, they are frequently classified as gambling or fall into ambiguous regulatory categories across jurisdictions.
Hilo is intentionally designed to avoid these classifications.
#### Designed Without Gambling Mechanics
Hilo does not involve wagering, odds, or financial exposure tied to specific outcomes. Users do not risk capital, do not trade contracts, and do not receive payouts based on event resolution. Participation is based on contributing predictions and information rather than placing bets.
By removing these mechanics at the system level, Hilo separates itself from products that regulators typically associate with gambling or betting activity.
#### No Financial Exposure or Counterparty Risk
Because users do not trade against one another or against the platform, there is no counterparty risk, no pooled funds, and no settlement of financial outcomes based on real-world events. This significantly reduces regulatory complexity and operational risk compared to liquidity-based prediction markets.
The platform’s outputs are data and analytics rather than financial instruments.
#### Jurisdiction-Agnostic Design
Hilo is built to operate across jurisdictions without relying on region-specific gambling or financial licenses. By avoiding monetary betting mechanics, the platform is not dependent on regulatory carve-outs, exemptions, or experimental approvals that have historically limited prediction markets to narrow geographies.
This design enables broader global participation and reduces the risk of sudden shutdowns, geo-blocking, or legal reversals.
#### Institutional and Partner Compatibility
Regulatory ambiguity has discouraged institutions, researchers, and enterprises from engaging with traditional prediction markets. Hilo's non-gambling, data-first structure is designed to be compatible with institutional standards around compliance, risk management, and ethical use.
This positioning supports partnerships with organizations that require structured data and forecasting insights without exposure to gambling-related risk.
#### Design Intent and Ongoing Review
Hilo's approach reflects a clear design intent to function as prediction and data infrastructure, not as a betting platform. While regulatory interpretation can vary by jurisdiction and evolve over time, the system is built from first principles to minimize risk and adapt to changing legal environments.
Legal considerations are treated as a core design constraint rather than an afterthought.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hilomarket.com/legal-and-regulatory-positioning.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.