[api-consumption] 📊 GitHub API Consumption Report — 2026-04-26

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-04-26 · Repository: github/gh-aw · Run: #24969837951

---

Today at a Glance

Metric	Value
🤖 Total Runs	64 (60 ✅ / 4 ❌)
🎯 Success Rate	93.8%
🔗 GitHub REST API Calls	22,501 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	33 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	378s (~6.3 min) (p95: 1,110s / ~18.5 min)

---

🔗 GitHub API Calls Trend (90 days)

This is the first data point recorded by this monitoring workflow — today's baseline is 22,501 REST API calls across 64 runs. No historical trend is available yet; future runs will build the 90-day rolling window. As history accumulates, spikes and quiet days will become visible here.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

With only today's data available, the chart shows today's top workflows as a bar chart fallback. Design Decision Gate and Test Quality Sentinel each triggered 10 runs and jointly consumed ~8,140 REST API calls, making them the dominant consumers. Once multi-day history accumulates, trend lines will show whether their usage is growing or stable.

---

🔗 GitHub REST API Calls Heatmap (90 days)

With fewer than 14 historical data points, the heatmap falls back to a bar chart of today's top workflows by REST API consumption. Once at least 14 days of data are collected, a calendar-style heatmap will reveal day-of-week patterns and weekly rhythms.

---

🍩 Top API Burners (24h)

The top API consumer today was Design Decision Gate 🏗️ with 4,100 calls (18.2%), closely followed by Test Quality Sentinel at 4,040 (17.9%) and Smoke CI at 2,845 (12.6%). These three workflows together account for 48.8% of total REST API consumption, suggesting that PR-gating and CI workflows are the primary API drivers. The remaining 51.2% is spread across 30 other workflows.

---

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

All workflows are comfortably below the 15,000/hr hourly rate limit — the highest single consumer (Design Decision Gate) used only 4,100 calls total across 10 runs (~410/run). No immediate throttling risk exists. The most optimization opportunity lies in the Step Name Alignment and Agentic Workflow Audit Agent workflows, which each ran once but consumed 2,398 and 1,955 calls respectively — both are candidates for API call auditing.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Design Decision Gate 🏗️	4,100	10	255s
Test Quality Sentinel	4,040	10	259s
Smoke CI	2,845	9	134s
Step Name Alignment	2,398	1	558s
Agentic Workflow Audit Agent	1,955	1	1,122s
Daily DIFC Integrity-Filtered Events Analyzer	1,769	1	3,120s
Contribution Check	1,507	2	336s
Copilot CLI Deep Research Agent	1,506	1	492s
[aw] Failure Investigator (6h)	1,447	1	840s
Issue Monster	657	5	232s

---

Trending Indicators

• 7-day API trend: → N/A (first run — baseline established today)
• 30-day API trend: → N/A (first run — baseline established today)
• GitHub REST API call rate: 22,501 calls across today (hourly limit: 15,000 per resource)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: no (first run)
• Data points stored: 1
• Earliest entry: 2026-04-26
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by GitHub API Consumption Report Agent · ● 492.4K · ◷

• expires on Apr 29, 2026, 11:59 PM UTC

[github-actions[bot]]

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

A newer discussion is available at Discussion #28822.