docs: drop stale platform-owned rule-based account caveat by bsiaotickchong · Pull Request #1063 · lightsparkdev/grid-api

bsiaotickchong · 2026-09-23T20:42:42Z

Summary

Platform-owned rule-based accounts are now supported: omitting customerId on POST /internal-accounts creates a platform-owned account. Two descriptions still said otherwise.

The customerId field on InternalAccountCreateRequest ended with "Platform-owned rule-based accounts are not available yet, so omitting this is currently rejected." That sentence is removed.
The POST /internal-accounts operation said rule-based accounts are available "for individual customers, and must be enabled for your platform before this endpoint accepts requests". It now says they are available "for a customer or for your platform itself", and the enablement clause is removed.

Changes

openapi/components/schemas/customers/InternalAccountCreateRequest.yaml: sentence removed.
openapi/paths/internal_accounts.yaml: availability wording updated and enablement clause removed.
openapi.yaml and mintlify/openapi.yaml: rebundled with make build.

Test plan

make build: the bundled diff contains only these two description changes.
make lint-openapi: exits 0.

🤖 Generated with Claude Code

Requested by @bsiaotickchong

Original PR: #1062

Platform-owned rule-based accounts are supported, so omitting customerId on POST /internal-accounts is no longer rejected. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

lightspark-bot · 2026-09-23T20:42:59Z

docs: drop stale platform-owned rule-based account caveat #1063 👈 (View in Graphite)
main

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

ls-bolt · 2026-09-23T20:44:54Z

⚡ Revision log — updated in place, latest first.

Revision 3

Removed the "must be enabled for your platform before this endpoint accepts requests" clause from the POST /internal-accounts description, per @bsiaotickchong. Rebundled with make build, and make lint-openapi passes.

Earlier revisions (2)

Revision 2

Updated the POST /internal-accounts description to say rule-based accounts are available "for a customer or for your platform itself" instead of "for individual customers", per Greptile. Rebundled with make build, and make lint-openapi passes.
preview is still failing because Stainless's SDK-preview upload returns 401 (the org migrated to stlc). This PR doesn't cause it.

Revision 1

No code change. The preview failure comes from the Stainless SDK-preview upload returning 401 ("This org has migrated to stlc and is now read-only on the Stainless platform"). Other open PRs fail the same way right now. It is not caused by this one-sentence description edit. Fixing it means migrating the workflow to the new Stainless setup, which is outside this PR.

greptile-apps · 2026-09-23T20:45:25Z

Confidence Score: 4/5

The documentation-only change is safe to merge after the non-blocking endpoint wording inconsistency is corrected.

Findings

Conflicting account availability guidance ▶

Fix with agent prompt

### Issue 1
openapi/components/schemas/customers/InternalAccountCreateRequest.yaml:17
This field now says that omitting `customerId` creates a platform-owned account, but the `POST /internal-accounts` operation still says rule-based accounts are available “for individual customers.” This contradiction can make integrators overlook the newly supported platform-owned flow. Please align the operation description and rebundle the generated contracts.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This PR removes an obsolete caveat from the optional customerId field and regenerates both published OpenAPI bundles. The updated field correctly presents omission as the platform-owned-account flow, but the endpoint-level description still limits rule-based accounts to individual customers and should be aligned.

Updates the modular InternalAccountCreateRequest schema.
Regenerates openapi.yaml and mintlify/openapi.yaml consistently.
Leaves conflicting ownership availability guidance on POST /internal-accounts.

_{Reviews (1) · Last reviewed commit: "docs: drop stale platform-owned rule-bas..."}

greptile-apps · 2026-09-23T20:45:31Z

      account in the same currency, which is where funds land when a sweep
-      cannot be completed. Platform-owned rule-based accounts are not available
-      yet, so omitting this is currently rejected.
+      cannot be completed.


Conflicting account availability guidance

This field now says that omitting customerId creates a platform-owned account, but the POST /internal-accounts operation still says rule-based accounts are available “for individual customers.” This contradiction can make integrators overlook the newly supported platform-owned flow. Please align the operation description and rebundle the generated contracts.

Knowledge Base Used:

Grid API contract

