Model-output API
Pull entitled models and latest signal packages into research systems, OMS workflows, dashboards, or internal risk tooling.
QSentia Platform
Explore solutionsQuantitative products, agents, platforms, and Connect APIs are open for approved institutional partners.
QSentia Connect
Connect for brokers and Family Offices.
A practical guide for approved partners who want to ingest QSentia model outputs, evidence, telemetry, and signed updates through a controlled API layer.
Connect supports partner ingestion without bypassing diligence. Model evidence, technical delivery, usage records, and capital authority remain staged and auditable.
Partner guide
Model output, evidence, and signed delivery in one controlled path.
Auth
Bearer key
Delivery
HMAC webhooks
Scope
Model entitlement
Capital
Gated approval
Recommended acceptance test
List entitled models, fetch a current latest-signal package, verify webhook signatures, and confirm usage rows are visible after the test run.
Partner capabilities
A controlled API layer for institutional ingestion.
Connect lets approved partners consume QSentia outputs while preserving security, entitlement, monitoring, and audit records.
Evidence before allocation
Backtests, trade and order logs, drawdowns, live paper returns, and broker status support diligence before capital is approved.
Signed webhooks
Receive model updates through HMAC-signed webhooks after your endpoint has passed test delivery.
Operational controls
Every key is scoped by customer, model entitlement, environment, and rate limit.
Usage and billing records
API calls and webhook deliveries create audit and usage records for partner review.
Capital stays gated
Live allocation is separate from Connect ingestion and only happens after diligence, approvals, and operating checks.
Onboarding sequence
From first review to production ingestion.
The workflow is deliberately staged so the investment team can evaluate model evidence while the technical team validates secure delivery before production use.
Review model evidence
Use marketplace and model pages to review public evidence, live paper status, backtest metrics, and sample logs.
Submit Connect application
Provide organization details, integration type, target models, expected API volume, and receiving workflow.
Approval and scope
QSentia approves the partner, creates the customer record, sets model entitlements, and assigns request limits.
Receive API key
Store the sandbox or production key in a secret manager. Do not place it in browser code, notebooks, or spreadsheets.
Pull and validate outputs
Call the models endpoint, fetch latest signals, reconcile timestamps, and record the QSentia model id internally.
Register webhooks
Add HTTPS endpoints, verify signatures, send test events, and enable scheduled delivery after test logs are clean.
Operate and audit
Monitor usage rows, webhook deliveries, billing status, and model entitlement changes in the Connect portal.
API quickstart
Minimum endpoints for a partner integration.
Approved partners use a bearer API key. Production systems should fail closed when rate limits are exhausted or signatures cannot be verified.
API docsMethodEndpointPurpose
GET
/api/connect/v1/modelsList entitled models, broker status, latest signal time, and live return context.
GET
/api/connect/v1/models/{model_id}/latest-signalFetch the latest signal package for one entitled model.
GET
/api/connect/v1/webhooksReview registered endpoints and delivery state.
POST
/api/connect/v1/webhooksRegister a receiving endpoint for signed delivery.
POST
/api/connect/v1/webhooks/testQueue and dispatch a test event.
Operating controls
How partners run Connect safely.
Connect is not intended to bypass investment diligence. It gives partners a controlled way to ingest model output while preserving oversight.
Security
Bearer keys are scoped and revocable. Webhook secrets stay server-side and are shown once to the partner.
Rate limits
Requests are constrained per minute and per day. Partners monitor limit headers and back off before exhaustion.
Usage records
API calls and webhook deliveries write audit and usage rows for operational and commercial review.
Capital workflow
Evidence and Shadow Mode come first. Actual capital enters selected models only after gated approval and account setup.
Partner launch checklist
Launch only after the evidence and delivery path are clean.
Investment allocation, brokerage setup, and live execution remain separate gated stages subject to diligence, agreements, and operational approval.
Integration owner and technical owner are named.
Target model ids and environment are approved by QSentia.
API key is stored in a secret manager and rotated when ownership changes.
Webhook receiver uses HTTPS and validates QSentia HMAC signatures.
Test webhook event is accepted, logged, and idempotently handled.
Usage logs and billing-meter rows are reviewed before production delivery is enabled.