> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wurk.fun/llms.txt
> Use this file to discover all available pages before exploring further.

# Rate Limits

> Operational guidance for x402 and MPP traffic

## 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

| Status | Meaning                         | Typical action           |
| ------ | ------------------------------- | ------------------------ |
| `200`  | Request paid and accepted       | Continue workflow        |
| `400`  | Invalid parameters              | Fix request payload      |
| `402`  | Payment challenge               | Sign and retry correctly |
| `409`  | Conflict (duplicate/constraint) | Change request inputs    |
| `429`  | Throttled                       | Exponential 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.

## Related docs

* [Authentication](/authentication)
* [Payment Methods](/concepts/payment-methods)
* [x402 Endpoint Families](/api-reference/x402-network-endpoints)