diff --git a/develop-docs/sdk/foundations/client/integrations/feature-flags.mdx b/develop-docs/sdk/foundations/client/integrations/feature-flags.mdx
index 34eb0a2d457ed..e34715cdb1498 100644
--- a/develop-docs/sdk/foundations/client/integrations/feature-flags.mdx
+++ b/develop-docs/sdk/foundations/client/integrations/feature-flags.mdx
@@ -2,12 +2,15 @@
 title: Feature Flags
 description: Guidelines for tracking feature flag evaluations — scope storage, span attributes, the add_feature_flag API, and third-party integrations.
 spec_id: sdk/foundations/client/integrations/feature-flags
-spec_version: 1.0.1
+spec_version: 1.0.2
 spec_status: stable
 spec_depends_on:
   - id: sdk/foundations/client/integrations
     version: ">=1.0.0"
 spec_changelog:
+  - version: 1.0.2
+    date: 2026-07-07
+    summary: Added `clear_feature_flags` scope API
   - version: 1.0.1
     date: 2026-06-05
     summary: Fixed `add_feature_flag` API specifying unsupported feature flag value types
@@ -47,6 +50,14 @@ If an SDK supports feature flags it MUST expose a function `add_feature_flag` wh
 
 </SpecSection>
 
+<SpecSection id="clear-feature-flags" status="stable" since="1.0.2">
+
+### The `clear_feature_flags` API
+
+SDKs **MAY** expose a `clear_feature_flags` function on the scope. When called, it **MUST** remove all feature flag evaluations stored on the current scope. It **MUST NOT** affect feature flags on parent or sibling scopes.
+
+</SpecSection>
+
 <SpecSection id="feature-flag-integrations" status="stable" since="1.0.0">
 
 ### Integrations