Guide updated
Official documentation reviewed 2026-10-17. The implementation is ready for user verification; real PAT creation, least-privilege access, organization funding scope and console/API reconciliation have not been tested with a real account. No provider login, model call, payment or permission change was performed.
- Required credentials
- Dedicated DigitalOcean PAT (dop_v1_ · billing:read)
- Monitoring currency
- USD · decimal dollars, not cents
- What is monitored
- Whole-account prepayment · not AI wallet
- Only GET https://api.digitalocean.com/v2/customers/my/prepayment_status. status.balance is the authenticated cloud billing account's prepayment, shared with all DigitalOcean products, not an AI-specific wallet or a Quota Monitor project balance. No identity discovery, bills, inference or payment calls.
Check privately without hosting a token
- Open the selected team's Billing page, or the organization's Billing tab for an organization-owned team. Confirm which account funds the workload.
- Read account prepayment separately from Inference & Agents balance, promotional credits and the ordinary invoice/amount owed. Do not add repeated team or project views.
- If already configured, use official doctl prepayment status and compare Balance at a similar time. No new payment, token disclosure or model request is needed.
Connect DigitalOcean · Account prepayment to Quota Monitor
Identify the correct billing context
Sign in yourself to the DigitalOcean Control Panel and select the team that owns the workload. Open Billing and find the account prepayment separately from Inference & Agents balance and the amount owed on the ordinary bill.
For an organization-owned team, open the profile menu → View Organizations → select the organization → Billing to check shared funding. Check that you already have financial access; do not create another organization, top up or change auto-reload just for monitoring.
Open personal access token creation
In the Control Panel main menu choose Account → API. On Applications & API Tokens, find Personal access tokens and choose Generate New Token.
Create a dedicated name such as QuotaMonitorBilling and an appropriate expiration. This integration uses a personal access token, not an inference/model key, Spaces key, OAuth access/refresh token, password or browser Cookie.
Select the minimal custom scope
Choose Custom Scopes, search for billing and select Read (billing:read) only. Inspect the selected-scope summary before generating the token. The documented endpoint needs no additional scope.
Do not choose the broad Read Only alias api:read or Full Access. billing:read also exposes other billing/invoice information, so it is not a balance-only scope. Available scopes depend on your existing team role; if missing, ask an existing administrator rather than elevating the monitoring identity. There is no IAM-policy JSON to paste for this UI flow.
Generate and privately retain the PAT
Select Generate Token only after checking the name, expiration and scope. Save the one-time displayed dop_v1_ value privately; do not put it in chat, URLs, screenshots, logs or MCP arguments.
A lost value requires a replacement token, not a Cookie workaround. Scopes cannot be edited after creation; use a new dedicated token for a deliberate rotation. Quota Monitor cannot verify the token's granted scope from its prefix, so you must check the creation summary.
Connect the account prepayment provider
In the target Quota Monitor project, add a connection and select DigitalOcean · Account prepayment. Enter the dedicated PAT in the masked credential field; the MCP secure-credential link uses the same form.
Currency is fixed to USD and there is no team/project/key filter, endpoint override or daily-burn estimate. Credentials are encrypted server-side and other views expose only a suffix. Open the help drawer to review this guide without submitting or revealing the input.
Reconcile the first successful reading
Refresh and confirm the successful query time advances. Compare status.balance with account prepayment for the same billing context at a similar time. For example, 25.123456789 USD means dollars, not 25.123456789 cents or an amount to divide by 100.
If the console groups amounts differently, use an already configured official doctl prepayment status locally and compare Balance; do not use doctl balance or the separate AI balance. eligible=false does not make a returned balance invalid. Missing data, a 404 or a denied query is an error, never an invented zero.
Interpret the independent flags
Check eligible (eligibility for the account prepayment gate), blocked (whether that gate blocks usage) and is_auto_prepay_enabled (account automatic prepayment). Unknown values stay unknown and are not shown as disabled.
These are not the AI wallet's auto-reload settings, expiry dates or a guarantee that a model can run. Other AI funds or promotional credits may remain. Thresholds in Quota Monitor only classify this account prepayment and do not change upstream payments or limits.
Troubleshoot and rotate safely
For 401, check the PAT's expiration/revocation and that the raw dop_v1_ token—not a Bearer header—was entered. For 403, check billing:read and the selected billing context without granting broader roles. For 404 or an unavailable prepayment feature, retain manual checking instead of guessing another endpoint; retry 429/temporary failures later.
Rotate through the secure credential form and verify a successful read before retiring the old monitoring token. Do not alter business credentials, call a paid model or top up as a test. Failed reads preserve the previous successful amount and timestamp; report only redacted error codes.
What Quota Monitor reads from DigitalOcean · Account prepayment
- The Inference & Agents balance is a separate AI-only balance. Account prepayment also pays for non-AI services. This connection reads only account prepayment; it does not claim that the general billing API exposes the AI wallet.
- Promotional credits, the Inference & Agents balance and account prepayment are distinct. AI usage draws in that order. A zero account prepayment does not prove that AI has no funds or that all cloud resources are stopped.
- Teams in an organization draw from organization-funded balances. Independent teams have their own billing context. Select the intended context before creating the PAT; duplicate connections must not be summed or allocated to individual projects/keys.
- balance is a decimal-dollar string; preserve zero, negative values and precision. month_to_date_balance and /customers/my/balance are billing figures, not substitutes. This connection discards them and does not guess a sign convention, reset, expiry or AI runway.
- eligible, blocked and is_auto_prepay_enabled describe the account prepayment gate only. Missing or null flags mean not returned, not false. Quota Monitor does not enable auto-reload or infer model availability from these flags.
- 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.
DigitalOcean · Account prepayment FAQ and troubleshooting
- Is this the DigitalOcean AI wallet?
- No. It is shared whole-account prepayment, which can also fund AI after other applicable funds. The independent Inference & Agents balance is not queried. General billing balance and month-to-date costs are not used as wallet funds.
- Which permission is required, and is it balance-only?
- Custom Scopes billing:read only; the reference lists no additional scope. It also permits other billing/invoice reads. Broad api:read or Full Access is unnecessary. A prefix alone cannot prove minimal permissions.
- Why does my team show the same amount as another team?
- Organization-owned teams share organization-funded balances. Check the selected billing context and reconcile it yourself; do not sum duplicate views or assume a per-team allocation. Real organization behavior is pending user testing.
- Does zero or blocked=true mean all AI calls will fail?
- No. The API flag describes the account prepayment gate, and AI-specific funds or promotional credits may exist separately. Model availability, reset time, expiry and AI runway remain unknown.
- Why are flags missing, or why is eligible=false?
- The official flags are optional. Missing/null means not returned, not false. eligible describes participation in the account prepayment gate experience; it is not an AI-credit balance or a reason to discard a valid balance.
- What if the API returns 403/404 or the amount differs?
- Check existing scope, expiration and billing context without expanding privileges. Compare account prepayment, not an invoice or AI wallet, at a similar time; payments and usage may update at different times. A failed or unsupported read retains the old snapshot, not zero.
Official DigitalOcean · Account prepayment references
- Official reference · docs.digitalocean.com/reference/api/reference/billing/(opens in a new tab)
- Official reference · docs.digitalocean.com/reference/api/scopes/billing/read/(opens in a new tab)
- Official reference · docs.digitalocean.com/reference/api/create-personal-access-token/(opens in a new tab)
- Official reference · docs.digitalocean.com/products/inference/how-to/manage-serverless-inference-prepayment/(opens in a new tab)
- Official reference · docs.digitalocean.com/platform/billing/pay-bills/(opens in a new tab)
- Official reference · docs.digitalocean.com/reference/doctl/reference/prepayment/status/(opens in a new tab)
- Official reference · github.com/digitalocean/openapi/blob/main/specification/resources/billing/models/prepayment_status.yml(opens in a new tab)
- Official reference · docs.digitalocean.com/platform/billing/invoices/(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.