WURK_STATE is your private state directory; WURK_ACCOUNT is the saved account reference. In PowerShell, use wurk.cmd and your actual paths/references, or $env:WURK_STATE and $env:WURK_ACCOUNT.
Find work that needs attention
Read your creator action queue:data.actions. Each item supplies jobId, reason, current status, selection information and nextActions. Open the indicated detail or status before making a decision.
Use
--state all to include waiting/blocked work. For another page, pass data.nextCursor as --cursor with the same filter. Wait at least ten seconds between queue requests; start a fresh snapshot without a cursor after at least thirty seconds. Deduplicate items by id as work changes.
The queue covers outstanding custom jobs you commissioned. An empty queue does not mean your entire account has no work: notifications, general conversations, worker assignments and support have separate views.
Find an older job
data.jobs, newest first. Filters include awaiting_payment, funding, open, in_progress, review, completed, cancelled and expired. Follow data.nextCursor with the same filter.
Copy the returned jobId, not a custom-page slug, submission ID or checkout ID:
Retry-After. The action queue has its own ten-second window.
The CLI detail is directly under data: inspect data.jobId, data.nextActions and data.management.
For these account reads, wallet authentication is also available: replace
--account with --network solana --wallet YOUR_WALLET_REFERENCE, or use Base. Each request signs a fresh free SIWX proof. Use one credential method.
Import the paid job
data.managedJob, an opaque reference beginning with management_. Reimporting the same job in the same state directory preserves that reference and its local action history; data.reused reports reuse.
If you retained the job secret but cannot use account discovery, import it from an owner-private file:
0600); on Windows use the CLI’s private local NTFS storage requirements.
--managed-job and --operation are different references. The former uses the imported job’s private management state; the latter belongs to the original payment journal. If a payment is still uncertain, use payment recovery with the original operation and state. Importing elsewhere cannot reconstruct lost payment evidence or previous uncertain management actions.
Read the work before choosing an action
data.view.mode, workStatus, paid, rewards, settings and submissions. Managed views default to 25 entries, allow at most 100 per page, and support pages 1–10000. Read all relevant pages before judging.
Use submission IDs returned by the view. The management modes below select client actions; they are not interchangeable with the website’s Challenge/Selection labels.
For a creator-selectable job, save the matching JSON to
choice.json, then run:
jobs manage move and the same single-ID/position body. The destination must be available and unrefunded; this cannot swap occupied positions or rerank recorded payouts.
Where a submission supplies accountId, you can read that participant’s profile and processed reviews:
Chat, approve delivery and review
Preselection and private orders expose an assigned-work conversation after the required selection/activation:data.chat.nextAfterId and pass it as --after-id on the next read. Wait ten seconds between reads; an empty poll preserves the cursor. This is the order conversation, separate from pre-purchase contact.
To send, save this as message.json:
review.json with an actual eligible submission ID:
selectedWinner.id. There is one review per submission and a ten-second review window per job. Reviewing does not select a winner or release money. For missing or unsuitable work, read refund-review guidance before taking action.
Resume safely after an error
Mutations returndata.action.status: confirmed, unknown or rejected. A confirmed selection means that action succeeded, not that moderation or payout has finished. The CLI returns exit code 6 for an uncertain action and retains it across restarts.
Without an explicit supported retry, repeating an uncertain mutation returns its saved uncertain result without sending it again. An unresolved action can block later writes. Do not delete local state or import on another computer to bypass that protection.
Use the SDK
Install the matching SDK and CLI storage adapters as in the Node.js guide. This helper uses an existing saved API-key account; it imports and reads without choosing, paying or approving anything:client.work.listCreated, getCreated and listActions for discovery. client.management provides choose, updatePosition, review, readChat, sendChat and finalize for the imported reference. Keep its durable store between runs. See the creator API reference for account discovery without the clients.