Use X Chat for the product; keep Chat API and Chat XDK

tcaldwell-x · tcaldwell-x · commit 0be419f3cf72 · 2026-06-26T20:55:48.000-07:00
Standalone references to Chat as the product are now X Chat.
Chat API and Chat XDK stay as the API and encryption SDK names;
code identifiers (Chat class, paths, event types) are unchanged.
diff --git a/xchat/cryptography-primer.mdx b/xchat/cryptography-primer.mdx
@@ -1,13 +1,13 @@
 ---
 title: Cryptography Primer
 sidebarTitle: Cryptography Primer
-description: Understand the encryption concepts behind Chat without diving into implementation details
-keywords: ["Chat cryptography", "E2EE primer", "encryption basics", "public key encryption", "ECDH", "digital signatures", "conversation keys"]
+description: Understand the encryption concepts behind X Chat without diving into implementation details
+keywords: ["X Chat cryptography", "E2EE primer", "encryption basics", "public key encryption", "ECDH", "digital signatures", "conversation keys"]
 ---
 
 import { Button } from '/snippets/button.mdx';
 
-This primer explains the cryptographic ideas behind Chat at a conceptual level. You do not need this depth to build—the [Chat XDK](/xchat/xchat-xdk) performs encryption, decryption, signing, and key storage for you—but the mental model helps when you design your app or debug behavior.
+This primer explains the cryptographic ideas behind X Chat at a conceptual level. You do not need this depth to build—the [Chat XDK](/xchat/xchat-xdk) performs encryption, decryption, signing, and key storage for you—but the mental model helps when you design your app or debug behavior.
 
 When you are ready to implement, use [Getting Started](/xchat/getting-started) for a full walkthrough and the [API reference](/x-api/chat/get-chat-conversations) in the sidebar for individual routes.
 
@@ -19,7 +19,7 @@ When you are ready to implement, use [Getting Started](/xchat/getting-started) f
 
 ## The big picture
 
-Chat uses a layered encryption system where:
+X Chat uses a layered encryption system where:
 
 1. **Messages** are encrypted with a **conversation key** (fast symmetric encryption)
 2. **Conversation keys** are encrypted to each participant using their **identity public key** (asymmetric key exchange)
@@ -51,7 +51,7 @@ In the product flow, X transports **ciphertext and key envelopes**—not readabl
 
 ## Key types explained
 
-Chat uses three kinds of key material, each with a specific purpose.
+X Chat uses three kinds of key material, each with a specific purpose.
 
 ### 1. Identity keypair
 
@@ -110,7 +110,7 @@ Conversation keys are generated when a conversation is set up or when keys rotat
     The Chat XDK signs the encrypted payload with your signing private key, proving you authored this exact content.
   </Step>
   <Step title="Send to X">
-    Your app sends the encrypted payload and signature to X through the Chat **send message** API. X stores and delivers bytes it cannot read as plaintext.
+    Your app sends the encrypted payload and signature to X through the Chat API **send message** endpoint. X stores and delivers bytes it cannot read as plaintext.
   </Step>
 </Steps>
 
@@ -166,7 +166,7 @@ Your app should:
 
 ## Juicebox: Distributed key storage
 
-Your **private** identity and signing keys must be stored carefully. Chat integrates **Juicebox** so keys can be recovered with a PIN across devices without giving any single server the full secret.
+Your **private** identity and signing keys must be stored carefully. X Chat integrates **Juicebox** so keys can be recovered with a PIN across devices without giving any single server the full secret.
 
 ### The problem with traditional key storage
 
@@ -208,7 +208,7 @@ You do not configure Juicebox servers by hand for the normal path. The Chat XDK
 
 ## Signatures explained
 
-Every Chat message includes a **digital signature** that supports:
+Every X Chat message includes a **digital signature** that supports:
 
 1. **Authenticity** — it was produced with the sender’s signing private key  
 2. **Integrity** — the encrypted content was not modified after signing  
@@ -230,7 +230,7 @@ The Chat XDK signs when you encrypt outbound messages and verifies when you decr
 
 ## Security properties
 
-### What Chat protects against
+### What X Chat protects against
 
 | Threat | Protection |
 |:-------|:-----------|
@@ -240,7 +240,7 @@ The Chat XDK signs when you encrypt outbound messages and verifies when you decr
 | **Trivial sender impersonation** | Valid signatures require the sender’s signing private key |
 | **Single-server key theft (with Juicebox)** | Shares are split across realms and PIN-gated |
 
-### What Chat does **not** protect against
+### What X Chat does **not** protect against
 
 | Threat | Why not |
 |:-------|:--------|
