docs: add AI-generated content warnings and reorganize v2 migration page

api-features/batch-payments.mdx

@@ -3,9 +3,13 @@
 description: "Process multiple payments in a single transaction for gas optimization"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Batch payments allow you to process multiple direct or conversion payments in a single blockchain transaction, significantly reducing gas costs and simplifying payment operations.
 
 ## How It Works
 

api-features/conversion-payments.mdx

@@ -1,11 +1,15 @@
 ---
 title: "Conversion Payments"
 description: "Fiat-denominated requests settled in cryptocurrency with real-time conversion"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Conversion payments allow you to create requests denominated in fiat currencies (USD, EUR) while receiving settlement in cryptocurrency, with automatic exchange rate conversion at payment time.
 
 ## How It Works
 

api-features/create-requests.mdx

@@ -3,6 +3,10 @@
 description: "Request creation workflows and configuration for invoices and payment collection"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Request creation forms the foundation of Request Network operations, enabling structured payment collection through invoice generation and payment request workflows.
@@ -34,7 +38,7 @@
 1. **Define:** Set payee, payer, amount, and currency details
 2. **Configure:** Choose payment network and accepted tokens
 3. **Store:** Decentralized storage on IPFS
 4. **Index:** Blockchain indexing for discovery
 5. **Track:** Real-time status monitoring
 
 ## Request Properties
@@ -48,7 +52,7 @@
 ### Payment Configuration
 - **Payment Network:** ERC20, ETH, or specialized networks
 - **Accepted Tokens:** Supported payment currencies
 - **Conversion Settings:** Fiat-denominated crypto payments
 
 ## Payment Network Selection
 
@@ -63,9 +67,9 @@
 </CardGroup>
 
 ### Supported Networks
 - **Mainnet:** Ethereum, Polygon, Arbitrum, Optimism
 - **Sidechains:** BSC, Gnosis, Fantom, Avalanche
 - **Testnets:** Sepolia, Mumbai for development
 
 ## Content Data
 

api-features/crosschain-payments.mdx

@@ -1,11 +1,15 @@
 ---
 title: "Crosschain Payments"
 description: "Multi-network payment routing with automatic bridging and optimization"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Crosschain payments enable seamless transactions across different blockchain networks, allowing payers to send from their preferred chain while payees receive on their preferred network.
 
 ## How It Works
 
@@ -20,26 +24,26 @@
 - Automatic routing optimization  
 - No manual bridging required
 
 ## Samechain Payments
 
 A special case of crosschain infrastructure that converts currencies on the same network (e.g., ETH → USDC on Ethereum).
 
 ## Supported Networks
 
 <CardGroup cols={2}>
   <Card title="Layer 1" icon="link">
     Ethereum, BSC, Avalanche, Fantom
   </Card>
 
   <Card title="Layer 2" icon="layers">
     Polygon, Arbitrum, Base, Optimism
   </Card>
 </CardGroup>
 
 ## Bridge Protocols
 
 - **LayerZero:** Ultra Light Node security
 - **Stargate:** Liquidity-based bridging
 - **Automatic Selection:** Optimal route chosen
 
 ## Used In

api-features/crypto-to-fiat-payments.mdx

@@ -3,9 +3,13 @@
 description: "USDC payments settled directly to bank accounts with automatic conversion"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Crypto-to-fiat payments enable seamless conversion from cryptocurrency to traditional bank account deposits, combining the speed of crypto with the familiarity of fiat settlement.
 
 ## How It Works
 
@@ -36,8 +40,8 @@
 
 ## Supported Networks
 
 - **Production:** USDC on Ethereum, Polygon, Arbitrum
 - **Sandbox:** USDC on Sepolia (testing)
 
 ## Settlement Time
 

api-features/fee-breakdowns.mdx

@@ -3,6 +3,10 @@
 description: "Comprehensive fee transparency with USD amounts and detailed cost structures"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Detailed fee breakdowns provide complete transparency into all costs associated with payments, including network fees, service fees, and USD equivalent amounts for better financial planning.
@@ -11,7 +15,7 @@
 
 <CardGroup cols={2}>
   <Card title="Network Fees" icon="network-wired">
     Blockchain transaction costs
   </Card>
 
   <Card title="Service Fees" icon="handshake">
