Skip to main content
New API (new-api / one-api) is a self-hosted LLM gateway that fronts many model providers behind one deployment and tracks the quota each request consumes. CostGraph reads New API as FOCUS 1.2 records at a grain of one record per day per model per token.

​
Choose how the data reaches us

CostGraph pulls it

You supply read-only credentials and we call New API 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 your new-api deployment, go to Profile > Security > Access Token and create an access token on an admin account. This is the dashboard token, not an inference sk- key, and admin scope is what reads logs across all users.
  • Note the base URL of the deployment and its QuotaPerUnit setting if you changed it from the default of 500000.

​
Let CostGraph pull

  1. Open Settings > Integrations and pick New API.
  2. Name the connection and pick the tenant these charges belong to.
  3. Enter the values you copied. The form lists what New API 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 New API 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

Rather than build that request yourself, run our exporter. It reads New API on a schedule and pushes the records for you, wherever you want to run it: a container, a Kubernetes CronJob, or a binary on a machine you already have.
Your New API 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 New API spend appears in Cost Overview and in anomaly detection alongside every other provider, with spend attributed back to the token or user that incurred it.