Skip to main content
LQM Builder

Independently verify an LQM Evidence Packet and model evidence chain

POST /lqm/evidence-packets/{packetUid}/verify

Contract

Recomputes the schema hash, packet hash, output hash and hash-linked per-model evidence ledger and re-attests the checkpoint and evaluation hashes. Verification never grants model promotion or Financial Actions authority.

Authentication
Bearer credential required
Required scope
lqm:build:run
Status
Published

Parameters

Name Location Type Required Description
packetUid path string Yes

Code examples

These examples compose a request only. Public reference pages never transmit your credential or execute the operation.

curl

curl -X POST \
  -H "Authorization: Bearer $FINANCEGPT_API_KEY" \
  -H "Accept: application/json"
  "https://financegpt.dev/api/v2/lqm/evidence-packets/{packetUid}/verify"

javascript

const response = await fetch("https:\/\/financegpt.dev\/api\/v2\/lqm\/evidence-packets\/{packetUid}\/verify", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${FINANCEGPT_API_KEY}`,
    Accept: 'application/json',
  },
});
const data = await response.json();

python

import json
import os
import requests

response = requests.request(
    'POST',
    'https://financegpt.dev/api/v2/lqm/evidence-packets/{packetUid}/verify',
    headers={
        'Authorization': 'Bearer ' + os.environ['FINANCEGPT_API_KEY'],
        'Accept': 'application/json',
    },
)
response.raise_for_status()
print(response.json())

php

<?php
$ch = curl_init('https://financegpt.dev/api/v2/lqm/evidence-packets/{packetUid}/verify');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST => 'POST',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer '.getenv('FINANCEGPT_API_KEY'),
        'Accept: application/json',
    ],
]);
$response = curl_exec($ch);
curl_close($ch);
echo $response;

Responses

Status Description
200 Evidence Packet verification passed
409 One or more packet or ledger integrity checks failed

Authority boundary

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:run

Machine-readable sources