@@ -46,7 +50,7 @@
 
 ### Network Fees
 - **Gas Fees:** Transaction execution costs
 - **Bridge Fees:** Crosschain transfer costs
 - **Token Conversion:** DEX swap fees
 
 ## USD Amount Calculations
@@ -59,23 +63,23 @@
 ### Breakdown Format
 ```json
 {
   "baseAmount": {
     "crypto": "100 USDC",
     "usd": "$100.00"
   },
   "fees": {
     "network": {
       "crypto": "0.25 USDC",
       "usd": "$0.25"
     },
     "service": {
       "crypto": "2.5 USDC", 
       "usd": "$2.50"
     }
   },
   "total": {
     "crypto": "102.75 USDC",
     "usd": "$102.75"
   }
 }
 ```

api-features/partial-payments.mdx

@@ -3,6 +3,10 @@
 description: "Split payments across multiple transactions and funding sources"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Partial payments allow requests to be fulfilled through multiple transactions, enabling split payments, installment plans, and flexible funding approaches.
@@ -41,7 +45,7 @@
 Works with all payment types except Crypto-to-fiat payments:
 - Native & ERC20 payments
 - Conversion payments  
 - Crosschain payments
 - Batch payments
 
 ## Used In

api-features/payment-detection.mdx

@@ -1,11 +1,15 @@
 ---
 title: "Payment Detection"
 description: "Automatic reference-based payment detection system for blockchain transactions"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 The Request Network API uses a **reference-based payment detection system** that automatically monitors blockchain transactions to detect when payments are made to your requests. This system works across multiple blockchains and handles various payment scenarios with zero configuration required.
 
 ## How It Works
 
@@ -21,13 +25,13 @@
 
 ### 1. Payment Reference Generation
 
 When you create a payment request, the API automatically generates a unique **payment reference** — a 16-character identifier that acts as a fingerprint for your request. This reference is what connects blockchain transactions back to your specific request.
 
 **Example:** `0x1234567890abcdef`
 
 ### 2. Blockchain Monitoring
 
 The API continuously monitors supported blockchains using subgraphs that scan for transactions containing payment references. This happens automatically in the background with no action required from you.
 
 **Monitoring includes:**
 - Real-time transaction scanning
@@ -55,20 +59,20 @@
 
 Payment detection works across all Request Network supported chains:
 
 ### Mainnet Networks
 - Ethereum, Polygon (Matic), Arbitrum One, Optimism, Base
 - Gnosis Chain, BSC, Fantom, Avalanche, Celo
 
 ### Testnet Networks
 - Sepolia, Base Sepolia, Arbitrum Sepolia, Optimism Sepolia
 
 ## Crosschain Payment Detection
 
 All crosschain payments using the Request Network API use the **ERC-20 Fee Proxy contract** as the final payment leg, ensuring payment detection works seamlessly across chains.
 
 **How it works:**
 1. Payer initiates payment on source chain (e.g., Polygon)
 2. Crosschain bridge transfers funds to destination chain (e.g., Base)
 3. Final payment uses ERC-20 Fee Proxy with payment reference
 4. Payment detection system identifies the transaction
 5. Request status updated automatically
@@ -79,7 +83,7 @@
 
 <CardGroup cols={2}>
   <Card title="Payment Confirmed" icon="circle-check">
     Full payment received and confirmed on blockchain
   </Card>
 
   <Card title="Payment Partial" icon="circle-half-stroke">
@@ -113,7 +117,7 @@
   </Card>
 
   <Card title="Reliable Infrastructure" icon="shield-check">
     Built on proven blockchain indexing infrastructure
   </Card>
 </CardGroup>
 

api-features/payment-types-overview.mdx

@@ -3,6 +3,10 @@ title: "Payment Types Overview"
 description: "Understanding Invoice-first vs Payment-first workflows and direct payment types"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Request Network supports two primary payment workflows and multiple payment types to accommodate different business needs.

api-features/platform-fees.mdx

@@ -1,8 +1,12 @@
 ---
 title: "Platform Fees"
 description: "Collect platform fees automatically from payments using feePercentage and feeAddress"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Platform fees enable service providers to collect their own fees from payment requests. The Request Network API supports percentage-based fees that are automatically calculated and collected during payment.
@@ -37,7 +41,7 @@
 </ParamField>
 
 <ParamField body="feeAddress" type="string">
   Ethereum address to receive the platform fee
 </ParamField>
 
 ## Implementation
