[api-consumption] 📊 GitHub API Consumption Report — 2026-06-19

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-06-19 · Repository: github/gh-aw · Run: #27824516852

⚠️ Partial collection note: The agentic-workflows logs MCP call timed out after downloading 57 complete run records (out of ~112 directories started) for the last 24h window. Today's totals therefore undercount actual activity (recent days saw 100–390 runs/day). Trends and per-workflow rankings below reflect only the runs successfully captured.

---

Today at a Glance

Metric	Value
🤖 Total Runs	57 (54 ✅ / 3 ❌)
🎯 Success Rate	94.7%
🔗 GitHub REST API Calls	9,791 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	37 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	639s (p95: 1307s)

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption is highly volatile, swinging between ~2.4K and a 574K peak on 2026-06-17 — driven by occasional heavy read/write bursts rather than a steady baseline. The 7‐day rolling average sits well above today's captured 9.8K, reflecting both the recent spike and today's partial collection. Outside the spikes, most days land in the single-digit-thousands range.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

CI- and review-oriented workflows — Smoke CI, Test Quality Sentinel, and the PR review agents — are the most consistent per-workflow consumers across the window. Spikes in the total line track days with elevated PR and issue activity. No single workflow dominates every day; leadership rotates with the day's event mix.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap shows consumption concentrated on mid-week development days, with the deepest cells aligning to the 2026-06-09 and 2026-06-17 burst days. Weekends are visibly lighter. The pattern is bursty rather than uniform, consistent with event-driven (PR/issue) triggering.

---

🍩 Top API Burners (24h)

Smoke CI (2,632) and Test Quality Sentinel (2,199) together account for roughly half of captured 24h consumption. The two top review agents (Matt Pocock Skills Reviewer, PR Code Quality Reviewer) and Design Decision Gate each add ~1K. Consumption is moderately concentrated in the top five, which is worth watching but not yet a single-point risk.

---

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

Even the heaviest single consumer (Smoke CI at 2,632) stays far below the 15,000/hr core limit, so there is comfortable headroom in the captured set. Smoke CI's load is spread across 7 runs (~376/run); the single-run consumers (Test Quality Sentinel at 2,199, the review agents at ~1K each) are the best candidates for caching or narrowing API queries if optimisation is pursued.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	2,632	7	276s
Test Quality Sentinel	2,199	1	606s
Matt Pocock Skills Reviewer	1,046	1	554s
PR Code Quality Reviewer	1,015	1	542s
Design Decision Gate 🏗️	1,014	1	324s
Sub-Issue Closer	366	1	534s
PR Sous Chef	330	3	479s
Contribution Check	289	2	664s
Auto-Triage Issues	180	2	340s
AI Moderator	166	2	1125s

---

Trending Indicators

• 7-day API trend: ↑ +40.8% vs. previous 7 days (inflated by the 2026-06-17 burst and today's partial capture)
• 30-day API trend: → insufficient data (history spans 31 days; a clean 60-day baseline is not yet available)
• GitHub REST API call rate: ~97,578 calls/day over last 7 days (hourly limit: 15,000) — skewed heavily by the single 574K spike day; the median day is far lower

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (30 entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 31
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · 234.1 AIC · ⌖ 37.5 AIC · ⊞ 12.1K · ◷

• expires on Jun 22, 2026, 4:16 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 #40459.