Skip to content
Docs

Norynta public docs

Norynta Data API

Market-intelligence data API documentation for partners, research teams, analytics platforms, and agents.

Norynta Data API

Purpose

This page describes Norynta's market-intelligence data product for partners, research teams, funds, analytics platforms, and agent developers.

Operational collection pipeline

  • GET /api/cron/run-pipeline now includes market-intelligence collection by default after auto-create / matcher / auto-resolve / house-mm phases.
  • Collection controls are exposed via query params:
    • collectMarketIntelligence=1|0
    • collectMarketIntelligenceDryRun=1
    • collectMarketIntelligenceEventLimit
    • collectMarketIntelligenceLookbackHours
    • collectMarketIntelligenceOutcomeLimit
  • Pipeline response now surfaces marketIntelligenceCollection so automation can monitor collection health without failing core market orchestration.
  • Collection runs are durably audited in data_product_collection_runs with job/status/schema version, timings, request scope, and result summary metadata.

Audience

  • quant funds and liquidity operators
  • analytics and dashboard partners
  • research teams and media organizations
  • developers building bots, agents, and alerting systems

What this product is

Norynta Data API is a privacy-safe market intelligence surface built from:

  • public market metadata
  • public/on-chain trading activity
  • Norynta-generated liquidity, spread, and ranking analytics
  • aggregated and normalized event intelligence

It is designed to provide actionable market analytics, not raw personal-data brokerage.

Core datasets

1. Market intelligence

Endpoint: GET /api/data/market-intelligence

Use it to retrieve ranked, derived analytics for active or historical markets.

Supported query parameters:

  • limit
  • lookbackHours
  • outcomeLimit
  • includeResolved
  • competitive
  • minVolumeUsd
  • domain (all, climate_weather, macro_finance, event_risk)
  • eventRisk=1 alias for domain=event_risk

Example:

curl "https://your-domain.example/api/data/market-intelligence?limit=25&lookbackHours=72"

Strategic event-risk example:

curl "https://your-domain.example/api/data/market-intelligence?domain=event_risk&competitive=0"

Representative response fields:

  • slug
  • eventPubkey
  • title
  • category
  • endTimestamp
  • resolved
  • volumeUsd
  • openOrders
  • spreadCents
  • spreadSamples
  • competitive
  • score
  • activityLevel
  • freshnessSeconds
  • lastTradeAt
  • eventRiskReadiness.domain
  • eventRiskReadiness.qualityTier
  • eventRiskReadiness.meetsQualityGate
  • eventRiskReadiness.gateFailures
  • eventRiskReadiness.resolutionControls

The top-level eventRisk object summarizes the visible response set for the strategic event-risk domains:

  • strategicDomains: climate_weather, macro_finance
  • counts: visible market counts by domain and readiness tier
  • qualityThresholds: spread, score, depth, and order-count gates
  • resolutionControlProfiles: SLA/source-control profiles for climate/weather parametric and macro-finance markets
  • apiReliability: schema version, cache policy, ETag support, commercial delay, and compatibility policy

2. Historical trade export

Endpoint: GET /api/data/trades

Use it to retrieve normalized trades by market or public wallet address.

Supported query parameters:

  • user
  • market
  • from (ISO timestamp)
  • to (ISO timestamp)
  • cursor (opaque cursor for incremental pagination)
  • order (asc or desc, default desc)
  • limit

3. Derived signals

Endpoint: GET /api/data/signals

Use it to retrieve a ranked list of derived opportunities and execution-relevant signals built from Norynta's own liquidity and activity analytics.

Supported query parameters:

  • limit
  • lookbackHours
  • outcomeLimit
  • includeResolved
  • minVolumeUsd
  • signalType (tight_spread, high_activity, high_conviction, all)

Representative response fields:

  • slug
  • title
  • category
  • signalType
  • signalScore
  • summary
  • competitive
  • spreadCents
  • volumeUsd
  • openOrders
  • freshnessSeconds
  • leadingOutcomeIndex
  • leadingOutcomeProbability
  • confidenceGap

This is the clearest example of Norynta selling intelligence, not just normalized public market data.

4. Public wallet position export

Endpoint: GET /api/data/positions

Use it to retrieve normalized public wallet positions computed from public trade history. This endpoint is part of the paid partner Data API and requires an agent/developer API key.

Supported query parameters:

  • user (public wallet address)
  • limit
  • tradeLimit (maximum historical trades used to compute the position snapshot)

