Norynta public docs
Norynta Data License And Commercialization
Commercialization, licensing, and permitted-use guidance for Norynta data products.
Norynta Data License and Commercialization Notes
Purpose
This document outlines a practical commercialization and usage framework for Norynta data products.
Canonical posture
Norynta's canonical commercialization posture is to sell privacy-safe market intelligence products and derived analytics, not raw personal-data brokerage.
Recommended commercialization model
The recommended approach is to commercialize:
- market-level analytics
- public/on-chain activity enriched with Norynta metadata
- aggregated liquidity, spread, activity, and ranking signals
- historical exports and recurring API access
The recommended approach is not to commercialize raw personal data. Norynta should not silently collect device fingerprints or raw location profiles for resale.
Permitted use examples
- research and analytics
- market making and quantitative modeling
- dashboards and monitoring
- editorial and intelligence products
- agent and bot decision support
Prohibited use examples
- re-identifying natural persons
- combining Norynta data with external private datasets to deanonymize users
- discriminatory profiling
- selling onward access in violation of Norynta license terms
- using non-public Norynta data without authorization
Restricted data categories
These categories should not be part of the sellable default data surface unless separately reviewed by counsel and platform policy owners:
- emails
- phone numbers
- IP addresses
- device fingerprints
- private KYC or AML records
- any identity-linked account recovery or support data
- precise location profiles
Product design guidelines
- prefer aggregated outputs over user-level outputs
- apply minimum cohort thresholds where applicable
- separate sellable datasets from internal raw data pipelines
- keep explicit audit logs for exports and enterprise deliveries
- document freshness, schema stability, and allowed usage clearly
- require policy/compliance review before introducing new sellable field classes
Operational governance requirements
- classify fields into
public,derived, andrestrictedcategories - restrict default commercial products to
public+derived - maintain export/delivery audit trails (customer, dataset, purpose, volume)
- enforce retention schedules by dataset class
- require explicit review for any release with re-identification risk
Go-to-market notes
The highest-probability first offering is usually:
- market intelligence API
- premium signal feed
- historical trade export
- enterprise delivery / bulk exports
Recommended packaging ladder
Canonical pricing and boundaries:
| Plan | Price | Commercial boundary |
|---|---|---|
| Public | Free | 15-minute delay, 60 reads/minute, one evaluation key |
| Approved Maker | Free | Real-time execution-critical access; quoting only, no resale |
| Builder Pro | $149/month | Real-time signals, 30-day history, internal commercial use |
| Commercial Data | $999/month | Bulk delivery, one-year history, schema guarantees |
| Enterprise / Event-Risk Pilot | $2.5k-$7.5k/month plus setup | Custom monitoring, evidence delivery, retention, and negotiated rights |
Historical, derived, bulk, and redistribution-capable products are not part of the default self-serve entitlement. Approved makers receive the real-time data needed to quote approved markets without turning that access into a data-resale license.
Builder Pro and Commercial Data can be purchased by a signed-in user through hosted Checkout when billing is available. Access begins only after Norynta verifies a signed subscription event. If checkout is not yet available, the plan action opens the commercial access request instead. Cancellation, payment failure, or subscription expiry returns API keys to the delayed self-serve boundary; it does not erase accrued payment obligations or expand license rights.
Starter
- ranked market intelligence only
- suitable for dashboards, research, and evaluation
- lower request budgets and optional delayed freshness
- clean monetization lever via enforced delayed data access
Good first sellable fields:
- market slug, title, category, lifecycle status
- public volume, liquidity, spread, and depth bands
- request demand count and public priority tier
- source confidence and resolution-policy class
- delayed price history and normalized public trade aggregates
Pro
- ranked market intelligence
- derived signal feed (
/api/data/signals) - normalized trade export
- normalized public wallet position export
- designed for active agents, quants, and market makers
Enterprise
- everything in Pro
- premium historical market-intelligence history
- bulk exports, recurring delivery, and custom schemas
- partner SLA / support expectations
First Sellable Offers
Start with narrow products that require little support and no bespoke data engineering.
| Offer | Buyer | Package | Notes |
|---|---|---|---|
| Delayed market-intelligence API | researchers, dashboards, media | Starter | easiest paid pilot; sell normalized ranking and quality signals, not raw user data |
| Real-time signal feed | market makers, bots, active traders | Pro | monetize freshness, schema stability, and fewer downstream calculations |
| Historical market-quality export | funds, analysts, data desks | Enterprise | charge for recurring delivery, retention, and support |
| Liquidity and hedge watchlist | insurers, reinsurers, treasury/risk teams | Enterprise | focus on event-risk monitoring before promising large executable hedge capacity |
Before pitching or delivering, confirm the buyer only needs public or
derived fields, assign an API-key tier/freshness delay, and record customer,
dataset, purpose, and delivery window in the data delivery audit trail.
Why the signal layer matters
The strongest monetization story is usually not raw public data alone. It is the combination of:
- public/on-chain facts,
- Norynta normalization,
- Norynta ranking logic,
- Norynta-derived signals that reduce downstream analysis work.
That is what turns a dataset into an intelligence product.
Operational monetization note
Where appropriate, commercial API keys can enforce freshness delays directly in
the runtime using per-key delaySeconds. This gives Norynta a concrete way
to sell delayed Starter access while preserving real-time or near-real-time
value for Pro and Enterprise customers.
First revenue path
The leanest path is to sell data that already improves the core marketplace:
- publish a free delayed market-intelligence sample
- offer Pro API keys to bot builders and market makers who need fresher depth
- sell Enterprise bulk exports only after export audit logs and field classifications are enforced
- keep restricted user, KYC, support, and security telemetry out of commercial exports unless a separate legal review approves a specific product
This aligns incentives: the more Norynta improves market quality, source confidence, request demand, and liquidity visibility, the more valuable the data product becomes.
Related docs
docs/public/DATA_API.mddocs/public/BUILD_ON_NORYNTA.mddocs/BLOCKCHAIN_COMPLIANCE_CONTROLS.mddocs/ARCHITECTURE.md