What problem does it solve? Processing queued LLM Gateway account-contribution requests one by one through admin APIs is slow and error-prone, especially when each account needs credential preflight checks, deterministic proxy assignment, and post-issue configuration. ## Core Features & Use Cases - Batch Admin Workflow: Fetches pending requests, preflights Codex credentials (OAuth refresh plus models probe through a local proxy), validates, approves, and issues accounts in bulk. - Deterministic Proxy Assignment: Selects the least-used active proxy config with name-based tie-breaking so one batch is balanced across proxies. - Standard Post-Issue Patching: Applies auto_refresh_enabled, fixed proxy mode, concurrency limits, and randomized start intervals, then attempts a best-effort usage refresh. - Use Case: After a public batch submit creates 20 pending requests with prefix pickup7_, run the helper script in dry-run mode to review the plan, then apply it to validate, issue, and configure every account end to end. ## Quick Start Ask the agent to run the approval script against the local admin API at http://127.0.0.1:19182 with your account prefix and expected count, first as a dry run and then with --apply to issue and patch the accounts.