Skip to main content
Blaxel runs agent infrastructure: micro-VM sandboxes, hosted agents, batch jobs, MCP servers, and volumes. CostGraph reads the billed cost and usage Blaxel reports, as FOCUS 1.2 records at a grain of one record per resource per billing dimension per day.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call Blaxel 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

  • In the Blaxel console, go to Profile > Security and create an API key. Use a personal key from an account member: a service-account key only sees its own workspace.
  • Copy the account id from the account settings.
  • The connect form links to the page where you create this credential.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick Blaxel.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what Blaxel 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 Blaxel 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 Blaxel 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 Blaxel spend appears in Cost Overview and in anomaly detection alongside every other provider.

​
Managed sandboxes

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