@@ -129,9 +133,9 @@
 
 Fee amounts are included in payment responses and can be queried for complete transparency:
 
 - Payment calldata includes calculated fee amount
 - Payment status includes fee breakdown
 - Fee amounts shown in both crypto and USD equivalents (where applicable)
 
 ## Important Notes
 
@@ -146,7 +150,7 @@
 <Warning>
 **Fee Address Validation**
 
 Ensure the `feeAddress` is a valid Ethereum address that you control. Fees are sent automatically and cannot be recovered if sent to an incorrect address.
 </Warning>
 
 ## What's Next?

api-features/query-payments.mdx

@@ -3,6 +3,10 @@
 description: "Advanced payment search and filtering with the GET /payments endpoint"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 The GET /payments endpoint provides comprehensive payment search and filtering capabilities, enabling detailed payment history analysis and transaction monitoring.
@@ -53,22 +57,22 @@
 
 <CardGroup cols={2}>
   <Card title="Single Network" icon="link">
     Payments on specific blockchain
   </Card>
 
   <Card title="Multi-Network" icon="network-wired">
     Crosschain payment search
   </Card>
 </CardGroup>
 
 ### Supported Networks
 Filter payments across Ethereum, Polygon, Arbitrum, BSC, and other supported networks.
 
 ## Response Data
 
 ### Payment Information
 - **Basic Details:** Amount, currency, timestamp
 - **Network Data:** Blockchain, transaction hash, block number
 - **Participants:** Payer and payee addresses
 - **Status:** Confirmation state and payment completion
 

api-features/query-requests.mdx

@@ -3,6 +3,10 @@
 description: "Request status monitoring, lifecycle management, and information retrieval"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Query requests provides comprehensive request status monitoring and information retrieval, enabling real-time tracking of payment requests throughout their lifecycle.
@@ -33,7 +37,7 @@
 1. **Identify:** Use request ID for lookup
 2. **Retrieve:** Get current request information
 3. **Analyze:** Check payment status and history
 4. **Update:** Reflect latest blockchain state
 
 ## Status Types
 
@@ -66,7 +70,7 @@
 - **Basic Details:** Amount, currency, participants
 - **Payment History:** Transaction details and confirmations
 - **Status Timeline:** Creation, updates, completion dates
 - **Network Data:** Blockchain and transaction information
 
 ## Real-time Monitoring
 

api-features/recurring-payments.mdx

@@ -3,6 +3,10 @@ title: "Recurring Payments"
 description: "Automated payment schedules for subscriptions and recurring billing"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Recurring payments enable automated payment collection on predefined schedules, supporting subscription services, installment plans, and regular business expenses.

api-features/standard-payments.mdx

@@ -3,13 +3,17 @@
 description: "Simple crypto-to-crypto payments using native currencies and ERC20 tokens"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Overview
 
 Standard payments are the simplest form of crypto transactions - sending tokens directly from one wallet to another without conversion or crosschain routing.
 
 ## Native Currency Payments
 
 Pay using blockchain native currencies like ETH, MATIC, BNB.
 
 **Benefits:**
 - No token approval required
@@ -21,7 +25,7 @@
 Pay using standard tokens like USDC, USDT, DAI.
 
 **Benefits:** 
 - Stable value (stablecoins)
 - Wide acceptance
 - Predictable costs
 
@@ -29,7 +33,7 @@
 
 <CardGroup cols={2}>
   <Card title="Production Networks" icon="globe">
     Ethereum, Polygon, Arbitrum, Base, Optimism, BSC, Avalanche, Fantom
   </Card>
 
   <Card title="500+ Tokens" icon="coins">
@@ -49,7 +53,7 @@
   </Card>
 
   <Card title="Invoicing" href="/use-cases/invoicing">
     Simple crypto invoices
   </Card>
 </CardGroup>
 

api-reference/authentication.mdx

@@ -3,6 +3,10 @@
 description: "API authentication, key management, and security best practices"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Authentication Overview
 
 Request Network API uses API key authentication to secure access to endpoints. This guide covers how to obtain, manage, and use your API keys securely.
@@ -37,7 +41,7 @@
 
   <Card title="Development Keys" icon="code">
     **Development Environment:**
     - Use testnet for development
     - Separate keys for each environment
     - Team access management
     - Testing and debugging tools
