submitting-llm-gateway-account-batches

Submits directories of Codex auth JSON files to the LLM Gateway batch review endpoint.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zero-yx/static_flow --skill submitting-llm-gateway-account-batches-zero-yx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: submitting-llm-gateway-account-batches
Source: https://github.com/zero-yx/static_flow/tree/main/skills/submitting-llm-gateway-account-batches
Command: npx skills add https://github.com/zero-yx/static_flow --skill submitting-llm-gateway-account-batches-zero-yx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Importing many Codex account auth JSON files one by one through the public single-submit endpoint is slow because each request is rate-limited. This Skill queues entire directories of auth files through the batch submission API so they appear in the StaticFlow LLM Gateway admin review queue as pending account-contribution requests. ## Core Features & Use Cases - Batch Submission: Scans a directory of *.json files and posts them as batched items to the /llm-gateway/account-contribution-requests/batch-submit endpoint with configurable batch size and wait intervals. - Multi-Account File Support: Expands sub2api-style files containing an accounts array into individual credential entries, extracting account_id, id_token, access_token, and refresh_token. - Safe Account Naming: Derives unique, backend-compliant account_name values from filename stems with a short SHA-256 hash suffix and optional prefix. - Use Case: You have 300 exported Codex auth JSON files in a folder. Run the helper script with --dry-run to preview the batches, confirm the contributor_message with the operator, then submit the real batch and report created, invalid, and conflict counts. ## Quick Start Ask the assistant to dry-run the submit-public-batch.sh script against your directory of Codex auth JSON files with a confirmed contributor message, then run the real batch submission.

Frequently Asked Questions about submitting-llm-gateway-account-batches

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch submit Codex auth JSON files to the LLM Gateway?▼

Run the submit-public-batch.sh script with --dir pointing to your JSON folder, --base-url set to the API base, and --message containing a reviewer-facing contributor message. Use --dry-run first to preview the batches before the real submission.

Does batch submission bypass the admin review process?▼

No, batch submission only creates pending account-contribution requests in the review queue. Every item still goes through the public submission path and requires admin validation and approval before accounts become active.

Can I submit sub2api files with multiple accounts in one JSON?▼

Yes, the script detects files containing an accounts array and expands each entry into a separate submission item. It extracts account_id, id_token, access_token, and refresh_token from each account's credentials object.

What do created, invalid, and conflict counts mean in the response?▼

The backend returns per-item statuses after each batch. Created means the request was queued as pending, invalid means the item failed validation, and conflict means a matching account already exists in the system.

Why does the script wait between batch requests?▼

The public endpoint enforces per-request rate limiting, so the script sleeps a configurable number of seconds (default 60) between batches. Keeping batch size at 200 or lower and respecting the wait interval avoids rejected requests.