docs: update sandbox access to self-serve via dashboard#315
Conversation
Grid Sandbox is now self-serve. Replace references to contacting sales/support for sandbox credentials with directions to create an account and generate API keys at app.lightspark.com. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Production environment still requires reaching out to a Lightspark representative. Only sandbox access is self-serve. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Greptile SummaryThis PR updates 10 documentation files to reflect that Grid Sandbox access is now self-serve via app.lightspark.com, replacing all references to emailing Confidence Score: 5/5
|
| Filename | Overview |
|---|---|
| .github/workflows/lint.yml | Adds libsecret-1-dev system dependency install before npm ci — unrelated to the docs-only changes described in the PR. |
| mintlify/global-p2p/quickstart.mdx | Fixes pre-existing "credentialsin" typo and adds dashboard link for self-serve sandbox access. |
| mintlify/payouts-and-b2b/platform-tools/sandbox-testing.mdx | Replaces support email contact with self-serve dashboard instructions for sandbox access. |
| mintlify/rewards/platform-tools/sandbox-testing.mdx | Identical sandbox onboarding update to the payouts-and-b2b sandbox-testing file. |
| mintlify/platform-overview/introduction/faq.mdx | Replaces "Contact Sales" + "Get Sandbox Credentials" steps with self-serve account creation flow. |
| mintlify/snippets/webhooks.mdx | Replaces support email / Slack prompt for public key with a direct link to the dashboard API settings. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Developer] --> B{Sandbox Access}
B -->|Before| C[Email support@lightspark.com]
C --> D[Wait for credentials]
D --> E[Receive sandbox API keys]
B -->|After| F[Go to app.lightspark.com]
F --> G[Create account]
G --> H[Generate sandbox API keys\nfrom dashboard]
E --> I[Set env vars & start building]
H --> I
I --> J[Test integration in Sandbox]
J --> K[Request Production access\nfrom Lightspark contact]
K --> L[Go live]
Prompt To Fix All With AI
This is a comment left during a code review.
Path: .github/workflows/lint.yml
Line: 34-36
Comment:
**Unrelated CI change bundled into docs-only PR**
The `libsecret-1-dev` install step is unrelated to the sandbox self-serve documentation updates described in the PR. `libsecret` is a GNOME keyring library typically required by native Node.js packages like `keytar`. If this was added to fix a CI failure caused by a new npm dependency, it would be clearer to include a brief comment or land it in a separate commit/PR so the change is traceable.
How can I resolve this? If you propose a fix, please make it concise.Reviews (2): Last reviewed commit: "ci: install libsecret for mint openapi-c..." | Re-trigger Greptile
The Mintlify CLI depends on keytar which requires libsecret on Linux. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
| cache: 'npm' | ||
|
|
||
| - name: Install libsecret | ||
| run: sudo apt-get update && sudo apt-get install -y libsecret-1-dev |
There was a problem hiding this comment.
i was getting a CI dependency error https://github.com/lightsparkdev/grid-api/actions/runs/23879181507/job/69628925625#step:6:52
There was a problem hiding this comment.
you think mint got hacked? thinking about it i don't know why mint would require libsecret
There was a problem hiding this comment.
claude's saying mint's added a new dependency openid-client which uses keytar.
There was a problem hiding this comment.
could just remove the mintlify check-openapi since we're already running the redoc lint.
at some point also wanted to create our own lint rules using https://stoplight.io/open-source/spectral

Grid Sandbox is now self-serve. Replace references to contacting
sales/support for sandbox credentials with directions to create an
account and generate API keys at app.lightspark.com.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com