Apim Throttle Expert
Diagnose 429 responses from the AI Citadel APIM gateway — identify which rate-limit policy tripped (per-product quota, per-named-value rate-limit-by-key, or backend pool TPM exhaustion).
Install
$ agentstack add skill-aiappsgbb-awesome-gbb-apim-throttle-expert ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-aiappsgbb-awesome-gbb-apim-throttle-expert) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
apimthrottleexpert
When to use
The SRE Agent should invoke this skill when:
- A user reports a 429 from the Citadel gateway
- A scheduled task flags a spike in 429 responses
- Backend pool TPM utilization approaches its limit
Investigation flow
- Identify the failing operation — ask the user for the path
(/llm/v1/chat/completions, /doc/analyze, etc.) and the time window.
- Pull APIM diagnostics from Log Analytics:
``kql ApiManagementGatewayLogs | where TimeGenerated > ago(2h) | where ResponseCode == 429 | summarize count() by OperationId, ClientIpAddress, ProductId, bin(TimeGenerated, 5m) | order by TimeGenerated desc ``
- Classify the 429 by inspecting the response headers in the same log:
| Header present | Cause | Action | |---|---|---| | Retry-After: + x-throttling-source: apim-product-quota | Per-product monthly quota exhausted | Check product config; consider raising or moving caller to a different product | | Retry-After: + x-throttling-source: rate-limit-by-key | Per-key rate limit (typically per-spoke MI) | Check rate-limit policy + named value | | Retry-After: + x-aoai-throttle: true | Backend AOAI TPM exhaustion (not APIM) | Scale up AOAI deployment or move to PTU | | No Retry-After | Bug in policy — escalate | Read the operation's policy XML |
- For backend exhaustion, check the BackendPool config:
``bash az apim api operation policy list ... ``
- Output the classification, the specific policy / quota that triggered, the per-product utilization, and a recommended action.
Tools
This skill uses:
RunAzCliReadCommandsQueryLogAnalyticsByWorkspaceId
Safety
- Never modify APIM policy, named values, or product subscriptions
- Never read APIM subscription key contents
- All actions must be reviewed by a human
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: aiappsgbb
- Source: aiappsgbb/awesome-gbb
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.