Give an external agent a governed execution path.
FinanceGPT accepts signed agent identities, but identity is never financial authority. Every proposal still crosses the applicable policy, risk, approval, execution and reconciliation controls.
Execution flow
Use a versioned Ed25519 public identity. FinanceGPT does not need the client private signing key.
Protocol access and requested operations are independently governed and do not imply permission to move money or approve actions.
Acknowledgement is not completion. Settlement, reconciliation exceptions and assurance evidence close the loop.
Non-bypassable control boundary
External agent → signed gateway → Action Envelope → authority → policy → risk → approval → credential-isolated execution → reconciliation → assurance evidence.
Production write access remains separately governed. Financial Operations and Restricted Autonomous Operations keep their existing commercial, security and institutional gates.
Read developer documentation