Skip to main content
Collimate runs microVM sandboxes for coding agents, billed per second while live and per GB-month while suspended. CostGraph reads Collimate usage as FOCUS 1.2 records at a grain of one record per usage dimension per day. Spend is estimated from Collimate’s published prices and can differ from your invoice.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call Collimate once a day. Nothing to run.

You push it

You send us FOCUS records over the API. Credentials never leave your infrastructure.

​
Before you begin

  • Create an API key (col_live_...) in Collimate. It is shown once, so copy it before leaving the page. Read access to usage is enough.
  • The connect form links to the page where you create this credential.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Collimate.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Collimate 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 billing data. Revoke them in Collimate at any time and the connection stops; nothing else is affected.

​
Push it yourself

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

​
Run the exporter

Your Collimate credential stays where you put it, and only the finished FOCUS records reach CostGraph. Run the exporter covers the three ways to run it and the variables it reads.

​
What CostGraph does with it

Records land as raw billing rows, are normalised into line items, and roll up into daily cost. From there Collimate spend appears in Cost Overview and in anomaly detection alongside every other provider.

​
Managed sandboxes

The same Collimate account can run CostGraph code changes. See Managed sandboxes.