Skip to content
Docs

Norynta public docs

Norynta Institutional Hedge And Data Pilots

Capital-efficient path from early market demand to institutional hedge, insurance, reinsurance, and data products.

Institutional Hedge and Data Pilots

Purpose

Define a capital-efficient path from early market demand to institutional hedge, insurance, reinsurance, and data products.

Near-term wedge

Do not sell broad institutional liquidity before it exists. Sell narrow pilots:

  • one event-risk category
  • one named resolution source
  • one market structure
  • one maker/liquidity plan
  • one data export or monitoring dashboard

This makes diligence easier and avoids overpromising depth.

Pilot categories

Good first institutional categories:

  • commodity, weather, and catastrophe risk
  • macro releases and rate decisions
  • public-company event risk
  • supply-chain and geopolitical disruption
  • crypto treasury and protocol-risk events

Each pilot should name:

  • target user
  • hedge use case
  • settlement source
  • market lifecycle
  • expected liquidity model
  • compliance boundary
  • data fields delivered

Data products to sell first

Start with privacy-safe products:

  • market and request demand rankings
  • event metadata and lifecycle history
  • orderbook depth and spread summaries
  • trade and volume aggregates
  • resolution outcomes and evidence packages
  • derived liquidity and volatility signals

Avoid selling raw identity, KYC, contact, device, or precise location data.

Commercial path

  1. Free public docs and sample data.
  2. Starter API tier with delayed/limited freshness.
  3. Pro API tier for active developers, makers, and researchers.
  4. Enterprise exports for funds, risk teams, and insurers.
  5. Bespoke hedge pilots with maker coordination.

Required proof before scaling

  • repeated demand-backed market requests
  • at least one first-liquidity partner per category
  • reliable settlement evidence
  • data dictionary and license terms
  • market-quality history
  • security and control docs
  • incident and dispute process

Operator commands

npm run founder:revenue-loop
npm run market:requests:triage
npm run opportunity:plan
npm run bot:starter:dry-run

Use founder:revenue-loop first. It combines demand-backed requests, first-maker signals, social headline drafts, and data-sales next steps before you decide whether to create markets, recruit makers, publish content, or sell data access.

Related docs

  • docs/public/DATA_LICENSE_AND_COMMERCIALIZATION.md
  • docs/public/DATA_API.md
  • docs/public/LIQUIDITY_PARTNERS.md
  • docs/public/MARKET_LISTING_STANDARDS.md
  • docs/RISK_MARKET_TAXONOMY.md