fix: soften low-level API banners — no deprecation commitment

Replace the "expect to deprecate in the medium term" wording (which
lacked product sign-off and contradicted the GA changelog's "fully
supported") with low-level positioning: use Access Grants for granting
access, and discuss your use case with the Seam team before building
on these APIs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: sybohy

docs/guides/low-level-apis/README.md

@@ -1,13 +1,13 @@
 ---
 description: >-
   Low-level Seam APIs for direct access code and ACS credential management.
-  These APIs are no longer recommended for granting access—use Access Grants.
+  For granting access, use Access Grants instead.
 ---
 
 # Low-Level APIs
 
 {% hint style="warning" %}
-**These APIs are no longer recommended for granting access.** Use [Access Grants](../use-cases/granting-access/README.md)—the default and recommended way to grant access to any physical space, across standalone smart locks and access control systems. New development should not build granting workflows on the APIs in this section; we expect to deprecate them for granting use cases in the medium term.
+**These are low-level APIs.** For granting access, use [Access Grants](../use-cases/granting-access/README.md)—the default and recommended way to grant access to any physical space, across standalone smart locks and access control systems. We don't recommend building on the APIs in this section unless you have discussed your use case with the Seam team at [support@seam.co](mailto:support@seam.co).
 {% endhint %}
 
 The guides in this section cover Seam's low-level credential primitives: managing [access codes](access-codes/README.md) directly on individual devices and managing [ACS credentials](managing-credentials.md) directly within an access control system.

docs/guides/low-level-apis/access-codes/README.md

@@ -7,7 +7,7 @@ description: >-
 # Creating and Managing Smart Lock Access Codes
 
 {% hint style="warning" %}
-**The Access Codes API is no longer recommended for granting access.** Use [Access Grants](../../use-cases/granting-access/README.md)—they grant access to standalone smart locks (via `device_ids`) and access systems through one consistent, future-proof interface, and manage the underlying codes for you. We expect to deprecate direct access code management for granting use cases in the medium term. See [Which API should I use to grant access?](../../use-cases/granting-access/README.md#which-api-should-i-use-to-grant-access) for the few cases where this low-level API is still required.
+**The Access Codes API is a low-level API.** For granting access, use [Access Grants](../../use-cases/granting-access/README.md)—they grant access to standalone smart locks (via `device_ids`) and access systems through one consistent interface, and manage the underlying codes for you. We don't recommend building on this API unless you have discussed your use case with the Seam team at [support@seam.co](mailto:support@seam.co). See [Which API should I use to grant access?](../../use-cases/granting-access/README.md#which-api-should-i-use-to-grant-access) for the few cases where this low-level API is still required.
 {% endhint %}
 
 <figure><img src="../../.gitbook/assets/code_unlock.gif" alt=""><figcaption></figcaption></figure>

docs/guides/low-level-apis/managing-credentials.md

@@ -5,7 +5,7 @@ description: Learn how to manage credentials and assign them to users.
 # Managing Credentials
 
 {% hint style="warning" %}
-**Direct ACS credential management is no longer recommended for granting access.** Use [Access Grants](../use-cases/granting-access/README.md)—they create and manage the underlying credentials for you, across access systems and standalone smart locks alike. We expect to deprecate direct credential creation for granting use cases in the medium term. See [Which API should I use to grant access?](../use-cases/granting-access/README.md#which-api-should-i-use-to-grant-access) for the few cases where this low-level API is still required.
+**This is a low-level API.** For granting access, use [Access Grants](../use-cases/granting-access/README.md)—they create and manage the underlying credentials for you, across access systems and standalone smart locks alike. We don't recommend building on this API unless you have discussed your use case with the Seam team at [support@seam.co](mailto:support@seam.co). See [Which API should I use to grant access?](../use-cases/granting-access/README.md#which-api-should-i-use-to-grant-access) for the few cases where this low-level API is still required.
 {% endhint %}
 
 An ACS generally uses digital means of access to authorize an [ACS user](../capability-guides/access-systems/user-management.md) trying to get through a specific entrance. Examples of credentials include plastic key cards, mobile keys, biometric identifiers, and PIN codes. The electronic nature of these credentials, as well as the fact that access is centralized, enables both the rapid provisioning and rescinding of access and the ability to compile access audit logs.