@@ -262,7 +262,7 @@ The Chat XDK signs when you encrypt outbound messages and verifies when you decr
 | **Keypair** | A linked public key and private key |
 | **ECDH / ECIES** | Algorithms used when wrapping conversation keys to identity keys |
 | **ECDSA** | Signature algorithm used for message authorship |
-| **P-256** | Elliptic curve used in Chat (secp256r1) |
+| **P-256** | Elliptic curve used in X Chat (secp256r1) |
 | **Conversation key** | Symmetric key shared by participants in one conversation (versioned over time) |
 | **Secret sharing** | Splitting a secret so multiple pieces are needed to reconstruct it |
 | **Realm** | An independent Juicebox server holding one share of your key material |
diff --git a/xchat/getting-started.mdx b/xchat/getting-started.mdx
@@ -1,13 +1,13 @@
 ---
 title: Getting Started with Chat API
 sidebarTitle: Getting Started
-description: Build end-to-end encrypted Chat messaging with the Chat XDK and X API
-keywords: ["Chat tutorial", "Chat quickstart", "Chat XDK", "encrypted DM", "Python", "TypeScript", "Go", "Rust", "C#", "Java"]
+description: Build end-to-end encrypted X Chat messaging with the Chat XDK and X API
+keywords: ["X Chat tutorial", "X Chat quickstart", "Chat XDK", "encrypted DM", "Python", "TypeScript", "Go", "Rust", "C#", "Java"]
 ---
 
 Send and receive end-to-end encrypted direct messages on X: set up keys, initialize a conversation, send a message, and decrypt inbound traffic.
 
-Chat apps use two pieces together:
+X Chat apps use two pieces together:
 
 | Component | Role |
 |:----------|:-----|
diff --git a/xchat/groups.mdx b/xchat/groups.mdx
@@ -1,11 +1,11 @@
 ---
 title: Group conversations
 sidebarTitle: Groups
-description: Multi-participant Chat conversations, keys, and encrypted metadata
-keywords: ["Chat groups", "group DM", "conversation keys", "group name encryption"]
+description: Multi-participant X Chat conversations, keys, and encrypted metadata
+keywords: ["X Chat groups", "group DM", "conversation keys", "group name encryption"]
 ---
 
-Group chats use the **same encryption model** as 1:1 Chat: one **conversation key** shared by members, wrapped to each member’s **identity public key**, with messages encrypted and signed by the Chat XDK. What changes is **membership**, **how you create the thread**, and often **encrypted title/avatar** fields on the conversation.
+Group chats use the **same encryption model** as 1:1 X Chat: one **conversation key** shared by members, wrapped to each member’s **identity public key**, with messages encrypted and signed by the Chat XDK. What changes is **membership**, **how you create the thread**, and often **encrypted title/avatar** fields on the conversation.
 
 1:1 flows are in [Getting Started](/xchat/getting-started). Endpoint details are under **API reference → Conversations and messages**.
 
diff --git a/xchat/introduction.mdx b/xchat/introduction.mdx
@@ -52,7 +52,7 @@ Grouped under **API reference** in the sidebar, including:
 
 ## Auth notes
 
-Use **OAuth 2.0 user context** with DM-related scopes (`dm.read`, `dm.write`, plus `users.read` / `tweet.read` as required; `media.write` for uploads). Chat activity for a user requires that user’s authorization. Juicebox config for PIN storage is returned on **your** public-key record (`juicebox_config` field)—see Getting Started.
+Use **OAuth 2.0 user context** with DM-related scopes (`dm.read`, `dm.write`, plus `users.read` / `tweet.read` as required; `media.write` for uploads). X Chat activity for a user requires that user’s authorization. Juicebox config for PIN storage is returned on **your** public-key record (`juicebox_config` field)—see Getting Started.
 
 ---
 
diff --git a/xchat/media.mdx b/xchat/media.mdx
@@ -1,15 +1,15 @@
 ---
 title: Media and attachments
 sidebarTitle: Media
-description: Encrypt, upload, send, download, and decrypt images and files in Chat
-keywords: ["Chat media", "encrypted images", "attachments", "encrypt_stream", "media upload"]
+description: Encrypt, upload, send, download, and decrypt images and files in X Chat
+keywords: ["X Chat media", "encrypted images", "attachments", "encrypt_stream", "media upload"]
 ---
 
 Images and other files use the **same conversation key** as text. Encrypt bytes with the Chat XDK (`encrypt_stream` / `decrypt_stream`), upload via **`/2/chat/media/...`** (sidebar **API reference → Media**), then attach **`media_hash_key`** on `encrypt_message`.
 
 Include **`media.write`** with your DM scopes when uploading. Use hyphenated conversation ids in paths (`:` → `-`). Prefer MIME/dimensions from **decrypted** bytes.
 
