SDKs & integration onboarding
SDK lifecycle & generated clients
Move from the published API v2 contract into verified SDK packages or generated cURL, JavaScript, Python and PHP starters while keeping credentials, scopes and financial authority separate.
Overview
Quickstart
API reference
Guides
LQM Builder
SDKs
Auth & webhooks
Changes
Versioning
CI
Support
Certification
Programme
Ecosystem
Solutions
References
Evidence exchange
Status
Marketplace
API plans
Contract delivery ยท Pin the current OpenAPI fingerprint in CI before deploying generated or packaged clients. Open CI tooling
Contract lifecycle
Published package fingerprints remain immutable. Contract attestation is reported separately from package integrity and is never inferred from a release name.
OpenAPI SHA-256
228f3cf999f801d03634f0dad1fc6d296671bc13a8cf0d80994b00a57b62f910Published SDK records
3
Generated client boundary
Source generation only
No server-side API execution and no embedded credentials.
Integration tracks
Credentials stay outside source control. Examples use environment-variable placeholders only.
cURL
Any shell with cURL
export FINANCEGPT_API_KEY="your-sandbox-key"Fastest path for contract verification, generated starters and CI smoke calls.
JavaScript
Node.js 18+
export FINANCEGPT_API_KEY="your-sandbox-key"Use native fetch for direct API v2 calls, generate an operation starter, or download a published FinanceGPT JavaScript SDK.
Python
Python 3.9+
export FINANCEGPT_API_KEY="your-sandbox-key"Use requests for direct API v2 calls, generate an operation starter, or download a published FinanceGPT Python SDK.
PHP
PHP 8.1+
export FINANCEGPT_API_KEY="your-sandbox-key"Use the cURL extension for direct API v2 calls, generate an operation starter, or download a published FinanceGPT PHP SDK.
Onboarding checklist
The same application, scope and authority boundaries should survive the move from Explorer to your codebase.
- Create a least-privilege sandbox application in the Developer Console.
- Keep the credential outside source control and load it from an environment variable or secret manager.
- Use the API Explorer to validate the exact operation, path parameters, request body and required scope.
- Use the SDK lifecycle manifest to verify package fingerprints and explicit OpenAPI contract attestation status.
- Generate a cURL, JavaScript, Python or PHP starter for the exact operation without embedding credentials.
- Inspect workspace-scoped request latency and failures in Developer Observability before requesting production access.
- Request production access separately; application identity does not create model, policy or transaction authority.
Generated client starters
Open any API Reference operation and choose SDK onboarding to generate a starter bound to that exact operation and current OpenAPI fingerprint.
Published SDK releases
Downloadable client packages with immutable SHA-256 fingerprints and independently reported package/contract status.
| SDK | Version | Runtime | Package integrity | Contract attestation | Actions |
|---|---|---|---|---|---|
FinanceGPT JavaScript SDK33cbd6d47073742cd798942eaa4105c898df06961d39a073760dfab43ff8f5a4 | 0.1.0 | Node.js 18+ | verified | not attested | ManifestDownload ZIP |
FinanceGPT PHP SDKb34be3bc2b319954052112604b1237293453a7bc3a0be80257078a820de7bf4b | 0.1.0 | PHP 8.1+ | verified | not attested | ManifestDownload ZIP |
FinanceGPT Python SDK031137c08eec5c8ac95d53f1345e7087db37c4d009a0a7c9396de2b1baa37bc6 | 0.1.0 | Python 3.9+ | verified | not attested | ManifestDownload ZIP |
MCP quick start
Create an AI agent application, grant MCP plus underlying tool scopes, then bind it to an Agent Profile.
POST https://financegpt.dev/api/mcp
Authorization: Bearer $FINANCEGPT_API_KEY
MCP-Protocol-Version: 2026-07-28
Mcp-Method: tools/list