Skip to main content

Job creation

For {network}, use solana or base. Prefer POST JSON for briefs. The payment network and reward asset are separate. Creation is payable through x402 without account-login headers. See payment families and retries.

Payment status and recovery

Send the saved X-Checkout-Token without PAYMENT-SIGNATURE. Account/payer-wallet alternatives are available only on supported status routes; new Preselection status is token-only. Advanced USDC and Contest also support authenticated action:"recover" for their latest twenty owned jobs on the selected network. The token only authorizes its own checkout. Basic and Advanced WURK return a job secret and status URL. Previously saved Preselection operations retain their original payment/recovery route. Wallet-wide recovery can restore management of an eligible paid job, but cannot reconstruct a missing checkout token or payment journal. See the maintained recovery guide.

Creator history and action queue

Use account API-key authentication or a fresh Solana/Base SIWX proof for these free reads: Created-work status accepts all, awaiting_payment, funding, open, in_progress, review, completed, cancelled or expired. Lists omit secrets. Created-work list/detail share a ten-second account cooldown. /actions returns actions, asOf, coverage, pagination and refresh/rate-limit fields. Inspect each item’s reason, status, selection and nextActions. Lower numeric priority comes first. A payment deadline is a real payment-initiation cutoff; selectionClosesAt closes submissions and does not require the creator to choose by that instant. For a closed submission window, review qualifying entries and select winners before requesting refund review for unfilled slots. A refund request pauses selection. An unpaid reservation in the queue does not authorize another payment. When a job lacks an API secret, detail can return nextActions.website with reason:"job_secret_unavailable" and requiresOwnerSession:true. Open that returned URL in the owner’s authenticated browser. An API key or SIWX proof does not create a website session.

Job actions

Use the public skill and advertised OpenAPI alongside these workflow references.