Partner Profile
DevCo relationships are for software companies, data companies, and platform builders that want to integrate LDRG market-state intelligence into their own products or research systems.
This path is intended for teams building dashboards, analytics layers, research terminals, data products, alerting systems, and workflow tools where liquidity-dynamics intelligence needs to be consumed as a structured system input. The first question is not only whether an API exists, but how the partner's product should represent research state, confidence, version history, and user responsibility.
What This Path Covers
DevCo work centers on the output contract: how signature intelligence records are represented, versioned, tested, displayed, stored, monitored, and separated from any customer-specific account workflow. That includes schema shape, field meaning, compatibility expectations, sandbox records, fallback behavior, and a clear boundary between LDRG research outputs and the partner's own product logic.
Access Surfaces
Review Areas
- Schema design, record lifecycle, version labels, deprecation handling, research status fields, and compatibility with the partner's data model.
- Sandbox payloads, replayable examples, model-output interpretation, UI display constraints, and user-facing explanation requirements.
- Rate limits, caching assumptions, historical access, delivery cadence, error handling, monitoring, and deployment controls.
- Data licensing boundaries, attribution rules, internal support responsibilities, and separation from broker, account, or order-entry workflows.
Readiness
A productive DevCo review usually starts with the partner's intended product surface, target users, supported markets, existing data providers, expected latency, and how research outputs will be described inside the application. LDRG can then identify whether API-only access, ORLOS-compatible records, or a scoped integration review is the appropriate starting point.
Operating Boundary
LDRG does not operate the partner's customer accounts or downstream user decisions. The DevCo controls its product experience, permissions, compliance review, and customer-facing implementation. LDRG supplies research intelligence and integration support within the agreed output contract.