Time-bucketed, aggregated serverless compute usage for your own account — the machine-seconds your deployed serverless apps consumed, priced with your machine prices and net of discounts. This matches the serverless portion of the dashboard usage view. Unlike /v1/models/usage (which reports model API endpoint calls), this reports the sdk_billing_event compute spend of the apps you run on fal Serverless. Results are always scoped to the apps you own.

Filtering by app:

• app — exact match on one or more app names (comma-separated or repeated, up to 50): ?app=my-app-dev,my-app-prod. Use the value exactly as it appears in the response app field.
• search — case-insensitive substring match on the app name, for when you know the name but not the exact environment/version suffix: ?search=my-app returns every my-app* variant.
• Provide both to AND them. Omit both to return every app you own — useful for discovering the exact app names to filter on.

Expansions:

• time_series: usage grouped into time buckets (default)
• summary: a single aggregate row per app × machine type across the window

Notes:

• Each row is machine-seconds (unit is always "second"); surge and non-surge usage of the same app/machine come back as separate rows (is_surge), so sum across them for a per-app total.
• Time-series bucket timestamps are returned in the timezone you request (ISO 8601 with offset, e.g. 2025-01-15T00:00:00-05:00), which also controls how usage is grouped into buckets.

Common Use Cases:

• Track your serverless apps' compute consumption and cost over time
• Break down spend per app, environment, and machine type
• Export usage to your own billing/observability tooling

Required permissions: billing:usage:read. Key presets that include them: BILLING, READONLY, FULL. See key permissions.