Batch-add accounts to my ZcodeKnight gateway, FULLY AUTOMATIC.

Gateway: {BASE_URL}  (admin key: I will provide it when you ask)
Panel page: {BASE_URL}/admin
Account credentials: I will provide the list (email + password per line) when you ask.

Do this:
1. POST {BASE_URL}/admin/api/accounts/login/batch
   Headers: Authorization: Bearer <admin key>, content-type: application/json
   Body: {"count": N, "provider": "zai"}   (namePrefix OPTIONAL — omit it; accounts default to their email. Pass it only if the user explicitly asks for custom names)
   Save every sessionId + authorizeUrl from the response.
2. For each authorizeUrl, open it with your browser automation (Playwright or
   browser-use), sign in with THAT account's email + password, and complete
   the authorization. Sessions expire 5 minutes after creation — process them
   in small waves (e.g. 3-5 at a time) so nothing expires while you work.
3. Poll POST {BASE_URL}/admin/api/accounts/login/batch/status
   Body: {"sessionIds": ["<all sessionIds>"]}
   Repeat every 5 seconds until summary.pending is 0. Report each account's
   ok/error and the final summary. The engine registers every successful
   account into the pool automatically — no further calls needed.
4. If some sessions expire before automation finishes, call the batch
   endpoint again for just the missing count and repeat steps 2-3.
5. Type credentials ONLY into the provider's own authorize page opened from
   its authorizeUrl — never send them to any other endpoint or third party.

Manage the invitation registry on my ZcodeKnight gateway, via its admin API only.

Gateway: {BASE_URL}  (admin key: I will provide it when you ask)
Panel page: {BASE_URL}/admin  (Invite page)

Auth for every call:
- Header: Authorization: Bearer <admin key>
- If you authenticate with the panel Cookie session instead, every POST/PATCH must
  also send the x-csrf-token header from the login response.

Contract:
- GET  {BASE_URL}/admin/api/invites?search=&category=&status=&accountId=&page=1&pageSize=20&sort=
  -> { entries: [{ id, ownerAccountId?, code, url, label, category, tags, source,
       campaignId, status, effectiveStatus, maxUses, usedCount, reservedCount,
       expiresAt, note, createdAt, updatedAt }], total, page, pageSize, totalPages,
       categories, settings: { defaultStrategy }, assignments: [...], accounts: [...] }
- GET  {BASE_URL}/admin/api/invites/stats -> { total, active, paused, expired, exhausted, assignedAccounts }
- POST {BASE_URL}/admin/api/invites  body { code | url, label?, category?, tags?, campaignId?, status?, maxUses?, expiresAt?, note?, ownerAccountId? } -> { entry }
- PATCH {BASE_URL}/admin/api/invites/:id  same fields, partial -> { entry }
- POST {BASE_URL}/admin/api/invites/:id/assign  { accountId, requestId? } -> { assignment, entry }
- POST {BASE_URL}/admin/api/invites/assign-next  { accountId, strategy: "round_robin", category?, requestId? } -> { assignment, entry }
- POST {BASE_URL}/admin/api/invites/:id/release  { accountId } -> { ok }
- POST {BASE_URL}/admin/api/invites/settings  { defaultStrategy: "manual" | "round_robin" } -> { settings }
- GET  {BASE_URL}/admin/api/marketing?accountId=<id> -> { accountId, fetchedAt, fresh, available, deliveries: [...], error? }

Rules you must follow:
1. This gateway's registry is LOCAL bookkeeping. An assignment returned by the
   assign endpoints is a LOCAL reservation, NOT a successful official use, and
   nothing here redeems, activates or spends a code upstream. Never report an
   assignment as a completed redemption.
2. Never invent official links, rewards or remaining-chance counts. If a field
   (expiresAt, maxUses, campaignId, remainingChances, a URL) is null/missing,
   say it is unknown.
3. `source` is "manual" for entries an operator entered and "official" for ones
   the engine knows about. Only manual entries can be created/edited through
   this API.
4. Prefer PATCH for edits; it accepts a partial body. Use an explicit null to
   clear an optional field such as ownerAccountId or expiresAt.
5. Do not attempt automatic external redemption, claiming or captcha solving
   through these endpoints — the API has no such call, and the Invite page never
   performs one.
6. Never send provider passwords anywhere: no endpoint here accepts them.