feat: billing and usage commands — view traffic, compute, and cost data

[the-pulli]

Description

The Cloud CLI currently has no way to view billing, usage, or traffic information. Users must open the Cloud dashboard to check bandwidth consumption, request counts, compute hours, or estimated costs.

As the CLI already covers most operational workflows (deployments, environments, commands, domains, etc.), adding billing and usage visibility would make it a complete management tool without requiring context-switching to the browser.

Suggested commands

# Current billing period summary (compute, bandwidth, requests, storage, cost)
cloud billing:usage

# Usage breakdown per environment
cloud billing:usage --environment=production

# Usage for a specific time range
cloud billing:usage --from=2026-03-01 --to=2026-03-18

# Current billing period invoice / cost estimate
cloud billing:estimate

# List past invoices
cloud billing:invoices

# View a specific invoice
cloud billing:invoice <invoice-id>

All commands should support --json for machine-readable output (useful for monitoring scripts, alerts, and CI cost tracking).

Use cases

• Quick traffic check: After a deployment or marketing campaign, verify bandwidth/request usage without leaving the terminal
• Cost monitoring in CI: Integrate usage checks into deployment pipelines to flag unexpected cost increases
• Multi-environment comparison: Compare usage across staging vs. production
• Budget alerts: Script periodic checks with --json output to trigger notifications when usage exceeds thresholds

Context

Related to #68 (metrics endpoints) but distinct — #68 covers real-time resource performance metrics (CPU, memory, connections), while this request covers aggregate billing and traffic data over time.

Environment

• Cloud CLI: v0.1.15

[JoshSalway]

Great idea — would love to have this. However, the Cloud API doesn't currently expose any billing, usage, or invoice endpoints. The CLI can only surface what the API provides.

This would need API-side support first (billing/usage endpoints), then the CLI commands could be built on top of them.

[the-pulli]

Thanks for the quick response, @JoshSalway. Understood — the CLI can only wrap what the API exposes.

Would it be worth opening a corresponding feature request on the Laravel Cloud feedback/roadmap (if one doesn't exist yet) to get the billing/usage API endpoints on the radar? Happy to do that if it helps move things forward, or if you can flag it internally that would be great.

[JoshSalway]

@the-pulli probably best to request that feature with the cloud team in the support chat, but I don't work for Laravel so don't know the correct approach regardless it's mentioned here for review.

[the-pulli]

Thanks — good to know. I'll reach out to the Cloud team via support chat directly. Will report back here if there's any update.

[Frostist]

I have started on just a basic usage command, which the api supports, but doesn't have support for the estimated etc