# FinOps: provider costs in one place

Monitor imported costs, coverage and synchronization per connection, keeping the Zild subscription separate from API usage.

Source: https://zild.ai/en-US/docs/apps/zild-admin/updates-finops-provedores

Monitor imported costs, coverage and synchronization per connection, keeping the Zild subscription separate from API usage.

## How to use it

In Admin, configure administrative access in AI Providers. In Provider costs, select a connection and UTC month, synchronize and check the latest import. Reconcile daily and service costs with the provider account, including usage outside Zild.

## Limits and prerequisites

Azure and Bedrock budgets send alerts; they do not stop usage. Gemini synchronizes caps without importing cost or token reports. Missing coverage does not mean zero spend. Reports may lag; tokens and request counts are not available for every provider.

## Validate in your operation

Run a controlled import and compare period, currency and scope with the invoice. Assign alert recipients and budget owners. Do not confuse a financial estimate with a technical spending block.

## Disabling synchronization does not stop agents

The automatic synchronization setting controls the connection’s financial import. Disabling it does not disable the execution connector or remove existing provider limits. To stop an operation, review the relevant agent, flow and execution controls; do not treat a lack of new imports as evidence that consumption has stopped.

Likewise, a failed execution test does not automatically erase financial configuration. Investigate each test message separately and check the latest verification time.

## Where to find each type of information

In Zild Admin, open FinOps and select Provider costs to inspect financial imports by connection and month. The Success and ROI tab presents evaluated agent outcomes. Use AI Providers to configure connections and access; credentials are not entered in the cost table.

If agent names fail to load in Success and ROI, results may remain available by identifier. Use Try again to recover names and confirm the ID before attributing a result to a process. This error differs from a failed cost import.

## Accumulated costs and average per user on the dashboard

The Admin dashboard’s accumulated cost combines periods imported into FinOps. Usage filters such as department, model or activity period do not narrow this financial total. Check partial-total notices and available imports before treating the value as complete coverage.

Average cost per user divides that accumulated cost by users with AI usage within the selected filters. Changing a filter can therefore change the denominator without changing the cost. This ratio is not automatically monthly cost per person or the selected department’s cost.

Synthetic example: US$600 imported and 30 filtered users produce US$20 per user. If a filter reduces the list to 10 users, the ratio becomes US$60 with no new spending. To compare departments or periods, first reconcile the same cost scope, time coverage and population; record the underlying values separately from the summary indicator.

The chart uses accumulated cost by UTC date. Do not sum its points as daily expenses: each point already includes earlier amounts. Missing configuration, a pending import and a failed query do not mean zero spending.

## From configuration to the first test

- Open the provider in AI Providers and review the selected connector. When exactly one enabled connector exists for that provider, the screen may select it automatically; confirm the intended environment.
- Create or edit the execution connector and save the provider to record the association. The access test can check a connector before saving, but does not replace saving that association.
- Use the execution test to verify catalog access. A successful result does not generate an AI response or establish permission for every model.
- Synchronize models after saving and activate those needed in ModelOps. If synchronization fails, check the message and last valid catalog; saving the provider does not establish successful model synchronization.
- Run a controlled case with the selected model in the agent, checking the response, tools and cost. Then configure and test the financial integration separately, if needed.

When editing, the administrative credential field returns empty. Leaving it empty preserves the existing credential; it is not a removal command. To replace it, enter the new credential and save. Testing costs, synchronizing models and changing limits require pending form changes to be saved.

Creating or editing a connector requires CreateConnector or UpdateConnector, respectively, in addition to management and lookup access. If a button is unavailable, check permissions and form state before rotating the key.

## Monthly review for the process owner

- Select the financial connection and UTC month. The list shows connections with costs configured; having an execution connector does not guarantee it appears here.
- Check organization/project, coverage and last successful import before copying any number. A disabled connection can retain old reports and existing provider limits.
- Open Costs by service to understand the total and Tokens by model where available. Cached tokens are already included in input tokens: do not add both columns to calculate total input.
- Compare the numeric cost with the budget. The current-month percentage bar is capped at 100%; it does not show how far spending exceeded the budget. For earlier months, the displayed limit remains the current limit, not that month’s historical budget.
- Record scope and review time with the process report. If the project also serves other applications, the imported total cannot be fully attributed to your pilot.

Illustrative example: engineering project review uses an account shared with logistics. Before calculating cost per reviewed project, separate consumption attributable to each process using execution evidence and the scope available from the provider. Dividing all account spending only by engineering reviews would produce an incorrect metric.

## Execution and financial management are different connections

The key used by an agent to run a model is not necessarily sufficient to read costs or manage budgets. In AI Providers, review the execution connector and financial administrative credential separately. An execution connection can be registered before financial reporting is enabled.