Customers and accounts API

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/customers/InternalAccountCreateRequest.yaml Line: 17 Comment: **Conflicting account availability guidance** This field now says that omitting `customerId` creates a platform-owned account, but the `POST /internal-accounts` operation still says rule-based accounts are available “for individual customers.” This contradiction can make integrators overlook the newly supported platform-owned flow. Please align the operation description and rebundle the generated contracts. **Knowledge Base Used:** - [Grid API contract](https://app.greptile.com/lightspark/-/custom-context/knowledge-base/lightsparkdev/grid-api/-/docs/api-contract.md) - [Customers and accounts API](https://app.greptile.com/lightspark/-/custom-context/knowledge-base/lightsparkdev/grid-api/-/docs/customers-and-accounts-api.md) --- For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Good catch, fixed in c067e69: the operation now says rule-based accounts are available "for a customer or for your platform itself", and both bundles are rebuilt. ⚡

🤖 notarized-geyser (#1) | Feedback

…-accounts Co-Authored-By: greptile-apps <greptile-apps@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

vercel · 2026-09-23T20:47:57Z

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

3 Skipped Deployments

Project	Deployment	Actions	Updated
grid-cards-demo	Ignored	Preview	Sep 23, 2026 8:59pm UTC
grid-flow-builder	Ignored	Preview	Sep 23, 2026 8:59pm UTC
grid-wallet-demo	Ignored	Preview	Sep 23, 2026 8:59pm UTC

ls-bolt · 2026-09-23T20:48:19Z

⚡ Review ledger

Round 1

Operation says rule-based accounts are for individual customers only, which contradicts the platform-owned customerId flow → FIXED: c067e69, openapi/paths/internal_accounts.yaml plus the rebuilt bundles (lint-openapi clean)

mintlify · 2026-09-23T20:48:25Z

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

Project	Status	Preview	Updated
Grid	🟢 Ready	View Preview	Sep 23, 2026, 9:00 PM

Co-Authored-By: bsiaotickchong <bsiaotickchong@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs: drop stale platform-owned rule-based account caveat

b40bae9

Platform-owned rule-based accounts are supported, so omitting customerId on POST /internal-accounts is no longer rejected. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

ls-bolt Bot added the bolt label Sep 23, 2026

ls-bolt Bot mentioned this pull request Sep 23, 2026

docs: drop stale platform-owned rule-based account caveat #1062

Closed

mintlify Bot deployed to staging - mintlify September 23, 2026 20:42

View deployment

greptile-apps Bot reviewed Sep 23, 2026

View reviewed changes

docs: say rule-based accounts can be platform-owned on POST /internal…

c067e69

…-accounts Co-Authored-By: greptile-apps <greptile-apps@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

mintlify Bot deployed to staging - mintlify September 23, 2026 20:48

View deployment

docs: drop the platform-enablement clause from POST /internal-accounts

3a12b5f

Co-Authored-By: bsiaotickchong <bsiaotickchong@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

mintlify Bot deployed to staging - mintlify September 23, 2026 21:00

View deployment

shreyav approved these changes Sep 23, 2026

View reviewed changes

JasonCWang approved these changes Sep 23, 2026

View reviewed changes

bsiaotickchong merged commit 141750d into main Sep 23, 2026
10 of 11 checks passed

bsiaotickchong deleted the 09-23-drop-stale-platform-owned-account-caveat branch September 23, 2026 21:21

Navigation Menu

Repository navigation

docs: drop stale platform-owned rule-based account caveat - #1063

docs: drop stale platform-owned rule-based account caveat#1063
bsiaotickchong merged 3 commits into
mainfrom
09-23-drop-stale-platform-owned-account-caveat

bsiaotickchong commented Sep 23, 2026 •

edited by ls-bolt Bot

Loading

Uh oh!

lightspark-bot commented Sep 23, 2026

Uh oh!

ls-bolt Bot commented Sep 23, 2026 •

edited

Loading

Revision 2

Revision 1

Uh oh!

greptile-apps Bot commented Sep 23, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot Sep 23, 2026

Uh oh!

ls-bolt Bot Sep 23, 2026

Uh oh!

vercel Bot commented Sep 23, 2026 •

edited

Loading

Uh oh!

ls-bolt Bot commented Sep 23, 2026

Uh oh!

mintlify Bot commented Sep 23, 2026 •

edited

Loading

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

bsiaotickchong commented Sep 23, 2026 • edited by ls-bolt Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Test plan

Uh oh!

lightspark-bot commented Sep 23, 2026

Uh oh!

ls-bolt Bot commented Sep 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Revision 3

Revision 2

Revision 1

Uh oh!

greptile-apps Bot commented Sep 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 4/5

Findings

Summary

Uh oh!

greptile-apps Bot Sep 23, 2026

Choose a reason for hiding this comment

Uh oh!

ls-bolt Bot Sep 23, 2026

Choose a reason for hiding this comment

Uh oh!

vercel Bot commented Sep 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ls-bolt Bot commented Sep 23, 2026

Round 1

Uh oh!

mintlify Bot commented Sep 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

bsiaotickchong commented Sep 23, 2026 •

edited by ls-bolt Bot

Loading

ls-bolt Bot commented Sep 23, 2026 •

edited

Loading

greptile-apps Bot commented Sep 23, 2026 •

edited

Loading

vercel Bot commented Sep 23, 2026 •

edited

Loading

mintlify Bot commented Sep 23, 2026 •

edited

Loading