Skip to main content
Developers
DOCUMENTATION

Build from clear financial developer boundaries.

FinanceGPT developer documentation is organised around the integration surface you need: APIs, SDKs, MCP, models, agents, integrations and governance.

Answer-first: FinanceGPT developer documentation describes the public integration contracts, concepts and governance boundaries used to build financial applications on FinanceGPT.

FinanceGPT Developers
intent = "forecast liquidity"evidence = workspace.data()model = LQM.run(evidence)reasoning = QLM.compose(model)action = policy.review(reasoning)
APISDKsMCPLQMQLMAgents
Data & evidenceQuantitative modelLanguage orchestrationGoverned tools
CAPABILITIES

What this workflow brings together.

The public page explains the outcome first, then keeps the underlying financial methods, evidence and review path visible.

Platform concepts
Authentication and permissions
API integration patterns
SDK integration patterns
MCP concepts
Model and agent concepts
Integration governance
Financial Actions boundary
HOW IT WORKS

From intent to reviewable output.

FinanceGPT should make complex financial work easier to express without hiding the evidence, calculations or control points.

Start with the quickstart and platform concepts.
Choose the integration surface your application requires.
Apply authentication and permission controls.
Test the application against bounded financial workflows.
Review governance and Financial Actions boundaries before production use.