Skip to content

docs(openai): rephrase Admin API key description to emphasize cost tracking (#7038) - #7048

Open
hmadhsan wants to merge 2 commits into
superplanehq:mainfrom
hmadhsan:docs/rephrase-openai-admin-key-cost-tracking
Open

docs(openai): rephrase Admin API key description to emphasize cost tracking (#7038)#7048
hmadhsan wants to merge 2 commits into
superplanehq:mainfrom
hmadhsan:docs/rephrase-openai-admin-key-cost-tracking

Conversation

@hmadhsan

Copy link
Copy Markdown

Closes #7038

🐛 What was the issue?

The OpenAI integration instructions previously stated: "Only required for the Get Usage Data component.", understating the value of setting an Admin API Key for tracking cost and usage data.

🛠️ What did we fix?

Rephrased the Admin API Key instructions in both pkg/integrations/openai/openai.go and docs/components/OpenAI.mdx to clearly state:

Required for tracking organization usage and costs via the Get Usage Data component.

🧪 Testing & Verification

  • Verified documentation and integration instruction formatting across openai.go and OpenAI.mdx.

hmadhsan added 2 commits July 28, 2026 12:13
…nehq#6359)

Signed-off-by: hmadhsan <20043390+hmadhsan@users.noreply.github.com>
…acking (superplanehq#7038)

Signed-off-by: hmadhsan <20043390+hmadhsan@users.noreply.github.com>
@superplanehq-integration

Copy link
Copy Markdown
Contributor

Maintainers: comment /deploy-storybook to get a Storybook link for this PR.

@superplanehq-integration

Copy link
Copy Markdown
Contributor

👋 Commands for maintainers:

  • /sp start - Start an ephemeral machine (takes ~30s)
  • /sp stop - Stop a running machine (auto-executed on pr close)

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.

Rephrase need for OpenAI Admin API key

1 participant