-This path is **not** the Posts media model (`expansions=attachments.media_keys`, `media.fields=variants`, etc.). Those parameters apply to **Posts**; E2EE Chat blobs are addressed by **`media_hash_key`** and Chat media download.
+This path is **not** the Posts media model (`expansions=attachments.media_keys`, `media.fields=variants`, etc.). Those parameters apply to **Posts**; E2EE X Chat blobs are addressed by **`media_hash_key`** and X Chat media download.
 
 ```mermaid
 flowchart LR
diff --git a/xchat/real-time-events.mdx b/xchat/real-time-events.mdx
@@ -1,18 +1,18 @@
 ---
-title: Real-time Chat Events
+title: Real-time X Chat Events
 sidebarTitle: Real-time events
 description: Receive encrypted chat events via webhooks or the activity stream
 ---
 
-X delivers **`chat.received`**, **`chat.sent`**, and related chat activity with **ciphertext** in the payload. Decrypt with the [Chat XDK](/xchat/xchat-xdk).
+X delivers **`chat.received`**, **`chat.sent`**, and related X Chat activity with **ciphertext** in the payload. Decrypt with the [Chat XDK](/xchat/xchat-xdk).
 
 | Layer | Role |
 |:------|:-----|
 | **Activity API** | `GET /2/activity/stream`; `POST` / `GET` / `PUT` / `DELETE` `/2/activity/subscriptions` (see OpenAPI security per operation) |
 | **Account Activity webhooks** | Optional `/2/account_activity/webhooks/...` subscription routes if you terminate on your own HTTPS URL |
 | **Chat XDK** | `extract_conversation_keys`, `decrypt_event` / `decrypt_events` |
 
-Private chat event types need authorization for the user you monitor. Encrypted Chat file attachments use **`media_hash_key`** and Chat media download—not Post API `expansions=attachments.media_keys` / `media.fields=variants`.
+Private X Chat event types need authorization for the user you monitor. Encrypted X Chat file attachments use **`media_hash_key`** and X Chat media download—not Post API `expansions=attachments.media_keys` / `media.fields=variants`.
 
 ---
 
diff --git a/xchat/troubleshooting.mdx b/xchat/troubleshooting.mdx
@@ -1,11 +1,11 @@
 ---
 title: Troubleshooting
 sidebarTitle: Troubleshooting
-description: Chat encryption and Chat XDK issues
-keywords: ["Chat errors", "Chat XDK", "decryption", "Juicebox", "encryption"]
+description: X Chat encryption and Chat XDK issues
+keywords: ["X Chat errors", "Chat XDK", "decryption", "Juicebox", "encryption"]
 ---
 
-This page covers problems that are **specific to Chat encryption and the Chat XDK**—keys, Juicebox, decrypt/verify, and building encrypted send payloads.
+This page covers problems that are **specific to X Chat encryption and the Chat XDK**—keys, Juicebox, decrypt/verify, and building encrypted send payloads.
 
 For webhooks, OAuth, HTTP status codes, and rate limits, use the general [X API](/x-api/introduction) and [authentication](/fundamentals/authentication/overview) documentation.
 
@@ -169,7 +169,7 @@ They may not have finished onboarding. After they register, load `public_key`, `
 
 ## Building the send payload
 
-These mistakes are specific to Chat encryption (not general HTTP errors):
+These mistakes are specific to X Chat encryption (not general HTTP errors):
 
 | Issue | Fix |
 |:------|:----|
diff --git a/xchat/xchat-xdk.mdx b/xchat/xchat-xdk.mdx
@@ -1,11 +1,11 @@
 ---
 title: Chat XDK Reference
 sidebarTitle: Chat XDK
-description: Encryption SDK for Chat (Python, TypeScript/JS, Rust, Go, C#, Java)
+description: Encryption SDK for X Chat (Python, TypeScript/JS, Rust, Go, C#, Java)
 keywords: ["Chat XDK", "chat-xdk", "encryption SDK", "E2EE SDK"]
 ---
 
-The **Chat XDK** handles key management, encryption, decryption, and signing for Chat. It does **not** call the X HTTP API—pair it with the [Python](/xdks/python/overview) or [TypeScript](/xdks/typescript/overview) **XDK**, or with HTTPS and a user access token.
+The **Chat XDK** handles key management, encryption, decryption, and signing for X Chat. It does **not** call the X HTTP API—pair it with the [Python](/xdks/python/overview) or [TypeScript](/xdks/typescript/overview) **XDK**, or with HTTPS and a user access token.
 
 App walkthrough: [Getting Started](/xchat/getting-started). Sample bots: [chat-xdk/examples](https://github.com/xdevplatform/chat-xdk/tree/main/examples).
 
