Skip to main content
Agents & MCP

Request execution of an already-authorized Financial Action

POST /agent-execution/actions/{uid}/execute

Contract

Dispatches only through the existing Financial Actions execution boundary. Machine-delegated execution requires fresh signed Machine Authority evidence and autonomous live remains subject to Restricted Autonomous Operations.

Authentication
Bearer credential required
Required scope
agent:execution:execute
Status
Published

Parameters

Name Location Type Required Description
uid 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/agent-execution/actions/{uid}/execute"

javascript

const response = await fetch("https:\/\/financegpt.dev\/api\/v2\/agent-execution\/actions\/{uid}\/execute", {
  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/agent-execution/actions/{uid}/execute',
    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/agent-execution/actions/{uid}/execute');
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 Execution request accepted; reconciliation remains the completion boundary
422 Execution not authorized or control gate 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.

agent:execution:execute

Machine-readable sources