Guide updated
Implemented from official documentation; live-account verification is pending. Key creation, permissions, workspace selection and console reconciliation need your own account test. Automated checks do not replace it.
- Required credentials
- Segmind API Key
- Monitoring currency
- USD · dollar-denominated Credits
- What is monitored
- Workspace Credits · USD
- GET https://api.segmind.com/v1/get-user-credits returns credits for the upstream Personal or team workspace (scope=provider_workspace). The official billing pages denominate Credits in dollars: credits=25 displays $25. This is not a Quota Monitor project wallet or member spending limit.
Check Segmind Credits without sharing a key
- Sign in to the official console and select the paying Personal or team workspace with the bottom-left switcher.
- Open Billing and read Credits Balance, not Cost Analytics spending or a member's daily, weekly or monthly cap.
- Compare again after pending work or authorized funding settles. Manual checking sends no credential to Quota Monitor.
Connect Segmind to Quota Monitor
Choose the paying workspace
Sign in at platform.segmind.com. Use the workspace switcher at the bottom left to select Personal or the team that pays for your application, then open Billing.
Check the workspace name and Credits Balance. You do not need to create a team, run a model or buy credits to set up monitoring.
Open the API Keys page
Choose Developer at the bottom of the left navigation, then API Keys. Use the page's new-key creation control for a separate monitoring key.
Leave existing application keys unchanged. The documented key shape is SG_ followed by 16 hexadecimal characters; a JWT, key name or masked suffix is not the secret.
Review permissions before saving the key
Use a recognizable name such as Quota Monitor balance where the creation form allows a name. Review any model-access and expiry controls offered for the new key, then complete creation.
No balance-only scope or deny-all model policy is confirmed in the public docs. Do not assume a Member role, spending cap or empty model list makes the key read-only. If this risk is unacceptable, use manual checking below.
Store the complete secret securely
Copy the new API key into secure storage while it is available. Confirm that it belongs to the intended Personal or team workspace before using it.
Do not copy x-api-key: with the value, add quotes or paste it into chat, URLs or screenshots. If the secret is lost, create a replacement rather than exposing another application's key.
Add a connection inside your project
In Quota Monitor open the target project → add provider connection → new connection → Segmind (USD). Enter a clear connection name, paste the key into the masked API Key field and save.
No workspace ID, custom endpoint or provider project/key filter is needed. A Quota Monitor project organizes monitoring; it cannot split Segmind's shared funds.
Reconcile the first successful sync
Wait for the first sync or refresh once the cooldown ends. Check the new successful timestamp and compare the same workspace's Billing balance. credits=25 must display $25, not $0.25.
free-credits=2 is displayed separately, not as $27 total. REST/MCP segmindBalance.balance must agree with the card's main amount. Compare nearby timestamps and allow for console rounding.
Use official billing when funds are low
Choose Open provider on the card to reach Billing. Recheck the signed-in workspace before an authorized person uses Recharge or reviews Auto-recharge.
Quota Monitor neither pays nor changes auto-recharge. Wait for funds to post before refreshing; member spend caps and model restrictions are separate from this balance.
Rotate or stop monitoring safely
For routine rotation create a new dedicated key, update the existing connection through the secure form, confirm sync, then revoke the old monitoring key in Developer → API Keys. Revoke immediately if exposed.
Removing a project association does not revoke the upstream key or delete a connection used elsewhere. Handle these actions separately and do not alter unrelated application keys.
What Quota Monitor reads from Segmind
- Use credits as the main spendable amount. free-credits is separate; its relationship to paid or subscription funds is not defined here. Never add it, assume cash/bonus splits, or apply another provider's credit ratio.
- Workspace funds may be shared by multiple keys and Quota Monitor projects. Do not sum duplicate balances or subtract usage a second time. Select the matching upstream workspace when comparing the console.
- Only a free balance GET is made: no model generation, login sessions, key management, top-ups or permission changes. Public REST/MCP exposes segmindBalance.balance and freeCredits from the same snapshot.
- Query time is not settlement time. In-flight jobs can reserve funds without changing the visible balance; model restrictions and member limits can also block requests. Positive Credits do not prove generation is available.
- Zero and negative values are retained. Missing fields, malformed responses and failures keep the previous successful amount and time, never fabricate zero. Credits are service funding, not withdrawable cash.
- The dashboard shows the latest successful snapshot. Manual refresh queries the provider again but cannot eliminate upstream billing delays. An old balance is not a new result after a failed query.
Segmind FAQ and troubleshooting
- Why do I get 401 or 403?
- Recheck the complete SG_ key on Developer → API Keys and whether it is active. Do not substitute a browser JWT or Cookie, widen permissions blindly or reuse a production key to bypass an error. Use manual checking if permissions remain unclear.
- What does 404 mean?
- The official balance endpoint documents 404 when no credit record exists. Check Billing for the intended workspace or ask Segmind support; it is not proof of zero funds. The connector does not try private endpoints.
- Why are free credits not added?
- The API defines credits as the spendable console balance and returns free-credits separately without an additive rule. Keep them separate. Neither field proves a refundable cash amount or unrestricted model access.
- Why is my team balance different?
- Confirm the workspace associated with this key and select that same Personal/team workspace in the console. Do not compare another team, Cost Analytics, member caps or a Quota Monitor project budget. Check again when running jobs finish.
- What happens after 429 or invalid_response?
- Wait for the next permitted refresh. A rejected or incomplete response retains the last successful snapshot and time, not a new zero. Send support only the redacted error code and timestamp, never the key.
- Has a real account passed verification?
- Not yet. Verify key creation and permissions, Personal/team scope and first-sync values, then compare the card and REST/MCP snapshot with official Billing. Deployment and synthetic tests are not live-account acceptance.
Official Segmind references
- Official reference · docs.segmind.com/docs/platform/account-and-billing-apis(opens in a new tab)
- Official reference · docs.segmind.com/docs/get-started/authentication(opens in a new tab)
- Official reference · docs.segmind.com/docs/platform/settings(opens in a new tab)
- Official reference · docs.segmind.com/docs/platform/teams(opens in a new tab)
- Official reference · docs.segmind.com/docs/platform/pricing-and-billing(opens in a new tab)
Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.