diligence

Daily Spend

This organization's recorded provider spend for one UTC calendar day.

An automatic worker has to enforce a per-day spend ceiling, and the only trustworthy number for that is the ledger Scout writes in the same transaction as each step result. Reading it back out beats a worker totalling its own local logs: a restarted, redeployed or duplicated worker forgets what it spent, and the ledger does not.

The total is deliberately EVERY cost_ledger row for the org on that day, not only automatic-worker rows. The ledger carries no actor column, and the direction that matters is conservative: an operator's manual run must eat into the automatic budget, never hide from it.

created_at is a timezone-aware column, so the [day, day+1) window is a real UTC day regardless of the server's local zone.

get/v1/internal/diligence/spend

Query parameters

daystring nullable

UTC calendar day, YYYY-MM-DD

UTC calendar day, YYYY-MM-DD

Headers

authorizationstring nullable
X-Tenantstring nullable

Response

Successful Response

object required