Skip to content

docs: update sandbox access to self-serve via dashboard#315

Merged
pengying merged 3 commits intomainfrom
pengying/self-serve-sandbox-docs
Apr 2, 2026
Merged

docs: update sandbox access to self-serve via dashboard#315
pengying merged 3 commits intomainfrom
pengying/self-serve-sandbox-docs

Conversation

@pengying
Copy link
Copy Markdown
Contributor

@pengying pengying commented Apr 2, 2026

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

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>
@mintlify
Copy link
Copy Markdown

mintlify bot commented Apr 2, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Grid 🟢 Ready View Preview Apr 2, 2026, 1:27 AM

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
grid-flow-builder Ready Ready Preview, Comment Apr 2, 2026 1:38am

Request Review

Copy link
Copy Markdown
Contributor Author

pengying commented Apr 2, 2026

This stack of pull requests is managed by Graphite. Learn more about stacking.

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-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 2, 2026

Greptile Summary

This PR updates 10 documentation files to reflect that Grid Sandbox access is now self-serve via app.lightspark.com, replacing all references to emailing support@lightspark.com or contacting sales. The changes are consistently applied across all relevant MDX files, and a pre-existing typo ("credentialsin") in quickstart.mdx is also fixed. The only notable item is an unrelated CI change adding libsecret-1-dev to the lint workflow, which is a P2 concern about bundling unrelated changes.

Confidence Score: 5/5

  • Safe to merge — all changes are documentation-only with one minor unrelated CI addition.
  • All documentation changes are straightforward, consistent, and accurately reflect the new self-serve sandbox flow. The single P2 finding (bundled CI change) does not affect correctness or safety.
  • .github/workflows/lint.yml — contains an unrelated libsecret-1-dev install step that should be explained or separated.

Important Files Changed

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]
Loading
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>
Copy link
Copy Markdown
Contributor Author

pengying commented Apr 2, 2026

Merge activity

  • Apr 2, 3:05 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Apr 2, 3:06 AM UTC: @pengying merged this pull request with Graphite.

@pengying pengying merged commit c768b01 into main Apr 2, 2026
11 checks passed
@pengying pengying deleted the pengying/self-serve-sandbox-docs branch April 2, 2026 03:06
cache: 'npm'

- name: Install libsecret
run: sudo apt-get update && sudo apt-get install -y libsecret-1-dev
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm what's this for?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you think mint got hacked? thinking about it i don't know why mint would require libsecret

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

claude's saying mint's added a new dependency openid-client which uses keytar.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants