cloudflare-cost-to-line: daily month-end cost forecasts sent to LINE

Key points

• Data: the README says it reads self-serve usage-based charges (USD, daily UTC line items) from Billable Usage API v1, which differ from the final amount paid including taxes, credits and invoice corrections.
• Forecast: charges so far plus the last 7 days’ average times the remaining days (including days not yet tallied) plus a configured monthly fixed cost. It holds the forecast back when data is missing, fewer than 7 days exist or the last 7 days were $0, and says free-tier overage, tiered pricing and sudden spikes cannot be forecast accurately.
• Setup: it deploys through GitHub Actions with separate tokens, a deploy token (Workers Admin at first, then Individual Workers Editor for that Worker) and a Billing Read token for charges, plus LINE Messaging API credentials. The default daily cron is 0 15 * * * (UTC) and the reporting time zone defaults to Asia/Tokyo.
• Delivery: temporary fetch failures are retried twice and then reported as an unconfirmed amount, and success means the LINE API accepted the message, not that it reached the device.

Original sources

1. Undated

   cloudflare-cost-to-line: daily month-end cost forecasts sent to LINE

   Open original source

   pych-ky’s MIT-licensed Worker sends the current month’s Cloudflare usage-based charges and a month-end forecast to LINE once a day or on demand, using the Billable Usage API.