[api-consumption] 📊 GitHub API Consumption Report — 2026-08-14

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-08-14 · Repository: github/gh-aw · Run: #31794554591

---

Today at a Glance

Metric	Value
🤖 Total Runs	166 (152 ✅ / 14 ❌)
🎯 Success Rate	91.57%
🔗 GitHub REST API Calls	117,760 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	285 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	586.4s (p95: 1211.3s)

---

🔗 GitHub API Calls Trend (90 days)

Only 4 days of history are currently available (2026-08-11 through 2026-08-14) out of the nominal 90-day window — a full backfill is still building up in cache-memory. Daily consumption swung widely, from a low of ~71K calls on 08-12 to a peak of ~193K calls on 08-11, before settling to 117.8K today. The 7-day rolling average is trending downward from its 08-11 peak as more recent, lower-volume days enter the window.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

Across the 4 available days, PR Sous Chef, Impeccable Skills Reviewer, PR Code Quality Reviewer, Matt Pocock Skills Reviewer, and Design Decision Gate 🏗️ consistently rank as the top 5 REST API consumers — each a PR-review-triggered workflow that fires on most PR pushes. Their relative ordering shifts slightly day to day depending on PR volume, but the same five workflows dominate every day observed so far.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Fewer than 14 days of history exist, so the calendar heatmap falls back to a bar chart of today's top workflows by REST API consumption. PR Sous Chef leads today's consumption at 12,480 calls, followed closely by three review workflows each in the 7.7K–8.2K range — indicating consumption is fairly evenly spread across the top PR-review agents rather than concentrated in a single outlier.

---

🍩 Top API Burners (24h)

The top 10 workflows account for the large majority of today's 117,760 calls, with PR Sous Chef the single largest consumer at ~10.6% of the daily total. No single workflow dominates outright — consumption is distributed across a cluster of PR-review and triage workflows, with a long tail of 79 additional lower-volume workflows grouped as "other."

---

🔗 GitHub REST API Consumption by Workflow (last 24h)

PR Sous Chef (12,480 calls) is today's top REST API consumer, followed by PR Code Quality Reviewer (8,158), Ponytail Reviewer (8,078), Impeccable Skills Reviewer (8,045), and Matt Pocock Skills Reviewer (7,689). All top workflows remain well under the 15,000/hour rate limit individually, but the cumulative load from the five review workflows firing on the same PR events (~44K calls combined) is worth watching if PR volume grows.

---

Top 10 Workflows by REST API Consumption (last 24h)

Workflow	REST API Calls	Runs	Avg Duration
PR Sous Chef	12,480	17	479.9s
PR Code Quality Reviewer	8,158	9	405.6s
Ponytail Reviewer	8,078	9	413.9s
Impeccable Skills Reviewer	8,045	9	387.0s
Design Decision Gate 🏗️	7,699	9	413.8s
Matt Pocock Skills Reviewer	7,689	9	434.1s
Issue Monster	5,113	4	409.8s
Auto-Triage Issues	2,892	2	410.5s
Avenger	2,768	4	898.3s
PR Triage Agent	2,520	2	731.0s

---

Trending Indicators

• 7-day API trend: → (insufficient data — only 4 days of history collected so far)
• 30-day API trend: → (insufficient data — only 4 days of history collected so far)
• GitHub REST API call rate: ~134,826 calls/day averaged over the 4 available days (hourly limit: 15,000)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (3 entries)
• Collection mode: backfill
• Logs start_date used: -90d (requested), but pagination was cut off after the initial call plus 2 additional continuation calls (per the bounded-retry policy), so the effective collected window only spans 2026-08-13 to 2026-08-14 (~1 day), not the full 90 days. The remaining historical runs were not fetched this run.
• Data points stored: 4
• Earliest entry: 2026-08-11
• Retention policy: 90 days

Note on partial data: This run's log collection hit the count-limit continuation cap after 3 total logs calls (as instructed, at most 2 additional continuation calls beyond the first). The dataset backing this report therefore reflects roughly 524 runs concentrated in the last ~1 day rather than a full 90-day history. Trend charts and indicators will fill in over subsequent daily runs as more of the 90-day window accumulates in cache-memory.

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · agent · 228 AIC · ⌖ 49.2 AIC · ⊞ 12.3K · ◷

• expires on Aug 17, 2026, 3:26 AM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #52879.