@@ -166,7 +170,7 @@
   <Card title="Webhook Limits" icon="webhook">
     **Webhook Rate Limits:**
     - 50 webhook deliveries per minute
     - Exponential backoff for retries
     - Maximum 5 retry attempts
 
     **Applies to:** Webhook delivery endpoints

api-setup/getting-started.mdx

@@ -3,6 +3,10 @@
 description: "Quick setup guide to get your API keys and start building with Request Network"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Welcome to Request Network
 
 Get started with Request Network in just a few minutes. This guide will walk you through setting up your account, obtaining API keys, and making your first API call.
@@ -14,7 +18,7 @@
     Sign up for a free Request Network account at [portal.request.network](https://portal.request.network)
   </Step>
   <Step title="Get API Keys">
     Generate your API keys for both testnet (development) and mainnet (production)
   </Step>
   <Step title="Choose Integration">
     Select your integration approach based on your use case
@@ -32,7 +36,7 @@
   <Card title="Developer Account" icon="code">
     **For Developers:**
     - Free account with generous limits
     - Access to testnet for development
     - API documentation and tools
     - Community support
 
@@ -58,7 +62,7 @@
     1. Log in to Request Portal
     2. Navigate to "API Keys" section
     3. Click "Generate New Key"
     4. Select "Testnet" environment
     5. Name your key (e.g., "Development")
     6. Copy and securely store the key
 
@@ -73,7 +77,7 @@
     **Production Environment:**
     1. Complete account verification
     2. Generate new API key
     3. Select "Mainnet" environment
     4. Configure production settings
     5. Set up monitoring and alerts
 
@@ -157,8 +161,8 @@
   -H "Content-Type: application/json" \
   -d '{
     "currency": "USD",
     "expectedAmount": "100",
     "payeeIdentity": "0x627306090abaB3A6e1400e9345bC60c78a8BEf57",
     "reason": "Test invoice"
   }'
 ```
@@ -309,14 +313,14 @@
   <Accordion title="Authentication Errors">
     **401 Unauthorized:**
     - Verify API key is correct
     - Check environment (testnet vs mainnet)
     - Ensure API key has required permissions
     - Verify Authorization header format
   </Accordion>
 
   <Accordion title="Rate Limiting">
     **429 Too Many Requests:**
     - Implement exponential backoff
     - Check your current rate limits
     - Consider upgrading to higher limits
     - Optimize API call frequency

docs.json

@@ -31,7 +31,7 @@
     "appearance": "dark"
   },
   "banner": {
-    "content": "⚠️ **Beta Docs** – Landing page, Payment Demo, Webhooks, and NEAR docs are ready. Use Cases, API, Resources, SDK, and Release Notes are still being revised. [View stable docs →](https://docs.request.network)",
+    "content": "⚠️ **Beta Docs** – Welcome page, Payment Demo, Webhooks, and NEAR docs are ready. Use Cases, API, Resources, SDK, and Release Notes are still being revised. [View stable docs →](https://docs.request.network)",
     "dismissible": true
   },
   "navigation": {
@@ -66,7 +66,8 @@
             "group": "🔑 API Setup",
             "pages": [
               "api-setup/getting-started",
-              "request-network-api/api-portal-manage-api-keys-and-webhooks"
+              "request-network-api/api-portal-manage-api-keys-and-webhooks",
+              "api-setup/migrate-to-v2"
             ]
           },
           {
@@ -165,7 +166,7 @@
           {
             "group": "🔧 SDK Documentation",
             "pages": [
-              "request-network-api/migrate-to-v2"
+              "sdk-legacy/overview"
             ]
           }
         ]

faq.mdx

@@ -3,13 +3,18 @@
 description: "Frequently Asked Questions and Common Misconceptions"
 
 ---
+
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 <Info>
 If your question is not answered below, please consider posting it to the [Request Network Discussions](https://github.com/orgs/RequestNetwork/discussions) page on Github.
 </Info>
 
 <AccordionGroup>
   <Accordion title="Is Request Network a blockchain, smart contract platform, or L2 scaling solution?">
     No. Request Network is not a blockchain, smart contract platform, or scaling solution. Rather, it's a protocol for storing payment requests, facilitating onchain payments, and reconciling those payments with the requests. It stores payment requests in [IPFS](https://www.ipfs.com/) and CID hashes on [Gnosis Chain](https://www.gnosis.io/). It uses [The Graph](https://thegraph.com/) for onchain event indexing. It processes payments across a variety of [supported payment chains](https://docs.request.network/get-started/supported-chains).
   </Accordion>
 
   <Accordion title="What is the difference between Request Network and Request Finance?">
@@ -21,7 +26,7 @@
 
     To help builders get started quickly, the Request Network Foundation operates [Request Node Gateways](https://docs.request.network/get-started/request-node-gateways) that are free for anyone to use. These gateways offer endpoints for creating and retrieving requests.
 
     Requests created on Gnosis Chain are "real" and will exist forever. Requests created on Sepolia are "test" requests and will exist only as long as Sepolia continues to operate.
   </Accordion>
 
   <Accordion title="Is the address that creates a request the same address that receives the payment?">
@@ -33,7 +38,7 @@
   </Accordion>
 
   <Accordion title="Are requests in Request Network stored fully onchain?">
     No. Request Network is a hybrid onchain/offchain protocol storing the majority of request contents in IPFS. Only the content-addressable ID (CID) is stored onchain, on Gnosis Chain.
   </Accordion>
 
   <Accordion title="Can I make a payment before creating a request?">
@@ -57,7 +62,7 @@
   </Accordion>
 
   <Accordion title="Can a Request Node modify a request's contents before persisting it to IPFS and onchain?">
     No. A Request Node cannot change a request's contents before persisting it to IPFS and onchain because doing so would invalidate the signature. This is true for private, encrypted requests as well. The Request Node cannot forge the end-user's signature.
   </Accordion>
 
   <Accordion title="Can I create a request via the Request Network SDK without using a Request Node?">
@@ -98,7 +103,7 @@
   <Accordion title="Does Request Network support crosschain payments where the payer sends funds on one chain and the payee receives funds on a different chain?">
     Yes, via the **Request Network API only**. Crosschain payments are not supported by the Request Network SDK or protocol directly. When using the API, payers can fund requests using assets on different chains and tokens, and the payee receives the requested asset on the request's chain. For example, you can pay a USDC-on-Base request using USDT from Optimism. 
 
     See <Card title="Crosschain Payments" icon="link" href="/api-features/crosschain-payments">Learn how to implement crosschain payment flows</Card> for implementation details.
   </Accordion>
 
   <Accordion title="Does Request Network support private requests?">
@@ -109,7 +114,7 @@
   </Accordion>
 
   <Accordion title="Does Request Network support private payments?">
     Yes. See [Hinkal Private Payments](https://docs.request.network/advanced/request-network-sdk/sdk-guides/payment/hinkal-private-payments)
   </Accordion>
 
   <Accordion title="Can I create a request via a smart contract call?">

glossary.mdx

@@ -1,6 +1,11 @@
 ---
 title: "Glossary"
 ---
+
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Parties of a Request
 
 ### Payee Identity
@@ -45,7 +50,7 @@
 
 ### Confirmed/Pending action
 
 Request relies on other blockchain technologies to ensure data immutability. Most blockchains don't offer transaction instant finality. This means that when performing an action on the request, this action can't directly be confirmed as effective.
 
 As long as the action hasn't persisted and is not confirmed, the action is marked as "pending". The "pending" state helps have a fast response and a good user experience. Until the request is Confirmed, it should not be relied upon.
 
@@ -103,7 +108,7 @@
 
 ### Conversion Payment
 
 A "conversion" request is denominated in one currency but paid in another currency. This is facilitated by on-chain price feeds provided by oracles. The typical use case is to denominate a request in fiat like USD and pay the request in stablecoins like USDC or DAI. For details see [Conversion Payment](https://docs.request.network/advanced/request-network-sdk/sdk-guides/payment/conversion-request)
 
 ### Swap-to-pay Payment
 
@@ -121,31 +126,31 @@
 
 ### Request Node
 
 Request Nodes are HTTP servers exposing an API that allows the Request Client to communicate with the Request Protocol. These servers abstract the complexity of IPFS and Ethereum used by the Request Protocol.
 
 ### Request Protocol
 
 The Request Protocol is the underlying protocol that powers Request. It defines how requests are stored on a distributed ledger and how to interpret actions performed on them.
 
 ## Blockchain, Cryptography
 
 ### Confirmation
 
 Confirmation means that the network has verified the blockchain transaction. This happens through a process known as mining in a proof-of-work system (e.g., Bitcoin). Once a transaction is confirmed, it cannot be reversed.
 
 ### Ether
 
 Ether is the native token of the Ethereum blockchain, which is used to pay for transaction fees, block proposer rewards, and other services on the network.
 
 ### IPFS
 
 The Inter-Planetary File System (IPFS) is a protocol and a peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content-addressing to uniquely identify each file in a global namespace connecting all computing devices.
 
 The Request Protocol uses IPFS to ensure data accessibility.
 
 ### Multi-signature
 
 Multi-signature (multisig) wallets allow multiple parties to require more than one key to authorize a transaction. The needed number of signatures is agreed upon at the creation of the wallet. Multi-signature addresses have a much greater resistance to theft.
 
 ### Private Key
 

release-notes/easy-invoice.mdx

@@ -3,6 +3,10 @@
 description: "Track updates, new features, and improvements to EasyInvoice, the no-code invoicing solution"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 # EasyInvoice Release Notes
 
 This page documents all updates to EasyInvoice, including new features, UI improvements, integrations, and bug fixes.
@@ -79,9 +83,9 @@
 
 ### 🎉 New Features
 
 - **Request Network Integration**: Native support for cryptocurrency payments
 - **Smart Contract Invoices**: Blockchain-verified invoice creation
 - **Multi-chain Support**: Accept payments on Ethereum, Polygon, and more
 - **DeFi Integrations**: Connect with popular DeFi protocols
 
 ### 🚀 Improvements
@@ -119,7 +123,7 @@
 </Card>
 
 <Card title="Payment Processing" icon="credit-card">
   Accept payments via crypto (Request Network), credit cards (Stripe), and bank transfers
 </Card>
 
 <Card title="Client Management" icon="users">
@@ -134,9 +138,9 @@
 ### Integration Ecosystem
 
 - **Payment Processors**: Stripe, PayPal, Request Network
 - **Accounting Software**: QuickBooks, Xero, FreshBooks
 - **E-commerce**: Shopify, WooCommerce, Magento
 - **CRM Systems**: HubSpot, Salesforce, Pipedrive
 
 ## Upcoming Features
 

release-notes/index.mdx

@@ -3,6 +3,10 @@ title: "Release Notes"
 description: "Stay up to date with the latest updates and improvements to Request Network products"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 # Release Notes
 
 Stay informed about the latest features, improvements, and bug fixes across all Request Network products. Our release notes provide detailed information about what's new and what's changed in each version.

release-notes/request-api.mdx

@@ -3,6 +3,10 @@
 description: "Track updates, new features, and changes to the Request Network API"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 # Request API Release Notes
 
 This page documents all updates to the Request Network API, including new features, improvements, bug fixes, and breaking changes.
@@ -46,7 +50,7 @@
 
 - **Security**: Enhanced API key validation and rotation capabilities
 - **Monitoring**: Improved request tracing for better debugging
 - **Webhooks**: Retry mechanism with exponential backoff for failed deliveries
 
 ### 🐛 Bug Fixes
 
@@ -62,7 +66,7 @@
 
 ### 🎉 New Features
 
 - **Multi-chain Support**: Native support for Ethereum, Polygon, Arbitrum, and more
 - **Payment Methods**: Credit card payments via Stripe integration
 - **Request Templates**: Reusable templates for recurring payment scenarios
 - **Advanced Webhooks**: Configurable event filtering and custom headers
@@ -71,7 +75,7 @@
 
 - **RESTful Design**: Complete API redesign following REST principles
 - **OpenAPI Specification**: Comprehensive API documentation with interactive examples
 - **SDK Support**: Official SDKs for JavaScript, Python, and PHP
 - **Performance**: 10x improvement in request processing speed
 
 ### ⚠️ Breaking Changes
@@ -86,7 +90,7 @@
 - **Field Names**: Several field names have been updated for consistency
 
 **Migration Resources:**
-- [Migration Guide](/request-network-api/migrate-to-v2)
+- [Migration Guide](/api-setup/migrate-to-v2)
 - [V1 to V2 Comparison Tool](https://portal.request.network/migration)
 - [Support Channel](https://request.network/discord) for migration assistance
 
@@ -127,7 +131,7 @@
 - **GraphQL API**: Alternative query interface for complex data retrieval
 - **Batch Operations**: Bulk operations for high-volume use cases
 - **Advanced Analytics**: Detailed payment and request analytics
 - **Mobile SDKs**: Native iOS and Android SDK support
 
 <Tip>
 Follow our [GitHub repository](https://github.com/RequestNetwork/request-api) to track development progress and provide feedback on upcoming features.

request-network-api/api-portal-manage-api-keys-and-webhooks.mdx

@@ -3,6 +3,10 @@ title: "API Portal: Manage API Keys and Webhooks"
 description: "An app for managing Request Network API keys and webhooks."
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 <Frame>
 ![API Portal Screenshot](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-e66c8fd31d32271aa1fa5f42ba24d2052d598bdf%252FScreenshot%2520from%25202025-02-13%252016-25-12.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f54d1873&sv=2)
 </Frame>

request-network-api/create-and-pay-requests.mdx

@@ -4,6 +4,10 @@
 description: "The Request Network API provides an interface for creating and paying requests within your application."
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 <Info>
 **Talk to an expert**
 
@@ -15,7 +19,7 @@
 At its core, the Request Network API empowers you to:
 
 - **Create Requests:** Define payment requests with information such as payee, payer (optional), amount, currency, and recurrence (optional).
 - **Facilitate Payments:** Return transaction calldata, ready to be signed by end-users and sent to the blockchain for secure and transparent value transfer.
 - **Deliver Webhook Notifications:** Receive instant updates on payment status changes, enabling your application to react dynamically to completed transactions.
 - **Fee Collection:** When paying a request, you can specify a fee percentage (between 0 and 100) and a fee address, which will add the fee on top of the payment amount - meaning the payer will pay the original amount plus the fee percentage, with the fee portion being sent to the specified fee address.
 - **Partial Payment Support:** Pay a portion of a request instead of the full amount at once. This unlocks powerful use cases such as:

request-network-api/easyinvoice-api-demo-app.mdx

@@ -3,7 +3,11 @@
 description: "An app for creating and paying requests using the Request Network API."
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 EasyInvoice is a web application built with Next.js that allows users to create and manage invoices, and accept crypto payments via the Request Network API. It mimics Web2 apps in its functionalities, providing a user-friendly experience with Google login and real-time updates.
 
 <Info>
 **Talk to an expert**
@@ -20,7 +24,7 @@
 
 ### Overall Supported Currencies and Chains
 
 15 stablecoins: USDC/USDT/DAI on 5 chains (Ethereum, Polygon, Arbitrum One, Base, OP Mainnet) + 4 testnet tokens on Sepolia + USD fiat for Conversion and Crypto-to-fiat payments.
 
 ### **Invoice Creation**
 
@@ -45,20 +49,20 @@
 ### Invoice Payment
 
 - **Invoice Payment:**
   - View invoice details and initiate payment using transaction calldata provided by the Request Network API.
   - Compatible with 80+ different crypto wallets via Reown AppKit
 - **Real-time Updates**: The app receives webhooks from the Request Network API to update the invoice status in real-time.
   <Frame caption="EasyInvoice Invoice Payment Page">
     ![EasyInvoice Invoice Payment
     Page](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-194de7d59aceefc3e98529f6fc470b68179e6a58%252FScreenshot%2520from%25202025-02-14%252001-01-00.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=45dd91bd&sv=2)
   </Frame>
   <br/>
   <Frame caption="EasyInvoice supports 80+ wallets via Reown AppKit">
     ![EasyInvoice supports 80+ wallets via Reown
     AppKit](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-aa6eba6e357825684e36735b00922664fc6c43bd%252Fimage%2520%281%29.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f019f5c4&sv=2)
   </Frame>
 
 ### Invoice Crosschain Payment
 
 <Frame caption="Crosschain Payment Process">
   ![](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-48739d507550f8489d876ba298ef0ee94cc5ede4%252FScreenshot%25202025-04-01%2520at%25204.07.30%25E2%2580%25AFPM.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e1eaea42&sv=2)
@@ -76,9 +80,9 @@
   ></iframe>
 </Frame>
 
 #### Crosschain Payment Supported Currencies
 
 For Crosschain (and Samechain) Payments, EasyInvoice supports 12 stablecoins: USDC/USDT/DAI on 4 chains (Ethereum, Arbitrum One, Base, OP Mainnet)
 
 ### Crypto-to-fiat Payment
 
@@ -97,7 +101,7 @@
 
 #### Crypto-to-fiat Payment Supported Currencies
 
 For Crypto-to-fiat Payments, EasyInvoice supports USDC on Sepolia.
 
 ### Batch Pay Invoices
 
@@ -150,7 +154,7 @@
 
 ### InvoiceMe Link
 
 - **InvoiceMe Link**: Prompt clients to send you an invoice prefilled with your name and email address.
   <Frame caption="Create InvoiceMe Link page">
     ![Create InvoiceMe Link
     page](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-633e8cd81e5cfbf71d0c911a31be57b15429b0c6%252Fimage9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=34532bc2&sv=2)

resources/community.mdx

@@ -3,6 +3,10 @@
 description: "Join the Request Network community, get support, and stay updated with the latest developments"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 ## Request Network Community
 
 Connect with developers, integrators, and the Request Network team across our community channels. Get help, share your projects, and stay updated with the latest developments.
@@ -233,9 +237,9 @@
 ### Conference Presence
 
 **Industry Events:**
 - ETHGlobal events and hackathons
 - Blockchain developer conferences
 - Fintech and payments industry events
 - Web3 developer workshops and meetups
 
 ## Community Showcase

resources/lifecycle-of-a-request.mdx

@@ -3,6 +3,10 @@
 description: "The typical lifecycle of a request is as follows:"
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 <Frame caption="Typical Lifecycle of a Request">
 ![Typical Lifecycle of a Request](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-bb17b9b51fa3361ad54d1ac2185323f707ac8766%252FLifecycle%2520of%2520a%2520Request.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b63df9bb&sv=2)
 </Frame>
@@ -14,7 +18,7 @@
 - The request is persisted in IPFS.
 - The IPFS Content-addressable ID (CID) is stored in a smart contract on Gnosis chain
 <Info>
 Requests are *created* by storing their CIDs on Gnosis, but this doesn't mean *payment* must occur on Gnosis. *Payment* can occur on any of the supported chains including 20+ EVM-compatible chains or NEAR.
 </Info>
 
 ## Update a request
@@ -25,18 +29,18 @@
 
 ## Pay a request
 
 - The payer derives a paymentReference from the request contents.
 - The payer calls a function on the payment network smart contract, passing in the token address, to address, amount, and paymentReference.
 - An event is emitted containing the token address, to address, amount, and paymentReference.
 <Info>
 Most requests are "reference-based" meaning that a paymentReference derived from the request contents is logged on-chain via a smart contract that emits an event. Nothing gets written back to IPFS when paying a "reference-based" request.
 
 The exception is when paying a "declarative" request, in which case, data *is* written back to IPFS. This includes when the payer declares that the payment was sent and the payee declares that the payment was received.
 </Info>
 ## Retrieve a request / Detect a payment
 
 - The event is indexed by the payments subgraph
 - An app can retrieve the request contents from IPFS and calculate the balance based on events from the payments subgraph.
 <Info>
 The request balance is calculated by adding up all the on-chain payment events with the same paymentReference. Partial payments are possible.
 </Info>

resources/request-scan.mdx

@@ -3,6 +3,10 @@
 description: "An explorer app for viewing requests, payments, and addresses in Request Network."
 ---
 
+<Warning>
+**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
+</Warning>
+
 <Frame caption="Request Scan Landing Page">
   ![Request Scan Landing
   Page](https://docs.request.network/~gitbook/image?url=https%3A%2F%2F1914277788-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fei6UAiSK3iAAi0mFH667%252Fuploads%252Fgit-blob-50112fc2716ed4df557c846c8b372bf0b34e1b0b%252FScreenshot%25202024-09-05%2520at%252015.23.45.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9d44768f&sv=2)
@@ -22,7 +26,7 @@
 - **Accountants:** Audit and verify financial data on the request network.
 - **Developers:** Easily access Request Network data for troubleshooting your applications.
 - **Analysts:** Gain deep insights into network activity and trends.
 - **Researchers:** Conduct in-depth studies on blockchain data.
 - **Enthusiasts:** Stay informed about the latest happenings on the Request Network.
 
 ## Usage
@@ -32,7 +36,7 @@
 - **Search Bar:** Located at the top, allows you to search for specific requests or addresses.
 - **Dashboard:** Provides an overview of network statistics and recent activity.
 - **Requests:** View a list of recent requests with details like payee, payer, amount, and timestamp.
 - **Payments:** View a list of recent payments with details like blockchain transactions, amounts, fees, and timestamps.
 - **Address:** View information about individual addresses, including their requests and payments.
 - **Request:** View information about individual requests, including their details and table with actions and payments.