read

read is the situation report. One call assembles the current picture for an asset across every domain that applies to its plane, so your agent does not stitch together price, funding, technicals, and the rest by hand. This is the call an agent makes first, and often the only one it needs.

curl -H 'Authorization: Bearer nx_your_key' \
  'https://noxint.ai/api/v1/read?id=crypto:bitcoin'

Parameters

string

One canonical asset ID. Mutually exclusive with ids.

string list

Two to ten distinct canonical asset IDs, comma-separated. Mutually exclusive with id.

Billing

Five credits per distinct returned asset, assessment included. That is the top of the rate card and it earns it: one read carries every domain headline plus the assessment, where rebuilding the same picture from domain calls costs more credits and far more context. A batch reserves up to ten assets at the rate (50 credits) and settles the actual number delivered. An asset that is refused rather than returned is not charged. For a cheap change-watch loop, poll price at 1 credit and read on change.

A crypto read, captured live

Trimmed from the production gateway, 2026-07-16:

{
  "data": {
    "asset_id": "crypto:bitcoin",
    "as_of": "2026-07-16T09:42:26.881000Z",
    "status": "live",
    "next_update_at": "2026-07-16T09:45:19Z",
    "baseline": { "window": "90d", "cadence": "1h", "n": 2160 },
    "assessment": {
      "headline_regime": { "state": "ranging", "rule": "headline_regime@1", "adx_14": 28.43 },
      "positioning": { "state": "mild_long", "funding_band": "leaning_long", "oi_trend": "unwinding", "rule": "funding_oi@1" },
      "structure": {
        "trend_state": "neutral",
        "last_event": { "type": "choch", "direction": "up", "bars_ago": 10 },
        "invalidation": { "price_usd": 64411.8, "distance_pct": 0.54, "basis": "last_choch" },
        "rule": "structure_invalidation@1"
      },
      "flow": { "state": "bid_dominant", "lead": "perp_led", "confirms_price": false, "rule": "taker_flow@1" },
      "cascade_risk": {
        "level": "low",
        "nearest_shelf": { "side": "short", "price_usd": 64327.42, "distance_pct": 0.4, "mass_usd": 194099234 },
        "rule": "shelf_cascade@1"
      },
      "risk_flags": ["flow_divergence", "single_venue_scope", "stale_inputs"],
      "confidence": { "level": "medium", "evidence": { "proved": 18, "refused": 0 } }
    },
    "headline": {
      "price_usd": 64068,
      "return_24h_pct": { "value": -1, "pctl": 30.4 },
      "funding_rate_8h_pct": { "value": 0.0065, "pctl": 84.4 },
      "oi_change_24h_pct": { "value": -3.26, "pctl": 12.4 },
      "net_taker_delta_24h_usd": { "value": 335931240, "pctl": 83.7 },
      "trend_state": "neutral"
    }
  }
}

The assessment is deterministic characterization, not model output and not advice: positioning, structure, flow, and cascade risk, each state produced by a versioned rule (funding_oi@1) so behavior changes are visible in the data itself. risk_flags names active caveats, and confidence counts the evidence: 18 inputs proved, 0 refused. Anything that cannot be delivered moves to an unavailable block under a typed reason; a worked refusal is in the data contract.

An equity read

Equities return a headline of market and filed facts, watermarked with how fresh the filing index is. There is no assessment on the equity plane. Also live, same session:

{
  "data": {
    "asset_id": "eq:0000320193:aapl",
    "shape": "operating_company",
    "as_of": "2026-07-15T23:59:59Z",
    "status": "live",
    "filings_indexed_through": "2026-07-11T23:59:59Z",
    "headline": {
      "price_usd": 327.5,
      "market_cap_usd": 4839256000000,
      "pe_ttm": { "value": "43.9", "unit": "ratio" },
      "eps_ttm": { "value": "7.46", "unit": "USD_per_share" },
      "revenue_growth_yoy_pct": { "value": "6.43", "unit": "pct" },
      "dividend_yield_pct": { "value": "0.32", "unit": "pct" }
    }
  }
}

Filed-derived values are exact decimal strings with explicit units, and the market clock (as_of) is end-of-day, separate from the filing watermark. Two clocks, both stated, neither pretending to be the other.

Using the API

Guides

Operations

MCP

Parameters

Billing

A crypto read, captured live

An equity read

​Parameters

​Billing

​A crypto read, captured live

​An equity read

Parameters

Billing

A crypto read, captured live

An equity read