[api-consumption] 📊 GitHub API Consumption Report — 2026-05-23

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-05-23 · Repository: github/gh-aw · Run: #26331003925

---

Today at a Glance

Metric	Value
🤖 Total Runs	95 (58 ✅ / 37 ❌)
🎯 Success Rate	61.1%
🔗 GitHub REST API Calls	10,619 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	29 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	442s (p95: 1036s)

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption has been volatile across the 6-day window in cache, peaking at ~80K on 2026-05-20 and dropping sharply to 10.6K today. The 7-day rolling average highlights a downward bias after the 2026-05-20 spike, suggesting either lighter workflow activity or improved API efficiency over the last 48 hours.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

With only two days of granular per-workflow detail in the trend window (2026-05-22 and 2026-05-23), the top consumers are reviewer-style agents (Test Quality Sentinel, Matt Pocock Skills Reviewer, Design Decision Gate, PR Code Quality Reviewer). These workflows consistently consume the most quota because they fetch PR diffs, files, and review context for every invocation. Building richer history over coming days will surface stronger longitudinal patterns.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap currently shows a single short week of activity since tracking just started; cells outside the May 18–23 range are empty (cool) by design. Wednesday 2026-05-20 stands out as the hottest day so far at ~80K core-quota calls. Expect richer weekly patterns to emerge once the 90-day window fills out.

---

🍩 Top API Burners (24h)

No single workflow dominates today's REST API mix — the top five consumers (Test Quality Sentinel, Matt Pocock Skills Reviewer, Design Decision Gate, PR Code Quality Reviewer, Smoke CI) together account for roughly 53% of all calls, with a long tail of smaller workflows. This even distribution lowers concentration risk but also means there is no obvious single optimisation target.

---

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

The top consumer (Test Quality Sentinel) used 1,446 core-quota calls — well below the 15K/hour hard limit, so no workflow is at immediate risk. Reviewer-style agents (positions 1–4) sit between ~1.0K and ~1.5K calls each; collapsing redundant pull_request_read fetches via caching or trimming repeated get_file_contents calls would be the cheapest optimisation lever. Total per-run consumption is healthy.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Test Quality Sentinel	1,446	4	8m 24s
Matt Pocock Skills Reviewer	1,379	4	4m 9s
Design Decision Gate 🏗️	1,328	4	5m 17s
PR Code Quality Reviewer	1,007	4	5m 6s
Smoke CI	553	4	3m 3s
[aw] Failure Investigator (6h)	544	2	4m 47s
Daily Documentation Healer	386	1	9m 55s
Daily Observability Report for AWF Firewall and MC	378	1	4m 2s
Contribution Check	357	3	8m 12s
Outcome Collector	259	2	5m 17s

---

Trending Indicators

• 7-day API trend: → (insufficient data — need ≥14 days of history)
• 30-day API trend: → (insufficient data — need ≥60 days of history)
• GitHub REST API call rate: 39,555 calls/day average over last 7 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 (5 entries)
• Collection mode: backfill
• Logs start_date used: -90d
• Data points stored: 6
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · ● 17.4M · ◷

• expires on May 26, 2026, 11:20 AM UTC

[github-actions[bot]]

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

A newer discussion is available at Discussion #34414.