Representative response fields:

  • proxyWallet
  • asset
  • conditionId
  • size
  • avgPrice
  • initialValue
  • currentValue
  • cashPnl
  • realizedPnl
  • curPrice
  • title
  • slug
  • outcome
  • outcomeIndex
  • endDate
  • lastActivityAt

5. Market intelligence history

Endpoint: GET /api/data/market-intelligence/history

Use it to retrieve premium time-series market history for a specific event slug and outcome.

Supported query parameters:

  • slug
  • outcomeIndex
  • timeframe (1H, 6H, 1D, 1W, 1M, ALL)
  • metric (midpoint, spreadCents, volumeUsd, openOrders, qualityScore, activityScore)
  • limit

Representative response fields:

  • slug
  • title
  • category
  • outcomeIndex
  • timeframe
  • points[] with { date, value }

6. Snapshot and health surfaces

Related endpoints:

  • GET /api/events/snapshots
  • POST /api/events/snapshots
  • GET /api/events/health-snapshots
  • GET /api/events/top

These are useful for market discovery, ranking, and trading automation.

Privacy and commercialization guardrails

Norynta's recommended data-commercialization model is:

  • sell aggregated market intelligence
  • sell public/on-chain data enriched with proprietary normalization
  • avoid selling direct personal data
  • avoid exposing private identity joins or KYC material
  • avoid packaging data in ways intended to re-identify individuals

Suggested packaging

Starter

  • ranked market intelligence
  • delayed or lower-frequency polling
  • basic developer support

Pro

  • higher-frequency access
  • access to /api/data/signals
  • broader historical windows
  • snapshot + health + trade and public-position export access
  • better rate limits

Enterprise

  • bulk historical exports
  • custom dataset delivery
  • access to all derived signals and premium history surfaces
  • partner SLAs
  • custom research or signal feeds

Freshness and caching

Market intelligence endpoints may return cache headers and ETags to support efficient polling and downstream caching.

Commercial data responses may also include:

  • X-Data-Plan
  • X-Data-Delay-Seconds
  • X-Data-Authenticated
  • X-Data-Usage-Policy

and a commercial object in the JSON body describing the applied freshness policy.

Schema/version contract

Commercial /api/data/* responses expose X-Api-Schema and include schemaVersion in the JSON body.

Current data-product schema version: 2026-06-10.

For institutional integrations, pin parsers to the schema version and monitor release notes before upgrading.

Delivery audit and enterprise controls

Commercial data access and enterprise delivery workflows should produce explicit audit events including:

  • dataset name
  • delivery channel (API/export/recurring)
  • customer and key identifiers (where available)
  • applied plan and freshness policy
  • result volume and request scope metadata

This supports contractual reporting, incident response, and policy assurance for institutional customers.

Authentication

Commercial data endpoints can be protected with Norynta API keys when BOT_API_KEYS is configured.

In production, the recommended model is a Supabase-backed agent key registry with hashed keys, revocation, expiry, and scope metadata. Environment-based BOT_API_KEYS should be treated as a compatibility or bootstrap path.

Supported auth formats:

  • x-api-key: <key>
  • Authorization: Bearer <key>

When API keys are enabled, /api/data/market-intelligence and /api/data/trades require one of the above credentials.

The same auth model also applies to /api/data/market-intelligence/history.

Commercial plans

Recommended packaging for API keys:

Starter

  • access to /api/data/market-intelligence
  • lower request budgets
  • optional delayed freshness

Delayed keys may receive only data older than their configured delaySeconds.

Pro

  • access to /api/data/market-intelligence
  • access to /api/data/signals
  • access to /api/data/trades
  • stronger limits and broader usage
  • typically near-real-time freshness

Enterprise

  • access to all /api/data/* endpoints
  • includes /api/data/market-intelligence/history
  • best limits, premium support, and custom delivery options

API keys can carry plan metadata, endpoint entitlements, and customer identifiers for billing and reporting workflows.

Example commercial key config:

[
  {
    "id": "partner_a",
    "key": "secret-a",
    "customerId": "cust_001",
    "plan": "pro",
    "allowedEndpoints": [
      "/api/data/market-intelligence",
      "/api/data/trades"
    ],
    "rateTier": "pro",
    "delaySeconds": 0
  }
]

Related docs

  • docs/public/API_OVERVIEW.md
  • docs/public/AUTH_AND_RATE_LIMITS.md
  • docs/public/SDK_AND_EXAMPLES.md
  • docs/public/TRADING_INTEGRATION_WORKFLOW.md