Skip to content
Developer platform / SDK programme

LargeQuant in the stack you already use.

REST and OpenAPI are the canonical production contract today. Tier-1 SDK source is already maintained for eight ecosystems; registry publication and automated contract-parity release engineering are completed in LQDX4.

GET /api/v1/omni
Authorization: Bearer lq_test_...

GET /api/v1/omni/molecular/capabilities

POST /api/v1/omni/finance/runs
Idempotency-Key: scenario-001
Tier-1 source

Eight official SDK codebases already follow the LargeQuant contract.

“Maintained source” means SDK code is present in the LargeQuant distribution. It does not imply that a package is already published to a public registry.

PYMaintained source

Python

largequant

sdks/python/

Package-registry publication: LQDX4
NOMaintained source

Node.js / TypeScript

@largequant/sdk

sdks/typescript/

Package-registry publication: LQDX4
PHMaintained source

PHP

largequant/largequant-php

sdks/php/

Package-registry publication: LQDX4
LAMaintained source

Laravel

largequant/laravel

sdks/laravel/

Package-registry publication: LQDX4
COMaintained source

CodeIgniter

largequant/codeigniter

sdks/codeigniter/

Package-registry publication: LQDX4
JAMaintained source

Java

com.largequant:largequant-sdk

sdks/java/

Package-registry publication: LQDX4
.NMaintained source

.NET / C#

LargeQuant

sdks/dotnet/

Package-registry publication: LQDX4
DAMaintained source

Dart / Flutter

largequant

sdks/dart/

Package-registry publication: LQDX4
GOPlanned

Go

github.com/largequant/largequant-go

go get github.com/largequant/largequant-go

RUPlanned

Rust

largequant

cargo add largequant

RUPlanned

Ruby

largequant

gem install largequant

Common abstraction

The SDKs wrap the same Omni and platform contracts.

Language packages should remain idiomatic while preserving the same identity, request ID, idempotency, run lifecycle, evidence and error semantics as REST.

Omni worldsUniversal runsEvidenceRequest IDsRate-limit metadataIdempotencyWebhooksTyped errors
Developer access

Start with REST. Move to official packages when LQDX4 publishes them.

The API contract does not change when you move from direct HTTP calls into a native SDK.