Fix naming inconsistencies: "Link API" → "Link" and "Query API MCP" → "Query MCP"

AGENTS.md

@@ -74,7 +74,7 @@ When answering questions about Emerge:
 
 ## API domains
 
-- Link API: https://link.emergedata.ai
+- Link: https://link.emergedata.ai
 - Query API: https://query.emergedata.ai
 - Dashboard: https://dashboard.emergedata.ai
 

CLAUDE.md

@@ -1,7 +1,7 @@
 # Emerge API Documentation
 
 ## Project overview
-Documentation for Emerge API - a privacy-first API for accessing consented user data. The project includes Link API (consent collection) and Query API (data retrieval).
+Documentation for Emerge API - a privacy-first API for accessing consented user data. The project includes Link (consent collection) and Query API (data retrieval).
 
 ## Technical stack
 - Format: MDX files with YAML frontmatter
@@ -108,7 +108,7 @@ description: Concise summary for SEO/navigation
 ```
 
 ## File organization
-- `/link/*.mdx` - Link API guides (overview, authentication, create-link, callbacks, webhooks)
+- `/link/*.mdx` - Link guides (overview, authentication, create-link, callbacks, webhooks)
 - `/query/*.mdx` - Query guides (overview, pagination, event-categories, data-schema)
 - `/ai/*.mdx` - Ship with MCP docs (overview, mcp-docs-setup, mcp-query-setup, mcp-query-tools, contextual-menu, examples)
 - `/ai-tools/*.mdx` - AI tool-specific setup guides (claude-code, cursor, windsurf) [Note: Directory exists in git but not filesystem - may be template content]

ai/mcp-query-setup.mdx

@@ -3,7 +3,7 @@ title: "MCP Query Setup"
 description: "Connect AI tools to query consented user data via MCP"
 ---
 
-The Query API MCP server gives AI agents (Claude, Cursor, VS Code) secure access to consented user data. Instead of making direct HTTP calls, AI tools use the Model Context Protocol with session-based credentials.
+The Query MCP server gives AI agents (Claude, Cursor, VS Code) secure access to consented user data. Instead of making direct HTTP calls, AI tools use the Model Context Protocol with session-based credentials.
 
 <Note>
 **Different from Docs MCP**: This server queries **user data**. For documentation search, see [Docs MCP Setup](/ai/mcp-docs-setup).
@@ -84,7 +84,7 @@ https://mcp.emergedata.ai/mcp
     2. Go to **Settings** → **Connectors**
     3. Click **Add custom connector**
     4. Enter configuration:
-       - **Name**: Emerge Query API
+       - **Name**: Emerge Query MCP
        - **URL**: `https://mcp.emergedata.ai/mcp`
     5. Add connection parameters:
        ```
@@ -219,7 +219,7 @@ The MCP server exposes 5 tools that map 1:1 to Query API sync endpoints:
 | `get_ads_data` | `/v1/sync/get_ads` | Ad interactions |
 | `get_receipts_data` | `/v1/sync/get_receipts` | Purchase receipts |
 
-See [MCP Query Tools](/ai/mcp-query-tools) for detailed parameter and response documentation.
+See [Query MCP Tools](/ai/mcp-query-tools) for detailed parameter and response documentation.
 
 ## Response Format
 

changelog.mdx

@@ -5,7 +5,7 @@ description: "API updates and documentation changes"
 
 ## v0.0.11 (2026-02-12)
 
-**Link API:**
+**Link:**
 - Updated webhook payload contract to v2 (`sources[]` + `client_id` in payload)
 - Updated webhook headers (`X-Signature`, `X-Webhook-Version: 2.0`, `X-Attempt-Number`, `Idempotency-Key`)
 - Added `client_id` to `GET /consent/status/{uid}` response
@@ -22,7 +22,7 @@ description: "API updates and documentation changes"
 
 ## v0.0.10 (2026-01-28)
 
-**Link API:**
+**Link:**
 - Removed `flow_version` parameter (deprecated)
 - Use `flow_config` for custom branding configurations