Register a quantitative LQM before training

Creates the canonical model identity in the existing FinanceGPT ML registry and attaches an LQM profile. This does not start training.

{
    "name": "string",
    "task_family": "forecasting",
    "intended_use": "string",
    "license": "string"
}

curl

curl -X POST \
  -H "Authorization: Bearer $FINANCEGPT_API_KEY" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  --data '{
    "name": "string",
    "task_family": "forecasting",
    "intended_use": "string",
    "license": "string"
}' \
  "https://financegpt.dev/api/v2/lqm/models"

javascript

const response = await fetch("https:\/\/financegpt.dev\/api\/v2\/lqm\/models", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${FINANCEGPT_API_KEY}`,
    Accept: 'application/json',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "name": "string",
    "task_family": "forecasting",
    "intended_use": "string",
    "license": "string"
}),
});
const data = await response.json();

python

import json
import os
import requests

response = requests.request(
    'POST',
    'https://financegpt.dev/api/v2/lqm/models',
    headers={
        'Authorization': 'Bearer ' + os.environ['FINANCEGPT_API_KEY'],
        'Accept': 'application/json',
    },
    json=json.loads('{"name":"string","task_family":"forecasting","intended_use":"string","license":"string"}'),
)
response.raise_for_status()
print(response.json())

php

<?php
$ch = curl_init('https://financegpt.dev/api/v2/lqm/models');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('FINANCEGPT_API_KEY'),
        'Accept: application/json',
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode(array (
  'name' => 'string',
  'task_family' => 'forecasting',
  'intended_use' => 'string',
  'license' => 'string',
)),
]);
$response = curl_exec($ch);
curl_close($ch);
echo $response;

A developer credential proves application identity and permits only its scopes. It does not grant model promotion, policy override, QLM rebinding, or Financial Actions execution authority unless those separate controls are satisfied.

lqm:build:write