Financial configuration belongs to the authenticated company. Once configured, organization/project identity remains fixed to preserve historical scope. Do not reuse the same financial identity across companies. Rotating credentials is different from changing reporting scope.

## What each integration can monitor



<table><thead><tr><th scope="col">Provider</th><th scope="col">Cost scope</th><th scope="col">Tokens and requests</th><th scope="col">Financial control</th></tr></thead><tbody><tr><td>OpenAI</td><td>Configured project, including other applications using it.</td><td>Completion tokens; costs may include other services.</td><td>Project monthly limit; verify enforcing status.</td></tr><tr><td>Anthropic</td><td>Dedicated workspace; Default is not accepted. Imported costs exclude Priority Tier.</td><td>Tokens by model; message counts are not provided by the report.</td><td>Configure Spend limits in Anthropic Console. This integration does not confirm or change that cap.</td></tr><tr><td>Gemini</td><td>This integration does not import cost reports.</td><td>Does not import tokens or requests.</td><td>Synchronizes eligible project spend caps; delays and overshoot are possible.</td></tr><tr><td>Azure AI Foundry</td><td>Entire Foundry resource. External Search, Storage and other resources are not automatically included.</td><td>Does not import or estimate tokens or requests.</td><td>Alert-only budget. Does not stop usage.</td></tr><tr><td>AWS Bedrock</td><td>Amazon Bedrock service for the account across commercial regions. Excludes charges classified under other services.</td><td>Does not import or estimate tokens or requests.</td><td>AWS Budgets alerts. Does not create invocation blocks.</td></tr></tbody></table>



## Prepare identifiers and access



<table><thead><tr><th scope="col">Provider</th><th scope="col">Account identification</th><th scope="col">Administrative credential</th></tr></thead><tbody><tr><td>OpenAI</td><td>Organization ID and active project ID.</td><td>Authorized account administrative key, separate from the execution key.</td></tr><tr><td>Anthropic</td><td>Organization ID and dedicated workspace (wrkspc_...).</td><td>Administrative key with access to organization reports.</td></tr><tr><td>Gemini</td><td>Billing account and canonical Google Cloud project number, not its name.</td><td>Service-account JSON. Enable Cloud Billing Budget, Cloud Billing and Cloud Resource Manager; grant project lookup and budget access required by the operation. Billing account currency must be USD.</td></tr><tr><td>Azure AI Foundry</td><td>Subscription GUID and resource-group/resource-name.</td><td>Entra ID application JSON with tenantId, clientId and clientSecret. Requires resource read access and appropriate Cost Management permissions. Costs must be USD; there is no automatic currency conversion.</td></tr><tr><td>AWS Bedrock</td><td>12-digit AWS account ID and bedrock scope.</td><td>JSON with accessKeyId, secretAccessKey and sessionToken for temporary credentials. notificationEmail is required to create a budget. Enable Cost Explorer and IAM billing access; allow cost queries and budget management as needed.</td></tr></tbody></table>



Do not share these secrets in conversations or training material. Enter them only in appropriate configuration fields. The Bedrock integration does not automatically renew temporary tokens: plan rotation before expiry.

## Read status before making a decision



<table><thead><tr><th scope="col">Status</th><th scope="col">Interpretation</th></tr></thead><tbody><tr><td>enforcing</td><td>The provider confirmed the applicable cap configuration. Accounting delays may still occur.</td></tr><tr><td>alert_only</td><td>An advisory budget exists; usage is not blocked. This does not prove email delivery.</td></tr><tr><td>pending / unknown / unconfirmed</td><td>The final state is not sufficiently confirmed. Recheck or synchronize before assuming failure or success.</td></tr><tr><td>unavailable</td><td>The integration cannot confirm this control. For Anthropic, manage the cap in Console.</td></tr><tr><td>blocked / inactive</td><td>For Gemini, blocked indicates cap-paused usage; inactive can mean waiting for the next period. For budgets, inactive can also mean outside the effective period. Interpret according to provider.</td></tr></tbody></table>



## Synchronization, history and troubleshooting

- Select the UTC month and check the last successful import. The routine imports current and previous months; older imported periods remain available.
- On failure, the dashboard preserves the previous import. Fix access and synchronize; old data is not a completed refresh.
- Bedrock automatic imports reuse results completed within six hours. Manual synchronization bypasses that window, and Cost Explorer queries may incur charges.
- A month without coverage differs from an imported month without activity. Gemini cap queries do not fabricate financial coverage.
- Compare report currency and scope before reconciling it with a Zild subscription or consolidated provider invoice.

Dashboard access requires AccessReports. Changing financial connections, synchronizing or managing limits requires UpdateTenantConfig. Execution-connector lookup also depends on ViewConnectors. Request access from your company administrator.

## Availability

Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.

Documentation reviewed: 2026-10-28.

[Read the announcement](/en-US/blog/finops-provedores)