Institutional Access

LSRI can be packaged for research teams, funds and trading desks that want a repeatable crypto market-regime layer, API-driven workflows and a cleaner operational setup than a retail-only dashboard. Institutional access starts at $500/month depending on users, API scope and support needs.

For quant desks · For portfolio risk monitoring · For systematic strategies

Who This Fits
Use Case
Research teams

Use LSRI as a compact daily regime layer for market review, internal notes, dashboards and historical regime analysis.

Use Case
Funds and desks

Support exposure review, risk committee discussion and systematic context around structural deterioration across major crypto assets.

Use Case
API workflows

Integrate the regime layer into notebooks, research pipelines, monitoring systems or internal alerting flows.

What Institutional Packaging Can Include
Delivery
Dashboard plus API

The same public logic can be consumed through dashboard views, alerting and API access, without changing the framing of the signal itself.

  • Multi-asset regime monitoring
  • Historical regime context
  • API-based internal workflows

API & data: REST, daily regime endpoint (/v2/lsri/crypto-status), update at 20:00 UTC Mon–Fri. Assets: BTC, ETH, SOL, BNB, XRP, DOGE. Higher limits and SLA options for institutional tiers.

Packaging
Access and support

The institutional layer is about operational packaging with a clearer commercial scope, not about hiding the methodology behind vague enterprise language.

  • Starting at $500/month
  • Higher API limits
  • Multi-user access
  • Priority email support
  • Research-oriented onboarding
  • Custom volume pricing
Operational fit
Designed for existing workflows

The goal is to fit LSRI into an existing research or monitoring stack without forcing a black-box operating model.

  • Shared review of dashboard vs API usage
  • Clarified access model for single or multi-user teams
  • Scope based on monitoring, reporting or alert workflows
Onboarding
Simple implementation path

Most institutional requests are packaging decisions: who needs access, what cadence matters, and whether the standard Pro layer already covers the use case.

  • Initial scoping around use case and expected scale
  • Decision between standard Pro and broader packaging
  • Operational handoff focused on practical use, not opaque sales language
What Stays Public
Transparency
Methodology and evidence remain visible

Institutional access does not depend on hiding the product. The public site already exposes methodology, track record and backtests so the framework can be inspected first.

Scope
Not a custom black box

The goal is a clearer delivery model and stronger operational access, not a marketing promise of proprietary certainty.

How The Institutional Process Works
Step 1
Share your workflow

Tell us whether the main need is research monitoring, desk context, API usage, or broader multi-user access. That lets the packaging stay operational instead of vague.

Step 2
Match the delivery model

We scope the practical setup around dashboard usage, API limits, onboarding expectations and team access rather than changing the public signal logic itself.

Step 3
Launch with a clear scope

The objective is a simple institutional wrapper around an already visible product: documented methodology, public proof pages and a cleaner operating workflow for teams.

Discuss institutional access

If you need higher limits, multi-user access or a more formal onboarding path, contact us with your team setup and intended usage. Most team packaging starts at $500/month and scales with users, API usage and support scope.

Starting at $500/month Higher API limits Research team onboarding Custom volume pricing Operational support
Useful details to include

A short message is enough. The most useful information is the team type, expected users, whether API access is required, and how LSRI would fit into your existing research or monitoring workflow.

  • Team type: research, fund, desk, allocator or advisory
  • Delivery need: dashboard, API, or both
  • Expected scale: number of users or usage intensity
  • Primary objective: monitoring, reporting, alerts or workflow integration
What happens next

We can scope whether the standard Pro layer is already enough or whether a more structured packaging model makes sense for your team.

  • Quick review of the use case and operating constraints
  • Recommendation: standard Pro vs structured team packaging
  • Clear next step for access, onboarding and workflow fit