Please wait
- -Please wait
- -boolean | This is enabled by default. Set false to persist sessions storage for the user. (This will be replaced with `canClearWebStorage` in an upcoming update) |
-| **`canUseAttestorAuthenticationRequest`** | boolean | Enable the use of authentication request when starting a verification |
-| **`claimCreationType`** | 'standalone' \| 'meChain' | The type of claim creation to use. Defaults to 'standalone'. |
-| **`canAutoSubmit`** | boolean | Whether to automatically submit the proof after generation. Defaults to true. When false, a prompt to submit is shown to the user. |
-| **`isCloseButtonVisible`** | boolean | Whether the close button is visible in the verification screen. Defaults to true. |
diff --git a/content/docs/advance-options/meta.json b/content/docs/advance-options/meta.json
deleted file mode 100644
index 4c5c098..0000000
--- a/content/docs/advance-options/meta.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "title": "Advanced Options",
- "pages": ["attestor-auth", "verification", "overrides","verification-options","verification-status","web-sdk","js-injections"]
-}
\ No newline at end of file
diff --git a/content/docs/advance-options/overrides.mdx b/content/docs/advance-options/overrides.mdx
deleted file mode 100644
index 6c42b3b..0000000
--- a/content/docs/advance-options/overrides.mdx
+++ /dev/null
@@ -1,312 +0,0 @@
----
-title: Overrides
-description: Instructions on how to override the default configuration of Reclaim Protocol's InApp SDKs
----
-
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
-import { Accordion, Accordions } from 'fumadocs-ui/components/accordion';
-
-# Get Started
-
-Many configurations in the InApp SDKs can be overridden. For example, a different attestor can be used, or we can update app info that appears in the verification flow.
-
-boolean | This is enabled by default. Set false to persist sessions storage for the user. (This will be replaced with `canClearWebStorage` in an upcoming update) |
-| **`canUseAttestorAuthenticationRequest`** | boolean | Enable the use of authentication request when starting a verification |
-| **`claimCreationType`** | 'standalone' \| 'meChain' | The type of claim creation to use. Defaults to 'standalone'. |
-| **`canAutoSubmit`** | boolean | Whether to automatically submit the proof after generation. Defaults to true. When false, a prompt to submit is shown to the user. |
-| **`isCloseButtonVisible`** | boolean | Whether the close button is visible in the verification screen. Defaults to true. |
diff --git a/content/docs/advance-options/verification.mdx b/content/docs/advance-options/verification.mdx
deleted file mode 100644
index 5882649..0000000
--- a/content/docs/advance-options/verification.mdx
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: Backend Verification
-description: Learn how to create session and verify with Reclaim Backend SDKs
----
-
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
-
-As best practice, we **strongly** recommend verifying proofs generated from client-side SDKs with a [Reclaim Protocol Backend SDK](http://localhost:3000/backend/installation).
-
-## Step-by-Step Guide
-
-### 1. Install the SDK
-
-Make sure you have installed the SDKs by following the instructions on the [Installation page](./../backend/installation).
-
-### 2. Prepare your variables
-- You will need to have the `APPLICATION_ID` and `APPLICATION_SECRET` from dev.reclaimprotocol.org.
-- You will also need to add providers to your application, keep the `PROVIDER_ID` handy too.
-- The providers you add to the application, will be the providers you will be able to ask the user to generate a proof for.
-- Make sure you add to your [Application from the dev tool](https://dev.reclaimprotocol.org/my-applications/).
-
-### 3. Get request URL from Backend SDK
-
-- Set the `useAppClip` option to `true` when initializing proof request: `ReclaimProofRequest.init`.
-- Get the `request_url` by calling `getRequestUrl` method on proof request object.
-
-```js
-import { ReclaimProofRequest } from '@reclaimprotocol/js-sdk';
-
-app.get('/reclaim/request', async (req: any, res: any) => {
- try {
- const reclaimProofRequest = await ReclaimProofRequest.init(APPLICATION_ID, APPLICATION_SECRET, PROVIDER_ID, { useAppClip: true })
-
- const request_url = await reclaimProofRequest.getRequestUrl()
-
- return res.json({ request_url })
- } catch (error) {
- console.error('Error generating request config:', error)
- return res.status(500).json({ error: 'Failed to generate request config' })
- }
-});
-```
-
-### 4. Generate proof on client mobile
-
-- Your native mobile application should use the `request_url` from the backend and start verification with this url.
-
-Welcome, {user.id}!
-{JSON.stringify(user.userData, null, 2)}
- {JSON.stringify(user.additionalData, null, 2)}
- Welcome, {user.id}!
-{JSON.stringify(user.userData, null, 2)}
- {JSON.stringify(user.additionalData, null, 2)}
-