Account Tools

Account tools are pre-built automation flows that act on a single account or a batch of accounts. Behind the scenes they're driven by Flavor, our headless web driver, which means they can interact with Jagex's web properties (login, account creation, support forms, OAuth) without you babysitting a browser.

You can run account tools manually from the Accounts page, schedule them via Triggers, or invoke them programmatically via the Public API.

Available tools

All five are first-party Flavor scenarios. Custom tools written by you or your team can be plugged in alongside them.

Tool reference

ban_appealer

Inputs: email, password, optional totp_secret, optional proxy. Output: success/failure status and the appeal-form diagnostics. Best run shortly after the ban — Jagex weighs recency.

account_creator

Inputs: optional email and password (auto-generated if omitted), required birthday_day (1–31), birthday_month (1–12), birthday_year (1900–2010), optional receive_emails, optional proxy. Output: a new account record with credentials and 2FA secret. Use a residential proxy if you're creating in volume.

jagex_upgrader

Inputs: email, password, optional totp_secret, optional proxy. Output: migration status. The account's tokens get refreshed inside Pitchfork on success — no manual import needed.

2fa_enabler

Inputs: email, password, optional proxy, optional save_backup_codes. Output: 2FA secret (always) and backup codes (if requested). Pitchfork stores the secret on the account so the standard login flow can derive TOTP codes automatically.

status_checker

Inputs: email, password, optional totp_secret, optional proxy, plus boolean toggles to skip subchecks: check_ban_status, check_membership, check_2fa_status, check_jagex_account. Output: a structured report. Cheap to run; useful as a recurring trigger to spot ban waves early.

Running tools

From the UI

1. Go to Accounts, select one or more rows
2. Run Account Tool → pick a tool from the list
3. Fill in tool-specific parameters; choose a priority (launch runs immediately, background queues behind active scripts)
4. Pick the agent to run on, then Run

Via Triggers

Use the start_account_tool action on any trigger. For example, fire status_checker on a scheduled trigger every hour for a group, or fire ban_appealer automatically off an account_banned trigger.

Via Public API

POST /api/account-tools/run
Content-Type: application/json

{
  "account_id": 1234,
  "tool_name": "status_checker",
  "agent_id": "my-agent-1",
  "priority": "background",
  "parameters": { "check_ban_status": true, "check_membership": true }
}

Returns a task_id. Poll GET /api/account-tools/status/{task_id} until status is completed or failed. Batch invocations go to POST /api/account-tools/batch with either account_ids[] or group_id (not both).

Custom tools (Flavor)

The same machinery powers your own automations. Flavor scenarios are headless browser flows defined in YAML or driven via its Go API; they can be registered as account tools and shown in the same UI as the first-party ones. Discord ping #flavor-dev if you want to write your own.

Status of historical doc claims

The earlier "in development" list mentioned a Jagex session grabber and an account checker — neither shipped under those names. Their use cases are covered by:

• Session grabbing → the Auth Capture trigger action (different mechanism, same outcome)
• Account checker → status_checker