Skip to main content

​
Overview

WURK applies anti-abuse controls per rail and workload type. Since x402/MPP requests are payment-gated, practical throughput is usually constrained by payment challenge handling and wallet cadence.

​
Practical guidelines

  • Reuse HTTP connections and retry logic for 402 challenge flows
  • Avoid blind loops; always parse challenge metadata before retrying
  • Prefer idempotent job payloads from your side to avoid accidental duplicates
  • Back off on repeated 429 or validation failures

​
Common status codes

StatusMeaningTypical action
200Request paid and acceptedContinue workflow
400Invalid parametersFix request payload
402Payment challengeSign and retry correctly
409Conflict (duplicate/constraint)Change request inputs
429ThrottledExponential backoff

​
Reliability recommendations

  1. Cache endpoint templates for each rail (/{network}, /mpp, /mpp-solana).
  2. Add observability for:
    • challenge rate (402)
    • paid success rate (200)
    • average retry latency
  3. Store job secrets securely for later submission reads.