Skip to main content
GET
Financial Health

Authorizations

X-API-Key
string
header
required

Response

200 - application/json

Successful Response

Financial system health status.

treasury_balance_usdc
number
required
Required range: x >= 0
pending_settlements
integer
required

Pending rows still inside the sweep's retry budget (in-flight). Rows the sweep cannot rebuild into a payment are charged the same budget (#246), so they drain to exhausted_settlements rather than sitting here forever

Required range: x >= 0
total_revenue_usdc
number
required
Required range: x >= 0
agents_tracked
integer
required
Required range: x >= 0
frozen
boolean
default:false
exhausted_settlements
integer
default:0

Pending rows whose sweep_attempts reached MAX_RETRIES: credited, never settled, no longer retried. Not included in pending_settlements

Required range: x >= 0
failed_settlements
integer
default:0

Ledger rows the startup sweep resolved to FAILED (#196). These are no longer counted by pending_settlements, so without this they would disappear from the health view entirely.

Required range: x >= 0
uncollected_usdc
number
default:0

USDC credited to the ledger that will never settle: exhausted PENDING plus FAILED rows (#359). Reconciliation work, expressed as money rather than as two row counts.

Required range: x >= 0
settlement_configured
boolean
default:false

True when the EVM settler would run (SETTLEMENT_RPC_URL and SETTLEMENT_PRIVATE_KEY both set). EVM leg only; see solana_settlement_configured for the other leg. When False, EVM rows stay pending indefinitely

solana_settlement_configured
boolean
default:false

True when the Solana settler would run (SOLANA_RPC_URL and SOLANA_FEE_PAYER_PRIVATE_KEY both set). All three settlement counters above are chain-mixed, so both flags must be read to know whether they are trustworthy. When False, Solana rows stay pending indefinitely

failed_settlement_queue_depth
integer
default:0
Required range: x >= 0