Usage and credit: balance, holds, free usage, startup hours, a pilot's sandbox-hours and per-resource charges, in integer microdollars.

Machine time an account without credit can still run, in milliseconds, or null when the account has none. GET /v1/limits describes each field.

Outbound traffic this calendar month (UTC): bytes the account's sandboxes sent to the internet, the part the monthly free usage covered, the part charged at the quoted rate, and what that cost.

What the account uses free, drawn before credit and never charged. With no credit, a product whose free usage is used is refused (included_usage_used_up) and its running sandboxes pause, until the 1st (an account that has paid) or until credit is added.

What Runtime for Startups includes: empty unless the account was accepted to it or given it. Machine time (startup hours) is given once, used after this month's free usage and before credit, never renewed, and gone after 12 months; storage is GB kept free each month for those 12 months.

What Runtime for Startups includes at once for its 12 months, or null without it or after them, when the account's own limits apply: image builds, and sandboxes (past it, a create answers quota_exceeded).

Renamed startupIncluded; works until 30 days after the rename ships (date set at deploy), then is gone.

Renamed startupLimits; works until 30 days after the rename ships (date set at deploy), then is gone.

The account's pilot, while it serves its sandboxes, or null: a pilot is a free run agreed with Runtime. hours is its included time in sandbox-hours (running time of every pilot sandbox, whatever its size; paused and stopped time does not count); usedMs and leftMs are that time used and left, in milliseconds. Once it is used, its running sandboxes pause with their memory kept, and creates and wakes answer pilot_hours_used; to extend the pilot or ask for more hours, the account's owner writes to support.

With ?key=<key id> only: that key's own spend, so a coordinator sees which worker spent what. A key may read itself, the keys it made (POST /v1/keys) at any depth, and any key whose agent its reads already reach (an account-wide or read-only key's).

Everything this principal acts for, one row a kind, however many: how many resources, what was charged and what is held.