lightsparkdev · jklein24 · May 27, 2026 · May 27, 2026 · greptile-apps · May 27, 2026
diff --git a/.claude/skills/grid-api/SKILL.md b/.claude/skills/grid-api/SKILL.md
@@ -24,7 +24,7 @@ allowed-tools:
 Assist users with global payment operations via the Grid API. Core capabilities:
 
 1. **Execute API Operations** - Use `curl` to interact with the Grid API directly
-2. **Answer Documentation Questions** - Fetch docs from <https://grid.lightspark.com/llms.txt> or the OpenAPI spec (<https://raw.githubusercontent.com/lightsparkdev/grid-api/refs/heads/main/openapi.yaml>)
+2. **Answer Documentation Questions** - Fetch docs from <https://docs.lightspark.com/llms.txt> or the OpenAPI spec (<https://raw.githubusercontent.com/lightsparkdev/grid-api/refs/heads/main/openapi.yaml>)
 3. **Guide Payment Workflows** - Help users send payments to bank accounts, UMA addresses, and crypto wallets
 
 ## Embedded Wallet Offramp (USDB → USD bank)
@@ -99,9 +99,9 @@ export GRID_BASE_URL=$(jq -r '.baseUrl // "https://api.lightspark.com/grid/2025-
 
 For questions not covered by this skill's reference files, fetch additional information from the web:
 
-- **LLM-optimized docs**: Fetch `https://grid.lightspark.com/llms.txt` for a concise overview of the Grid API, or `https://grid.lightspark.com/llms-full.txt` for comprehensive documentation
+- **LLM-optimized docs**: Fetch `https://docs.lightspark.com/llms.txt` for a concise overview of the Grid API, or `https://docs.lightspark.com/llms-full.txt` for comprehensive documentation
 - **OpenAPI Spec**: Fetch `https://raw.githubusercontent.com/lightsparkdev/grid-api/refs/heads/main/openapi.yaml` for the full API schema with request/response definitions
-- **Published docs**: Browse `https://grid.lightspark.com` for guides, tutorials, and API reference. Any page can use the `.md` suffix for a more agent-readable format.
+- **Published docs**: Browse `https://docs.lightspark.com` for guides, tutorials, and API reference. Any page can use the `.md` suffix for a more agent-readable format.
 
 ## Making API Calls
 

diff --git a/.gitignore b/.gitignore
@@ -57,3 +57,8 @@ scripts/export-icons.js
 
 # Superset
 .superset/
+
+# Claude Code scratch — never commit
+.claude/worktrees/
+.claude/scheduled_tasks.lock
+error-audit/
diff --git a/.stainless/stainless.yml b/.stainless/stainless.yml
@@ -10,7 +10,7 @@ organization:
   # and headings.
   name: Lightspark Grid
   # Link to your API documentation.
-  docs: 'grid.lightspark.com'
+  docs: 'docs.lightspark.com'
   # Contact email for bug reports, questions, and support requests.
   contact: support@lightspark.com
 

diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 Grid is an API that enables modern financial institutions to easily send and receive global payments. One API to send, receive, and settle value globally—fiat, stablecoins, or Bitcoin. Always real time, always low cost, built on an open network.
 
-See the full documentation at <https://grid.lightspark.com/>.
+See the full documentation at <https://docs.lightspark.com/>.
 
 ## Overview
 

diff --git a/components/grid-visualizer/CLAUDE.md b/components/grid-visualizer/CLAUDE.md
@@ -14,7 +14,7 @@ Grid Visualizer is an interactive tool that helps integrators understand and get
 
 ## Entry Points
 
-- **Docs site**: grid.lightspark.com
+- **Docs site**: docs.lightspark.com
 - **Marketing site**: lightspark.com/grid
 - **Direct links** shared in sales conversations
 - Currently deployed at: https://grid-flow-builder.vercel.app/

diff --git a/components/grid-visualizer/next.config.mjs b/components/grid-visualizer/next.config.mjs
@@ -26,7 +26,7 @@ const nextConfig = {
         headers: [
           {
             key: 'Content-Security-Policy',
-            value: "frame-ancestors 'self' https://grid.lightspark.com https://*.lightspark.com http://localhost:*",
+            value: "frame-ancestors 'self' https://docs.lightspark.com https://*.lightspark.com http://localhost:*",
           },
         ],
       },

diff --git a/components/grid-visualizer/src/components/Footer/Footer.tsx b/components/grid-visualizer/src/components/Footer/Footer.tsx
@@ -43,7 +43,7 @@ export function Footer({ theme, setTheme }: FooterProps) {
       </button>
 
       <div className={styles.trailing}>
-          <a href="https://grid.lightspark.com" className={styles.link} target="_blank" rel="noopener noreferrer">
+          <a href="https://docs.lightspark.com" className={styles.link} target="_blank" rel="noopener noreferrer">
             View docs
           </a>
           <a

diff --git a/mintlify/global-p2p/getting-started/platform-configuration.mdx b/mintlify/global-p2p/getting-started/platform-configuration.mdx
@@ -17,7 +17,7 @@ To send and receive using UMA with your own domain (e.g., `$alice@yourdomain.com
 2. Proxy inbound UMA requests to {topLevelProductName}
 3. Define supported currencies and, if you are a regulated institution, the counterparty information you require
 
-If you do not configure an UMA domain, Grid will use the default domain `grid.lightspark.com`.
+If you do not configure an UMA domain, Grid will use the default domain `docs.lightspark.com`.
 
 <Note>You can find more information about the UMA protocol and end user experience at [https://uma.me](https://uma.me).</Note>
 
@@ -30,9 +30,9 @@ Set up proxying so UMA‑related requests are forwarded to your assigned `proxyU
 
 - UMA domain determines the address format (e.g., `$alice@yourdomain.com`)
 - Proxy the following paths to `{proxyUmaSubdomain}`:
-  - `https://<umaDomain>/.well-known/lnurlp/*` -> `https://<proxyUmaSubdomain>.grid.lightspark.com/.well-known/lnurlp/*`
-  - `https://<umaDomain>/.well-known/lnurlpubkey` -> `https://<proxyUmaSubdomain>.grid.lightspark.com/.well-known/lnurlpubkey`
-  - `https://<umaDomain>/.well-known/uma-configuration` -> `https://<proxyUmaSubdomain>.grid.lightspark.com/.well-known/uma-configuration`
+  - `https://<umaDomain>/.well-known/lnurlp/*` -> `https://<proxyUmaSubdomain>.docs.lightspark.com/.well-known/lnurlp/*`
+  - `https://<umaDomain>/.well-known/lnurlpubkey` -> `https://<proxyUmaSubdomain>.docs.lightspark.com/.well-known/lnurlpubkey`
+  - `https://<umaDomain>/.well-known/uma-configuration` -> `https://<proxyUmaSubdomain>.docs.lightspark.com/.well-known/uma-configuration`
 
 Additionally, configure:
 - Supported currencies (min/max, enabled transaction types)

diff --git a/mintlify/openapi.yaml b/mintlify/openapi.yaml
diff --git a/mintlify/platform-overview/building-with-ai.mdx b/mintlify/platform-overview/building-with-ai.mdx
@@ -110,7 +110,7 @@ Start in the sandbox environment to experiment safely. The Skill is great at gen
 Grid provides a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that lets AI agents search Grid's SDK documentation **and** execute Grid API operations directly. Your agentic workflows get full context of the Grid API during implementation and can run quotes, transfers, customer onboarding, and other operations end-to-end.
 
 ```text
-https://mcp.grid.lightspark.com/
+https://mcp.docs.lightspark.com/
 ```
 
 The MCP server exposes two tools:
@@ -137,7 +137,7 @@ The MCP server requires Grid API credentials. In the [Grid dashboard](https://ap
     "mcpServers": {
       "grid_mcp": {
         "type": "http",
-        "url": "https://mcp.grid.lightspark.com/",
+        "url": "https://mcp.docs.lightspark.com/",
         "headers": {
           "x-grid-client-id": "{client id}",
           "x-grid-client-secret": "{client secret}"
@@ -159,7 +159,7 @@ The MCP server requires Grid API credentials. In the [Grid dashboard](https://ap
         "args": [
           "-y",
           "mcp-remote",
-          "https://mcp.grid.lightspark.com/",
+          "https://mcp.docs.lightspark.com/",
           "--header",
           "x-grid-client-id: {client id}",
           "--header",
@@ -180,7 +180,7 @@ The MCP server requires Grid API credentials. In the [Grid dashboard](https://ap
   {
     "mcpServers": {
       "grid_mcp": {
-        "url": "https://mcp.grid.lightspark.com/",
+        "url": "https://mcp.docs.lightspark.com/",
         "headers": {
           "x-grid-client-id": "{client id}",
           "x-grid-client-secret": "{client secret}"
@@ -194,7 +194,7 @@ The MCP server requires Grid API credentials. In the [Grid dashboard](https://ap
 <Tab title="ChatGPT and others">
   Any client that supports MCP's streamable HTTP transport (ChatGPT, Windsurf, Zed, Cline, and others) can connect using the same URL and headers:
 
-  - **URL:** `https://mcp.grid.lightspark.com/`
+  - **URL:** `https://mcp.docs.lightspark.com/`
   - **Headers:** `x-grid-client-id: {client id}` and `x-grid-client-secret: {client secret}`
 
   For clients that don't yet support HTTP-transport MCP servers natively, use [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) as a bridge — see the Claude desktop app tab for an example.

diff --git a/mintlify/snippets/platform-configuration-uma.mdx b/mintlify/snippets/platform-configuration-uma.mdx
@@ -121,9 +121,9 @@ Requirements for a valid UMA domain:
 - Must be a valid domain name format
 - Should be a domain that you control
 - Must proxy incoming requests to the Grid API as follows:
-  - `https://<umaDomain>/.well-known/lnurlp/*` -> `https://<proxyUmaSubdomain>.grid.lightspark.com/.well-known/lnurlp/*`
-  - `https://<umaDomain>/.well-known/lnurlpubkey` -> `https://<proxyUmaSubdomain>.grid.lightspark.com/.well-known/lnurlpubkey`
-  - `https://<umaDomain>/.well-known/uma-configuration` -> `https://<proxyUmaSubdomain>.grid.lightspark.com/.well-known/uma-configuration`
+  - `https://<umaDomain>/.well-known/lnurlp/*` -> `https://<proxyUmaSubdomain>.docs.lightspark.com/.well-known/lnurlp/*`
+  - `https://<umaDomain>/.well-known/lnurlpubkey` -> `https://<proxyUmaSubdomain>.docs.lightspark.com/.well-known/lnurlpubkey`
+  - `https://<umaDomain>/.well-known/uma-configuration` -> `https://<proxyUmaSubdomain>.docs.lightspark.com/.well-known/uma-configuration`
 
 ### Webhook Endpoint
 

diff --git a/openapi.yaml b/openapi.yaml
diff --git a/openapi/components/schemas/quotes/RealtimeFundingQuoteSource.yaml b/openapi/components/schemas/quotes/RealtimeFundingQuoteSource.yaml
@@ -20,7 +20,7 @@ allOf:
         type: string
         description: >-
           Currency code for the funding source. See
-          [Supported Currencies](https://grid.lightspark.com/platform-overview/core-concepts/currencies-and-rails)
+          [Supported Currencies](https://docs.lightspark.com/platform-overview/core-concepts/currencies-and-rails)
           for the full list of supported fiat and crypto currencies.
         example: USD
       cryptoNetwork:

diff --git a/openapi/components/schemas/quotes/UmaAddressDestination.yaml b/openapi/components/schemas/quotes/UmaAddressDestination.yaml
@@ -18,7 +18,7 @@ allOf:
         type: string
         description: >-
           Currency code for the destination. See
-          [Supported Currencies](https://grid.lightspark.com/platform-overview/core-concepts/currencies-and-rails)
+          [Supported Currencies](https://docs.lightspark.com/platform-overview/core-concepts/currencies-and-rails)
           for the full list of supported fiat and crypto currencies.
         example: EUR
     description: UMA address destination details
diff --git a/openapi/openapi.yaml b/openapi/openapi.yaml
diff --git a/scripts/README.md b/scripts/README.md
@@ -8,7 +8,7 @@ are HPKE bundle decrypt and Turnkey API stamp construction, which live in
 `@turnkey/crypto` and `@turnkey/api-key-stamper`).
 
 > **For production integrations**, prefer the official Grid SDKs at
-> <https://grid.lightspark.com>. This README is intended for hands-on
+> <https://docs.lightspark.com>. This README is intended for hands-on
 > tinkering, debugging, and end-to-end validation — it favors curl and
 > the minimal signing helpers over a full SDK stack.