Connect DigitalOcean

The DigitalOcean integration imports daily estimated costs into Cloud Intelligence™. Use Cloud Analytics to analyze your organization’s infrastructure spend by team, date, SKU, and region. Verified AI charges can also appear in GenAI Intelligence.

Prerequisites

• A DigitalOcean organization with access to its billing information.
• The organization’s UUID and an organization personal access token with the billing:read scope.
• A DoiT account with the Billing Profiles Admin permission.

Connect the organization once. Its costs retain the team that incurred each charge. Organization-level credits remain attributed to the organization. Standalone-team connections are not supported; connecting a team separately would risk duplicating costs already imported through the organization.

Ask your organization owner for the organization UUID. A team UUID, user account UUID, or project ID cannot replace it. Optional team-membership discovery through DigitalOcean’s Organizations API requires a separate permission; the billing connection requires only billing:read.

Create a billing token

1. Sign in to the DigitalOcean control panel and select the organization you want to connect.
2. Open the organization’s API tab, then select Generate New Token.
3. Give the token a descriptive name and choose an expiration date.
4. Select Custom Scopes and grant billing:read.
5. Generate and copy the token. DigitalOcean displays its secret only once.

The token's permissions also depend on your DigitalOcean organization role. See Manage your organization. Use a billing personal access token for this connection; an inference model access key does not provide billing access.

Connect your organization

1. Sign in to Cloud Intelligence.
2. Open Data ingestion and integrations > Integrations and find DigitalOcean.
3. Select Connect +.
4. Enter the Organization ID and Personal Access Token for the same organization.
5. Select Test connection, then Save after the test succeeds.

The connection test checks access to Billing Insights. An organization with no billing rows can pass the test, but a forbidden or failed request cannot. Initial loading targets the last 180 completed days, limited by available DigitalOcean history, which starts on December 1, 2025.

Infrastructure costs

The integration imports charges that DigitalOcean exposes through Billing Insights, including ordinary infrastructure charges. It preserves unknown SKUs so a new product does not lose its cost merely because it has not been classified.

Reporting dimension	DigitalOcean value
Provider	DigitalOcean
Billing account	Connected organization
Team	Team that incurred the charge, or the organization for organization-level credits
SKU	Billing SKU and description
Region	Region code, when provided
Date	Usage day

Labels include Cost basis, Billing source, Team, SKU, Region, Resource description, and Resource group. A resource description is not a durable resource ID. DigitalOcean projects, resource tags, and native usage quantities are not included in this release.

Estimated cost

Billing Insights contains daily estimates derived from nightly invoice items. Its monthly sum can differ from the final invoice. DoiT identifies this data as estimated cost and does not add invoice previews, payments, or prepaid balance top-ups to it. Use your DigitalOcean invoice for final billing reconciliation. DigitalOcean’s billing responses can cover the entire organization. Compare organization totals with the consolidated invoice; filter both sides consistently when comparing a single team.

AI costs and GenAI Intelligence

AI coverage uses reviewed billing SKUs. A verified AI charge contributes to GenAI spend; ordinary GPU Droplets, storage, networking, and unidentified SKUs are not automatically classified as AI.

The verified GLM5.3 Flash input and output SKUs map to model glm-5.3-flash and developer Zhipu AI. DigitalOcean remains the billing provider. Other models and developers appear only after their billing SKUs have been verified. Charges without verified AI classification remain available in ordinary DigitalOcean cost reports.

Billing Insights does not provide structured daily input/output token counts, cache counts, request counts, or GPU-hour quantities. A billing description can repeat the same token count across several days, including days with zero cost. DoiT does not convert that text into usage metrics, so token-efficiency and cost-per-million-token analysis are unavailable through this billing connection. Token usage shown in DigitalOcean's inference console is a separate data source.

The Inference Cloud Trial credit can offset both infrastructure and AI charges. DoiT retains this general credit in ordinary DigitalOcean billing without assigning it to GenAI. An organization can therefore have positive GenAI spend while its total DigitalOcean cost is zero after credits.

Costs billed directly by another model provider when you supply that provider's own API key belong to that provider's billing integration. Do not add them again as DigitalOcean spend. Similarly, the DigitalOcean billing and Tokenomics views represent the same eligible charges; their costs should not be added together.

Refresh and corrections

DoiT checks for updates every six hours and imports completed days. DigitalOcean publishes the underlying estimates nightly, so the polling interval is not a guarantee of six-hour freshness.

The integration refreshes the last 35 completed days to capture recent corrections. Successful refreshes replace earlier values, including days that become empty, without duplicating charges. Failed requests preserve the last successfully imported data. Older corrections may require a backfill.

Troubleshooting

• Test connection returns 401 or 403: Verify the organization UUID, the token’s billing:read scope, and the token owner’s organization permissions. Create the token in the organization’s API tab, not an individual team’s settings. Reading an account balance successfully does not establish access to Billing Insights. DigitalOcean token scopes cannot be edited after creation; create a new appropriately scoped token if necessary.
• No data after an inference request: Wait for DigitalOcean's next billing refresh. Very small charges may round to zero at the source's published precision. Confirm the model key and billing token cover the same organization and usage team.
• AI spend is missing from GenAI Intelligence: First check whether the charge appears in DigitalOcean cost reports. AI classification additionally requires a verified SKU mapping; unknown charges are retained without AI attribution.
• Totals differ from the invoice: Daily Billing Insights estimates do not necessarily include all final invoicing factors. Compare the same organization, teams, and dates and retain the estimated-cost distinction.

If you need assistance, open an expert inquiry.