Privy

Add explicit rate limit documentation to the API reference pages for each users endpoint (e.g., GET /users/by-wallet-address), specifying the requests-per-second threshold and whether it differs by plan tier.

Add documentation about webhook payload size limits, including maximum body size in bytes/MB and any behavior when limits are exceeded (truncation, rejection, etc.). This is important for buyers handling large transaction data who need to size their endpoints appropriately.

Add a dedicated page or section documenting the webhook retry schedule, including specific backoff intervals (e.g., exponential backoff with jitter), maximum retry attempts, and total retry window before Privy marks a delivery as failed and stops retrying.

Create a dedicated documentation page or FAQ section covering authorization key lifecycle management, specifically addressing: (1) whether old and new keys work simultaneously during rotation, (2) the duration of any grace period, and (3) recommended patterns for zero-downtime rotation. This is critical operational information for security-conscious buyers managing production systems.

Add documentation about allowed origins configuration for embedded wallets, including the maximum number of origins per app and how to configure staging/preview/production subdomains in the Privy dashboard or via API.

Add explicit documentation about React Strict Mode compatibility, including whether the SDK handles double-mounting correctly or requires specific configuration.

The pricing page (https://www.privy.io/pricing) is referenced in navigation but its content was not retrieved. The crawler should fetch the actual pricing page to capture tier details, MAU thresholds, and whether transaction fees are bundled or separate.

The key quorum documentation pages appear to have collapsed or failed to load content. The URLs suggest dedicated pages exist for creating key quorums and configuring thresholds, but the crawler retrieved only navigation shells. Expand the 'Creating key quorums' page at /controls/key-quorum/create and the 'Key quorums overview' page to capture the actual configuration parameters including maximum owners and threshold rules.

The funding documentation pages (chunks [1], [5], [10]) appear to have collapsed or failed to load substantive content—showing only navigation links, 'Was this page helpful?' prompts, and Mintlify footer rather than actual documentation body. The crawler likely failed to expand JavaScript-rendered content. The gas management pages (chunks [7], [8], [9]) are top-level navigation pages without specific details on custodial wallet gas abstraction. Need to re-crawl with JavaScript execution enabled or check if content lives in accordions/tabs that weren't expanded.

Add explicit documentation stating that the endpoint only returns users who have previously linked their Twitter account through Privy, and document any rate limits or daily lookup caps that apply.

Create a dedicated, comprehensive API error codes reference page that lists all possible error codes with their exact string values, HTTP status codes, descriptions, and programmatic handling guidance. Include a searchable table or machine-readable format (e.g., JSON schema) for the complete error catalog.

Document how to set custom intent expiration times in the API reference for intent creation endpoints, and clarify whether per-transaction or per-policy timeout configuration is supported for high-value transactions.

Add a dedicated security/compliance page that explicitly states: (1) SOC 2 Type II certification with audit date and scope, (2) penetration testing frequency (e.g., annual, quarterly), and (3) link to the most recent audit report or trust center.

Add explicit documentation on whether MFA enforcement is configurable at the organization/app level vs. per-user opt-in, and clarify the relationship between policy-based MFA and organization-wide enforcement.