Skip to main content
BoxCompute runs cloud computers for AI agents, billed per second while a VM runs. CostGraph reads BoxCompute at a grain of one record per sandbox per day. Spend is BoxCompute’s own settled charges, plus an estimate for runs still in progress that is replaced after they settle.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we read BoxCompute. Nothing to run.

You push it

You send us the records over the API. Your credentials stay in your infrastructure.

​
Before you begin

  • In BoxCompute, create an API key (bc_live_...) with the usage:read scope.
  • The connect form links to the page where you create this credential.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick BoxCompute.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what BoxCompute needs and marks the optional ones.
  4. Select Connect.
CostGraph verifies the credentials with a short fetch before saving, so a wrong value or a missing permission fails while you are still on the form.
Credentials are encrypted at rest and used only to read usage and cost. Revoke them in BoxCompute at any time and the connection stops; nothing else is affected.

​
Push it yourself

Send the charges to CostGraph yourself instead. Push data covers the connection id, the focus:write key, and the request shape.

​
Run the exporter

Your BoxCompute credential stays with you. Only the finished records reach CostGraph. Run the exporter covers the three ways to run it and the variables it reads.

​
What CostGraph does with it

BoxCompute spend appears in Cost Overview and in anomaly detection alongside every other provider.